[#MULE-6202] Name is not a valid attribute for the new attachment, property, variable and session variable transformers - JIRA

Details

Type: Bug
Status: Reopened
Priority: Critical
Resolution: Unresolved
Affects Version/s: 3.3 RC4
Fix Version/s: 3.3.1, 3.4.0
Component/s: Schema
Labels:
- targeted-3.3.1

User impact:
High
Similar Issues:
None

Description

Name is not a valid attribute for the new attachment, property, variable and session variable transformers.

Transformers affected: set-attachment, remove-attachment, copy-attachment, set-property, remove-property, copy-property, set-variable, remove-variable, set-session-variable and remove-session-variable.
This affects Studio because we are not able to add these transformers as global ones. This causes inconsistency since all the transformers available in the palette are available as global transformers in the global elements pane.
I will be creating a Jira for Studio and I will make it dependent of this one.

Tipically all the transformers are global transformers and can be referenced by this name attribute. In this case, as name is not a valid attribute, if you create a flow and a transformer reference and reference that transformer, such as set-attachment, mule fails throwing the following error:

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ New app 'test'                                           +
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
INFO  2012-04-28 18:51:51,576 [[test].config.change.1.thread.1] org.mule.module.launcher.application.DefaultMuleApplication: 
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Initializing app 'test'                                  +
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
INFO  2012-04-28 18:51:51,582 [[test].config.change.1.thread.1] org.mule.lifecycle.AbstractLifecycleManager: Initialising RegistryBroker
INFO  2012-04-28 18:51:51,591 [[test].config.change.1.thread.1] org.mule.config.spring.MuleApplicationContext: Refreshing org.mule.config.spring.MuleApplicationContext@5d18a770: startup date [Sat Apr 28 18:51:51 GMT-03:00 2012]; root of context hierarchy
ERROR 2012-04-28 18:51:52,250 [[test].config.change.1.thread.1] org.mule.module.launcher.application.DefaultMuleApplication: null
org.xml.sax.SAXParseException: cvc-complex-type.3.2.2: Attribute 'name' is not allowed to appear in element 'set-attachment'.
	at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source)
	at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
	at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
	at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
	at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
	at org.apache.xerces.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(Unknown Source)
	at org.apache.xerces.impl.xs.XMLSchemaValidator.reportSchemaError(Unknown Source)
	at org.apache.xerces.impl.xs.XMLSchemaValidator.processAttributes(Unknown Source)
	at org.apache.xerces.impl.xs.XMLSchemaValidator.handleStartElement(Unknown Source)
	at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown Source)
	at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
	at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
	at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
	at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
	at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
	at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
	at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
	at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
	at org.springframework.beans.factory.xml.DefaultDocumentLoader.loadDocument(DefaultDocumentLoader.java:75)
	at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:388)
	at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:334)
	at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:302)
	at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:174)
	at org.mule.config.spring.MuleApplicationContext.loadBeanDefinitions(MuleApplicationContext.java:112)
	at org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:131)
	at org.springframework.context.support.AbstractApplicationContext.obtainFreshBeanFactory(AbstractApplicationContext.java:522)
	at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:436)
	at org.mule.config.spring.SpringRegistry.doInitialise(SpringRegistry.java:89)
	at org.mule.registry.AbstractRegistry.initialise(AbstractRegistry.java:109)
	at org.mule.config.spring.SpringXmlConfigurationBuilder.createSpringRegistry(SpringXmlConfigurationBuilder.java:116)
	at org.mule.config.spring.SpringXmlConfigurationBuilder.doConfigure(SpringXmlConfigurationBuilder.java:73)
	at org.mule.config.builders.AbstractConfigurationBuilder.configure(AbstractConfigurationBuilder.java:46)
	at org.mule.config.builders.AbstractResourceConfigurationBuilder.configure(AbstractResourceConfigurationBuilder.java:78)
	at org.mule.config.builders.AutoConfigurationBuilder.autoConfigure(AutoConfigurationBuilder.java:101)
	at org.mule.config.builders.AutoConfigurationBuilder.doConfigure(AutoConfigurationBuilder.java:57)
	at org.mule.config.builders.AbstractConfigurationBuilder.configure(AbstractConfigurationBuilder.java:46)
	at org.mule.config.builders.AbstractResourceConfigurationBuilder.configure(AbstractResourceConfigurationBuilder.java:78)
	at org.mule.context.DefaultMuleContextFactory.createMuleContext(DefaultMuleContextFactory.java:80)
	at org.mule.module.launcher.application.DefaultMuleApplication.init(DefaultMuleApplication.java:208)
	at org.mule.module.launcher.application.DefaultMuleApplication.redeploy(DefaultMuleApplication.java:366)
	at org.mule.module.launcher.application.DefaultMuleApplication$ConfigFileWatcher.onChange(DefaultMuleApplication.java:540)
	at org.mule.module.launcher.AbstractFileWatcher.run(AbstractFileWatcher.java:59)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
	at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
	at java.lang.Thread.run(Thread.java:680)

