[JBoss JIRA] Created: (SWITCHYARD-411) Hardcoded directory name in jboss-as7's assembly.xml
by David Ward (JIRA)
Hardcoded directory name in jboss-as7's assembly.xml
----------------------------------------------------
Key: SWITCHYARD-411
URL: https://issues.jboss.org/browse/SWITCHYARD-411
Project: SwitchYard
Issue Type: Bug
Components: build, quickstarts
Affects Versions: 0.2
Reporter: David Ward
Priority: Minor
Fix For: 0.3
Inside release/jboss-as7/assembly.xml, you will find this line:
<directory>../../quickstarts</directory>
That makes the assumption that when someone clones the jboss-switchyard/quickstarts repo locally, they keep the same name "quickstarts" as their local directory. I did not (I called it switchyard-quickstarts), so in order for the assembly to work for me, I had to create a symbolic link from quickstarts to switchyard-quickstarts (ln -s switchyard-quickstarts quickstarts). Obviously I could have just used the original repo name, but I don't see why we should force this on people.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] Created: (SWITCHYARD-410) JAXB transformation fails when ObjectFactory does not produce JAXBElement<?>
by Keith Babo (JIRA)
JAXB transformation fails when ObjectFactory does not produce JAXBElement<?>
----------------------------------------------------------------------------
Key: SWITCHYARD-410
URL: https://issues.jboss.org/browse/SWITCHYARD-410
Project: SwitchYard
Issue Type: Bug
Components: transformation
Reporter: Keith Babo
Assignee: Tom Fennelly
Fix For: 0.2
JAXBUnmarshalTransformer assumes that the return type for unmarshal will always be a JAXBElement type, but this is not always true. Take the following generated JAXB ObjectFactory:
{noformat}
@XmlRegistry
public class ObjectFactory {
/**
* Create a new ObjectFactory that can be used to create new instances of schema derived classes for package: org.switchyard.demo.openshift
*
*/
public ObjectFactory() {
}
/**
* Create an instance of {@link Order }
*
*/
public Order createOrder() {
return new Order();
}
/**
* Create an instance of {@link OrderAck }
*
*/
public OrderAck createOrderAck() {
return new OrderAck();
}
}
{noformat}
The above creates a ClassCastException in the transformation code. Suggest a slight tweak to the logic in JAXBUnmarshalTransformer :
{noformat}
Object unmarshalledObject = unmarshaller.unmarshal(message.getContent(Source.class));
if (unmarshalledObject instanceof JAXBElement) {
message.setContent(((JAXBElement)unmarshalledObject).getValue());
} else {
message.setContent(unmarshalledObject);
}
{noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] Created: (SWITCHYARD-409) Remove unused required JAXB attributes from transform schema
by Keith Babo (JIRA)
Remove unused required JAXB attributes from transform schema
------------------------------------------------------------
Key: SWITCHYARD-409
URL: https://issues.jboss.org/browse/SWITCHYARD-409
Project: SwitchYard
Issue Type: Bug
Components: transformation
Reporter: Keith Babo
Assignee: Tom Fennelly
Fix For: 0.2
The type and contextPath attributes are not used, but they are required in the schema. We should just remove them if they're not used.
{noformat}
<complexContent>
<extension base="swyd:TransformType">
<attribute name="type" type="trfm:javaTransformType" use="required">
<annotation>
<documentation xml:lang="en">
Transform type.
</documentation>
</annotation>
</attribute>
<attribute name="contextPath" type="string" use="required">
<annotation>
<documentation xml:lang="en">
List of java package names that contain schema
derived class and/or java to schema (JAXB-annotated)
mapped classes.
</documentation>
</annotation>
</attribute>
</extension>
</complexContent>
{noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years