This is a flow test i created:

<?xml version="1.0" encoding="UTF-8"?>

<mule xmlns="http://www.mulesoft.org/schema/mule/core" xmlns:http="http://www.mulesoft.org/schema/mule/http" xmlns:doc="http://www.mulesoft.org/schema/mule/documentation" xmlns:spring="http://www.springframework.org/schema/beans" xmlns:core="http://www.mulesoft.org/schema/mule/core" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="EE-3.3.0" xsi:schemaLocation="
http://www.mulesoft.org/schema/mule/http http://www.mulesoft.org/schema/mule/http/current/mule-http.xsd 
http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-3.0.xsd 
http://www.mulesoft.org/schema/mule/core http://www.mulesoft.org/schema/mule/core/current/mule.xsd ">
    <set-attachment name="setattachment" value="value" contentType="" doc:name="Attachment" attachmentName="hey"></set-attachment>
    <flow name="flows1Flow1" doc:name="flows1Flow1">
        <http:inbound-endpoint exchange-pattern="request-response" host="localhost" port="8081" doc:name="HTTP"/>
        <echo-component doc:name="Echo"/>
        <transformer ref="setattachment" doc:name="Transformer Reference"/>
    </flow>
</mule>

I will attach a screen shot for this issue...

Options
- Sort By Name
- Sort By Date
- Ascending
- Descending
- Download All

Attachments

Errors in mule when executing a flow that contains a set-attachment transformer with name.png

271 kB

28/Apr/12 05:10 PM

Activity

Ascending order - Click to sort in descending order

Hide

Permalink

Pablo La Greca added a comment - 20/Aug/12 03:23 PM - edited

3.3.x: https://fisheye.codehaus.org/changelog/mule/?cs=24781
3.3.x: https://fisheye.codehaus.org/changelog/mule/?cs=24783
3.x: https://fisheye.codehaus.org/changelog/mule/?cs=24784

Show

Pablo La Greca added a comment - 20/Aug/12 03:23 PM - edited 3.3.x: https://fisheye.codehaus.org/changelog/mule/?cs=24781 3.3.x: https://fisheye.codehaus.org/changelog/mule/?cs=24783 3.x: https://fisheye.codehaus.org/changelog/mule/?cs=24784

Hide

Permalink

Daniel Feist added a comment - 21/Sep/12 02:05 PM

This also should be the case for <set-payload> which is in the same group of transformers as those fixed with this issue.

Show

Daniel Feist added a comment - 21/Sep/12 02:05 PM This also should be the case for <set-payload> which is in the same group of transformers as those fixed with this issue.

Name is not a valid attribute for the new attachment, property, variable and session variable transformers

Details

Description

Attachments

Activity

People

Dates

Agile