[BPEL SE] MissingSchemaInfoException when assigning values to casted type element
|
View:
New views
11 Messages
—
Rating Filter:
Alert me
|
 |
[BPEL SE] MissingSchemaInfoException when assigning values to casted type element
by babram
::
Rate this Message:
Hi,
I'm using Netbeans 6.1 and Glassfish v2u2/OpenESB v2 and am running into the problem mentioned in the subject. First some snippets from the WSDL/XSD (some content removed for clarity): <wsdl:message name="createAndStartRequestByValueRequest"> <wsdl:part name="parameters" element="om-v1-0:createAndStartRequestByValueRequest" /> </wsdl:message> <element name="createAndStartRequestByValueRequest"> <complexType> <sequence> <element name="requestValue" type="om-v1-0:RequestValue" /> </sequence> </complexType> </element> <complexType name="ServiceOrderValue" > <complexContent> <extension base = "om-v1-0:RequestValue" > <sequence> <element name="serviceOrderItems" type="om-v1-0:ArrayOfServiceOrderItemValue" nillable= "true" minOccurs="0" maxOccurs="1" /> </sequence> </extension> </complexContent> </complexType> Now on to the BPEL process: Variable definition (simplified): <variable name="var" messageType="omWS-v1-0:createAndStartRequestByValueRequest"/> The casting and assignment in the BPEL process (assign name is AssignResponse). This has been done through the UI: <copy> <sxed:editor> <sxed:casts> <sxed:cast path="$var.parameters/ns0:requestValue" type="ns0:ServiceOrderValue" source="to"/> </sxed:casts> </sxed:editor> <from>'some text'</from> <to>$var.parameters/ns0:requestValue/ns0:serviceOrderItems/ns0:item/ns0:service/common-core:describedBy/common-core:item/common-core:characteristic</to> </copy> Everything compiles and deploys fine. However, when running, the following exception occurs (stack trace below): BPCOR-6130:Activity Name is AssignResponse at com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELInterpreter.createVirtualFaultUnit(BPELInterpreter.java:251) at com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELInterpreter.execute(BPELInterpreter.java:203) at com.sun.jbi.engine.bpel.core.bpel.engine.BusinessProcessInstanceThread.execute(BusinessProcessInstanceThread.java:98) at com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELProcessManagerImpl.process(BPELProcessManagerImpl.java:998) at com.sun.jbi.engine.bpel.core.bpel.engine.impl.EngineImpl.process(EngineImpl.java:351) at com.sun.jbi.engine.bpel.core.bpel.engine.impl.EngineImpl.process(EngineImpl.java:1314) at com.sun.jbi.engine.bpel.BPELSEInOutThread.processRequest(BPELSEInOutThread.java:456) at com.sun.jbi.engine.bpel.BPELSEInOutThread.processMsgEx(BPELSEInOutThread.java:266) at com.sun.jbi.engine.bpel.BPELSEInOutThread.run(BPELSEInOutThread.java:191) Caused by: com.sun.xml.transform.sware.MissingSchemaInfoException: Particle not found in the complex type. element={http://ossj.org/xml/OrderManagement/v1-0}serviceOrderItems, complexType={http://ossj.org/xml/OrderManagement/v1-0}RequestValue at com.sun.xml.transform.sware.impl.DOMSorter.checkSortNeeded(DOMSorter.java:167) at com.sun.xml.transform.sware.impl.DOMSorter.checkSortNeeded(DOMSorter.java:244) at com.sun.xml.transform.sware.impl.ReorderTransformerImpl.transform(ReorderTransformerImpl.java:227) at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.AssignUnitImpl.transformDocument(AssignUnitImpl.java:430) at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.AssignUnitImpl.validateOrAndTransformVariable(AssignUnitImpl.java:383) at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.AssignUnitImpl.doAction(AssignUnitImpl.java:321) at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.CodeReUseHelper.executeChildActivities(CodeReUseHelper.java:65) at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.StructuredActivityUnitImpl.executeChildActivities(StructuredActivityUnitImpl.java:193) at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.StructuredActivityUnitImpl.doAction(StructuredActivityUnitImpl.java:93) at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.SequenceUnitImpl.doAction(SequenceUnitImpl.java:95) at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.CodeReUseHelper.executeChildActivities(CodeReUseHelper.java:65) at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.StructuredActivityUnitImpl.executeChildActivities(StructuredActivityUnitImpl.java:193) at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.BPELProcessInstanceImpl.doAction(BPELProcessInstanceImpl.java:643) at com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELInterpreter.execute(BPELInterpreter.java:148) ... 7 more The interesting part is: Caused by: com.sun.xml.transform.sware.MissingSchemaInfoException: Particle not found in the complex type. element={http://ossj.org/xml/OrderManagement/v1-0}serviceOrderItems, complexType={http://ossj.org/xml/OrderManagement/v1-0}RequestValue It looks like the cast hasn't been performed. I'm using the same casting (RequestValue -> ServiceOrderValue) for incoming messages and that works fine. Does anyone have any thoughts on this? Am I doing something wrong? Is it a bug? Many Thanks, Bjorn |
|
|
Re: [BPEL SE] MissingSchemaInfoException when assigning values to casted type element
by elena_mml
::
Rate this Message:
Hi Bjorn,
I had the same exception thrown when my input xml did not match the xsd. (There was an element in my input xml which was not defined in the xsd. The name was actually misspelled.) Make sure that this is not the case for you. Elena.
|
|
|
Re: [BPEL SE] MissingSchemaInfoException when assigning values to casted type element
by Jun Xu-2
::
Rate this Message:
Also, if you are doing type casting, make sure the xsi:type ({http://www.w3.org/2001/XMLSchema-instance}type) attribute is set on the target. Regards, Jun Sun's Open ESB Community (http://open-esb.org) elena_mml wrote: > Hi Bjorn, > > I had the same exception thrown when my input xml did not match the xsd. > (There was an element in my input xml which was not defined in the xsd. The > name was actually misspelled.) Make sure that this is not the case for you. > > Elena. > > > babram wrote: > >> Hi, >> >> I'm using Netbeans 6.1 and Glassfish v2u2/OpenESB v2 and am running into >> the problem mentioned in the subject. >> >> First some snippets from the WSDL/XSD (some content removed for clarity): >> >> <wsdl:message name="createAndStartRequestByValueRequest"> >> <wsdl:part name="parameters" >> element="om-v1-0:createAndStartRequestByValueRequest" /> >> </wsdl:message> >> >> <element name="createAndStartRequestByValueRequest"> >> <complexType> >> <sequence> >> <element name="requestValue" type="om-v1-0:RequestValue" >> /> >> </sequence> >> </complexType> >> </element> >> >> <complexType name="ServiceOrderValue" > >> <complexContent> >> <extension base = "om-v1-0:RequestValue" > >> <sequence> >> <element name="serviceOrderItems" >> type="om-v1-0:ArrayOfServiceOrderItemValue" nillable= "true" minOccurs="0" >> maxOccurs="1" /> >> </sequence> >> </extension> >> </complexContent> >> </complexType> >> >> Now on to the BPEL process: >> >> Variable definition (simplified): >> >> <variable name="var" >> messageType="omWS-v1-0:createAndStartRequestByValueRequest"/> >> >> The casting and assignment in the BPEL process (assign name is >> AssignResponse). This has been done through the UI: >> >> <copy> >> <sxed:editor> >> <sxed:casts> >> <sxed:cast path="$var.parameters/ns0:requestValue" >> type="ns0:ServiceOrderValue" source="to"/> >> </sxed:casts> >> </sxed:editor> >> <from>'some text'</from> >> >> <to>$var.parameters/ns0:requestValue/ns0:serviceOrderItems/ns0:item/ns0:service/common-core:describedBy/common-core:item/common-core:characteristic</to> >> </copy> >> >> Everything compiles and deploys fine. However, when running, the following >> exception occurs (stack trace below): >> >> BPCOR-6130:Activity Name is AssignResponse >> at >> com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELInterpreter.createVirtualFaultUnit(BPELInterpreter.java:251) >> at >> com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELInterpreter.execute(BPELInterpreter.java:203) >> at >> com.sun.jbi.engine.bpel.core.bpel.engine.BusinessProcessInstanceThread.execute(BusinessProcessInstanceThread.java:98) >> at >> com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELProcessManagerImpl.process(BPELProcessManagerImpl.java:998) >> at >> com.sun.jbi.engine.bpel.core.bpel.engine.impl.EngineImpl.process(EngineImpl.java:351) >> at >> com.sun.jbi.engine.bpel.core.bpel.engine.impl.EngineImpl.process(EngineImpl.java:1314) >> at >> com.sun.jbi.engine.bpel.BPELSEInOutThread.processRequest(BPELSEInOutThread.java:456) >> at >> com.sun.jbi.engine.bpel.BPELSEInOutThread.processMsgEx(BPELSEInOutThread.java:266) >> at >> com.sun.jbi.engine.bpel.BPELSEInOutThread.run(BPELSEInOutThread.java:191) >> Caused by: com.sun.xml.transform.sware.MissingSchemaInfoException: >> Particle not found in the complex type. >> element={http://ossj.org/xml/OrderManagement/v1-0}serviceOrderItems, >> complexType={http://ossj.org/xml/OrderManagement/v1-0}RequestValue >> at >> com.sun.xml.transform.sware.impl.DOMSorter.checkSortNeeded(DOMSorter.java:167) >> at >> com.sun.xml.transform.sware.impl.DOMSorter.checkSortNeeded(DOMSorter.java:244) >> at >> com.sun.xml.transform.sware.impl.ReorderTransformerImpl.transform(ReorderTransformerImpl.java:227) >> at >> com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.AssignUnitImpl.transformDocument(AssignUnitImpl.java:430) >> at >> com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.AssignUnitImpl.validateOrAndTransformVariable(AssignUnitImpl.java:383) >> at >> com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.AssignUnitImpl.doAction(AssignUnitImpl.java:321) >> at >> com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.CodeReUseHelper.executeChildActivities(CodeReUseHelper.java:65) >> at >> com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.StructuredActivityUnitImpl.executeChildActivities(StructuredActivityUnitImpl.java:193) >> at >> com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.StructuredActivityUnitImpl.doAction(StructuredActivityUnitImpl.java:93) >> at >> com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.SequenceUnitImpl.doAction(SequenceUnitImpl.java:95) >> at >> com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.CodeReUseHelper.executeChildActivities(CodeReUseHelper.java:65) >> at >> com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.StructuredActivityUnitImpl.executeChildActivities(StructuredActivityUnitImpl.java:193) >> at >> com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.BPELProcessInstanceImpl.doAction(BPELProcessInstanceImpl.java:643) >> at >> com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELInterpreter.execute(BPELInterpreter.java:148) >> ... 7 more >> >> >> The interesting part is: >> >> Caused by: com.sun.xml.transform.sware.MissingSchemaInfoException: >> Particle not found in the complex type. >> element={http://ossj.org/xml/OrderManagement/v1-0}serviceOrderItems, >> complexType={http://ossj.org/xml/OrderManagement/v1-0}RequestValue >> >> It looks like the cast hasn't been performed. >> >> I'm using the same casting (RequestValue -> ServiceOrderValue) for >> incoming messages and that works fine. >> >> Does anyone have any thoughts on this? Am I doing something wrong? Is it a >> bug? >> >> Many Thanks, >> Bjorn >> >> > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@... For additional commands, e-mail: dev-help@... |
|
|
Re: [BPEL SE] MissingSchemaInfoException when assigning values to casted type element
by babram
::
Rate this Message:
Thanks Jun and Elena for your suggestions!
@Elena I was referring to the same element for an incoming request (using casting) and that works but I will verify that there are no spelling errors. @Jun That is a good point you raise. I realise now that I should have been more clear in my initial post on when the problem actually occurs. The issue is occurring when constructing an outgoing request (i.e. invoke action from the BPEL process). With danger of oversimplifying(!): this works (for incoming requests with the subtype ServiceOrderValue present): <copy> <sxed:editor> <sxed:casts> <sxed:cast path="$incomingRequest.parameters/ns0:requestValue" type="ns0:ServiceOrderValue" source="from"/> </sxed:casts> </sxed:editor> <from>$incomingRequest.parameters/ns0:requestValue/ns0:serviceOrderItems/ns0:item/ns0:service/common-core:describedBy/common-core:item/common-core:characteristic</from> <to>$another</to> </copy> but this doesn't (when constructing outgoing requests from "scratch") <copy> <sxed:editor> <sxed:casts> <sxed:cast path="$outgoingRequest.parameters/ns0:requestValue" type="ns0:ServiceOrderValue" source="to"/> </sxed:casts> </sxed:editor> <from>'some text'</from> <to>$outgoingRequest.parameters/ns0:requestValue/ns0:serviceOrderItems/ns0:item/ns0:service/common-core:describedBy/common-core:item/common-core:characteristic</to> </copy> There are probably other factors that causes the error though... Due to time constraint I have solved the problem (temporary) by overriding the message type using the subtype (i.e. no need for casting). However, I will need to revisit the problem at some point... So I'll post updates when I have done more investigation. Thanks, Bjorn
|
|
|
Re: [BPEL SE] MissingSchemaInfoException when assigning values to casted type element
by babram
::
Rate this Message:
Hi Jun,
In a related issue I have the following xsd: <element name="value" type="anyType" nillable= "true" minOccurs="0" maxOccurs="1" /> that BPEL generates the following from: <common-core:value>something</common-core:value> The same XSD is used elsewhere and the type is set accordingly (using JAXB for example) So what I would like BPEL SE to do is (for example as the type will vary): <common-core:value xsi:type="xs:string">something</common-core:value> In response to your email below, is there anyway I can force this attribute for outgoing elements? I've been searching for this to no avail and the BPEL Mapper doesn't seem to provide an option to do this either... I will continue looking for a solution. Ideally BPEL SE would add the type automatically derived from the "from" entry type. Many Thanks, Bjorn
|
|
|
Re: [BPEL SE] MissingSchemaInfoException when assigning values to casted type element
by Jun Xu-2
::
Rate this Message:
Hi Bjorn, You are right. For simple types, the xsi:type attribute should be set automatically by the BPEL engine. For complex type, if the element of the complex type is assigned as a whole, the xsi:type attribute should also be set automatically by the BPEL engine. If the child elements of the complex type are assigned, then the BPEL engine should utilize the type cast information stored by the BPEL editor to set the xsi:type attribute. So basically the type cast information will not only be the design time hint, but also be the runtime hint. Anyway, the xsi:type attribute needs not set explicitly. Unfortunately the engine does not do the above mentioned at this moment. You may file an enhancement request for this. Regards, Jun Sun's Open ESB Community (http://open-esb.org) babram wrote: > Hi Jun, > > In a related issue I have the following xsd: > > <element name="value" type="anyType" nillable= "true" minOccurs="0" > maxOccurs="1" /> > > that BPEL generates the following from: > > <common-core:value>something</common-core:value> > > The same XSD is used elsewhere and the type is set accordingly (using JAXB > for example) > > So what I would like BPEL SE to do is (for example as the type will vary): > > <common-core:value xsi:type="xs:string">something</common-core:value> > > In response to your email below, is there anyway I can force this attribute > for outgoing elements? I've been searching for this to no avail and the BPEL > Mapper doesn't seem to provide an option to do this either... I will > continue looking for a solution. > > Ideally BPEL SE would add the type automatically derived from the "from" > entry type. > > Many Thanks, > Bjorn > > > Jun Xu-2 wrote: > >> Also, if you are doing type casting, make sure the xsi:type >> ({http://www.w3.org/2001/XMLSchema-instance}type) attribute is set on >> the target. >> >> Regards, >> Jun >> >> Sun's Open ESB Community (http://open-esb.org) >> >> >> >> elena_mml wrote: >> >>> Hi Bjorn, >>> >>> I had the same exception thrown when my input xml did not match the xsd. >>> (There was an element in my input xml which was not defined in the xsd. >>> The >>> name was actually misspelled.) Make sure that this is not the case for >>> you. >>> >>> Elena. >>> >>> >>> babram wrote: >>> >>> >>>> Hi, >>>> >>>> I'm using Netbeans 6.1 and Glassfish v2u2/OpenESB v2 and am running into >>>> the problem mentioned in the subject. >>>> >>>> First some snippets from the WSDL/XSD (some content removed for >>>> clarity): >>>> >>>> <wsdl:message name="createAndStartRequestByValueRequest"> >>>> <wsdl:part name="parameters" >>>> element="om-v1-0:createAndStartRequestByValueRequest" /> >>>> </wsdl:message> >>>> >>>> <element name="createAndStartRequestByValueRequest"> >>>> <complexType> >>>> <sequence> >>>> <element name="requestValue" type="om-v1-0:RequestValue" >>>> /> >>>> </sequence> >>>> </complexType> >>>> </element> >>>> >>>> <complexType name="ServiceOrderValue" > >>>> <complexContent> >>>> <extension base = "om-v1-0:RequestValue" > >>>> <sequence> >>>> <element name="serviceOrderItems" >>>> type="om-v1-0:ArrayOfServiceOrderItemValue" nillable= "true" >>>> minOccurs="0" >>>> maxOccurs="1" /> >>>> </sequence> >>>> </extension> >>>> </complexContent> >>>> </complexType> >>>> >>>> Now on to the BPEL process: >>>> >>>> Variable definition (simplified): >>>> >>>> <variable name="var" >>>> messageType="omWS-v1-0:createAndStartRequestByValueRequest"/> >>>> >>>> The casting and assignment in the BPEL process (assign name is >>>> AssignResponse). This has been done through the UI: >>>> >>>> <copy> >>>> <sxed:editor> >>>> <sxed:casts> >>>> <sxed:cast path="$var.parameters/ns0:requestValue" >>>> type="ns0:ServiceOrderValue" source="to"/> >>>> </sxed:casts> >>>> </sxed:editor> >>>> <from>'some text'</from> >>>> >>>> <to>$var.parameters/ns0:requestValue/ns0:serviceOrderItems/ns0:item/ns0:service/common-core:describedBy/common-core:item/common-core:characteristic</to> >>>> </copy> >>>> >>>> Everything compiles and deploys fine. However, when running, the >>>> following >>>> exception occurs (stack trace below): >>>> >>>> BPCOR-6130:Activity Name is AssignResponse >>>> at >>>> com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELInterpreter.createVirtualFaultUnit(BPELInterpreter.java:251) >>>> at >>>> com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELInterpreter.execute(BPELInterpreter.java:203) >>>> at >>>> com.sun.jbi.engine.bpel.core.bpel.engine.BusinessProcessInstanceThread.execute(BusinessProcessInstanceThread.java:98) >>>> at >>>> com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELProcessManagerImpl.process(BPELProcessManagerImpl.java:998) >>>> at >>>> com.sun.jbi.engine.bpel.core.bpel.engine.impl.EngineImpl.process(EngineImpl.java:351) >>>> at >>>> com.sun.jbi.engine.bpel.core.bpel.engine.impl.EngineImpl.process(EngineImpl.java:1314) >>>> at >>>> com.sun.jbi.engine.bpel.BPELSEInOutThread.processRequest(BPELSEInOutThread.java:456) >>>> at >>>> com.sun.jbi.engine.bpel.BPELSEInOutThread.processMsgEx(BPELSEInOutThread.java:266) >>>> at >>>> com.sun.jbi.engine.bpel.BPELSEInOutThread.run(BPELSEInOutThread.java:191) >>>> Caused by: com.sun.xml.transform.sware.MissingSchemaInfoException: >>>> Particle not found in the complex type. >>>> element={http://ossj.org/xml/OrderManagement/v1-0}serviceOrderItems, >>>> complexType={http://ossj.org/xml/OrderManagement/v1-0}RequestValue >>>> at >>>> com.sun.xml.transform.sware.impl.DOMSorter.checkSortNeeded(DOMSorter.java:167) >>>> at >>>> com.sun.xml.transform.sware.impl.DOMSorter.checkSortNeeded(DOMSorter.java:244) >>>> at >>>> com.sun.xml.transform.sware.impl.ReorderTransformerImpl.transform(ReorderTransformerImpl.java:227) >>>> at >>>> com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.AssignUnitImpl.transformDocument(AssignUnitImpl.java:430) >>>> at >>>> com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.AssignUnitImpl.validateOrAndTransformVariable(AssignUnitImpl.java:383) >>>> at >>>> com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.AssignUnitImpl.doAction(AssignUnitImpl.java:321) >>>> at >>>> com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.CodeReUseHelper.executeChildActivities(CodeReUseHelper.java:65) >>>> at >>>> com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.StructuredActivityUnitImpl.executeChildActivities(StructuredActivityUnitImpl.java:193) >>>> at >>>> com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.StructuredActivityUnitImpl.doAction(StructuredActivityUnitImpl.java:93) >>>> at >>>> com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.SequenceUnitImpl.doAction(SequenceUnitImpl.java:95) >>>> at >>>> com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.CodeReUseHelper.executeChildActivities(CodeReUseHelper.java:65) >>>> at >>>> com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.StructuredActivityUnitImpl.executeChildActivities(StructuredActivityUnitImpl.java:193) >>>> at >>>> com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.BPELProcessInstanceImpl.doAction(BPELProcessInstanceImpl.java:643) >>>> at >>>> com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELInterpreter.execute(BPELInterpreter.java:148) >>>> ... 7 more >>>> >>>> >>>> The interesting part is: >>>> >>>> Caused by: com.sun.xml.transform.sware.MissingSchemaInfoException: >>>> Particle not found in the complex type. >>>> element={http://ossj.org/xml/OrderManagement/v1-0}serviceOrderItems, >>>> complexType={http://ossj.org/xml/OrderManagement/v1-0}RequestValue >>>> >>>> It looks like the cast hasn't been performed. >>>> >>>> I'm using the same casting (RequestValue -> ServiceOrderValue) for >>>> incoming messages and that works fine. >>>> >>>> Does anyone have any thoughts on this? Am I doing something wrong? Is it >>>> a >>>> bug? >>>> >>>> Many Thanks, >>>> Bjorn >>>> >>>> >>>> >>> >>> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscribe@... >> For additional commands, e-mail: dev-help@... >> >> >> >> > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@... For additional commands, e-mail: dev-help@... |
|
|
Re: [BPEL SE] MissingSchemaInfoException when assigning values to casted type element
by Jun Xu-2
::
Rate this Message:
Hi Bjorn, Although the BPEL engine does not set xsi:type automatically and you could not find any design time support for setting this attribute, as a workaround, you can always hand code the BPEL source to set this attribute. This way, at least you can workaround the MissingSchemaInfoException issue. Regards, Jun Sun's Open ESB Community (http://open-esb.org) Jun Xu wrote: > > Hi Bjorn, > > You are right. For simple types, the xsi:type attribute should be set > automatically by the BPEL engine. For complex type, if the element of > the complex type is assigned as a whole, the xsi:type attribute should > also be set automatically by the BPEL engine. If the child elements > of the complex type are assigned, then the BPEL engine should utilize > the type cast information stored by the BPEL editor to set the > xsi:type attribute. So basically the type cast information will not > only be the design time hint, but also be the runtime hint. Anyway, > the xsi:type attribute needs not set explicitly. Unfortunately the > engine does not do the above mentioned at this moment. You may file > an enhancement request for this. > > Regards, > Jun > > Sun's Open ESB Community (http://open-esb.org) > > > > babram wrote: >> Hi Jun, >> >> In a related issue I have the following xsd: >> >> <element name="value" type="anyType" nillable= "true" minOccurs="0" >> maxOccurs="1" /> >> >> that BPEL generates the following from: >> >> <common-core:value>something</common-core:value> >> >> The same XSD is used elsewhere and the type is set accordingly (using >> JAXB >> for example) >> >> So what I would like BPEL SE to do is (for example as the type will >> vary): >> >> <common-core:value xsi:type="xs:string">something</common-core:value> >> >> In response to your email below, is there anyway I can force this >> attribute >> for outgoing elements? I've been searching for this to no avail and >> the BPEL >> Mapper doesn't seem to provide an option to do this either... I will >> continue looking for a solution. >> >> Ideally BPEL SE would add the type automatically derived from the "from" >> entry type. >> >> Many Thanks, >> Bjorn >> >> >> Jun Xu-2 wrote: >> >>> Also, if you are doing type casting, make sure the xsi:type >>> ({http://www.w3.org/2001/XMLSchema-instance}type) attribute is set >>> on the target. >>> >>> Regards, >>> Jun >>> >>> Sun's Open ESB Community (http://open-esb.org) >>> >>> >>> >>> elena_mml wrote: >>> >>>> Hi Bjorn, >>>> >>>> I had the same exception thrown when my input xml did not match the >>>> xsd. >>>> (There was an element in my input xml which was not defined in the >>>> xsd. >>>> The >>>> name was actually misspelled.) Make sure that this is not the case for >>>> you. >>>> >>>> Elena. >>>> >>>> babram wrote: >>>> >>>>> Hi, >>>>> >>>>> I'm using Netbeans 6.1 and Glassfish v2u2/OpenESB v2 and am >>>>> running into >>>>> the problem mentioned in the subject. >>>>> >>>>> First some snippets from the WSDL/XSD (some content removed for >>>>> clarity): >>>>> >>>>> <wsdl:message name="createAndStartRequestByValueRequest"> >>>>> <wsdl:part name="parameters" >>>>> element="om-v1-0:createAndStartRequestByValueRequest" /> >>>>> </wsdl:message> >>>>> >>>>> <element name="createAndStartRequestByValueRequest"> >>>>> <complexType> >>>>> <sequence> >>>>> <element name="requestValue" >>>>> type="om-v1-0:RequestValue" /> >>>>> </sequence> >>>>> </complexType> >>>>> </element> >>>>> >>>>> <complexType name="ServiceOrderValue" > >>>>> <complexContent> >>>>> <extension base = "om-v1-0:RequestValue" > >>>>> <sequence> >>>>> <element name="serviceOrderItems" >>>>> type="om-v1-0:ArrayOfServiceOrderItemValue" nillable= "true" >>>>> minOccurs="0" >>>>> maxOccurs="1" /> >>>>> </sequence> >>>>> </extension> >>>>> </complexContent> >>>>> </complexType> >>>>> >>>>> Now on to the BPEL process: >>>>> >>>>> Variable definition (simplified): >>>>> >>>>> <variable name="var" >>>>> messageType="omWS-v1-0:createAndStartRequestByValueRequest"/> >>>>> >>>>> The casting and assignment in the BPEL process (assign name is >>>>> AssignResponse). This has been done through the UI: >>>>> >>>>> <copy> >>>>> <sxed:editor> >>>>> <sxed:casts> >>>>> <sxed:cast path="$var.parameters/ns0:requestValue" >>>>> type="ns0:ServiceOrderValue" source="to"/> >>>>> </sxed:casts> >>>>> </sxed:editor> >>>>> <from>'some text'</from> >>>>> >>>>> <to>$var.parameters/ns0:requestValue/ns0:serviceOrderItems/ns0:item/ns0:service/common-core:describedBy/common-core:item/common-core:characteristic</to> >>>>> >>>>> </copy> >>>>> >>>>> Everything compiles and deploys fine. However, when running, the >>>>> following >>>>> exception occurs (stack trace below): >>>>> >>>>> BPCOR-6130:Activity Name is AssignResponse >>>>> at >>>>> com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELInterpreter.createVirtualFaultUnit(BPELInterpreter.java:251) >>>>> >>>>> at >>>>> com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELInterpreter.execute(BPELInterpreter.java:203) >>>>> >>>>> at >>>>> com.sun.jbi.engine.bpel.core.bpel.engine.BusinessProcessInstanceThread.execute(BusinessProcessInstanceThread.java:98) >>>>> >>>>> at >>>>> com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELProcessManagerImpl.process(BPELProcessManagerImpl.java:998) >>>>> >>>>> at >>>>> com.sun.jbi.engine.bpel.core.bpel.engine.impl.EngineImpl.process(EngineImpl.java:351) >>>>> >>>>> at >>>>> com.sun.jbi.engine.bpel.core.bpel.engine.impl.EngineImpl.process(EngineImpl.java:1314) >>>>> >>>>> at >>>>> com.sun.jbi.engine.bpel.BPELSEInOutThread.processRequest(BPELSEInOutThread.java:456) >>>>> >>>>> at >>>>> com.sun.jbi.engine.bpel.BPELSEInOutThread.processMsgEx(BPELSEInOutThread.java:266) >>>>> >>>>> at >>>>> com.sun.jbi.engine.bpel.BPELSEInOutThread.run(BPELSEInOutThread.java:191) >>>>> >>>>> Caused by: com.sun.xml.transform.sware.MissingSchemaInfoException: >>>>> Particle not found in the complex type. >>>>> element={http://ossj.org/xml/OrderManagement/v1-0}serviceOrderItems, >>>>> complexType={http://ossj.org/xml/OrderManagement/v1-0}RequestValue >>>>> at >>>>> com.sun.xml.transform.sware.impl.DOMSorter.checkSortNeeded(DOMSorter.java:167) >>>>> >>>>> at >>>>> com.sun.xml.transform.sware.impl.DOMSorter.checkSortNeeded(DOMSorter.java:244) >>>>> >>>>> at >>>>> com.sun.xml.transform.sware.impl.ReorderTransformerImpl.transform(ReorderTransformerImpl.java:227) >>>>> >>>>> at >>>>> com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.AssignUnitImpl.transformDocument(AssignUnitImpl.java:430) >>>>> >>>>> at >>>>> com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.AssignUnitImpl.validateOrAndTransformVariable(AssignUnitImpl.java:383) >>>>> >>>>> at >>>>> com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.AssignUnitImpl.doAction(AssignUnitImpl.java:321) >>>>> >>>>> at >>>>> com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.CodeReUseHelper.executeChildActivities(CodeReUseHelper.java:65) >>>>> >>>>> at >>>>> com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.StructuredActivityUnitImpl.executeChildActivities(StructuredActivityUnitImpl.java:193) >>>>> >>>>> at >>>>> com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.StructuredActivityUnitImpl.doAction(StructuredActivityUnitImpl.java:93) >>>>> >>>>> at >>>>> com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.SequenceUnitImpl.doAction(SequenceUnitImpl.java:95) >>>>> >>>>> at >>>>> com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.CodeReUseHelper.executeChildActivities(CodeReUseHelper.java:65) >>>>> >>>>> at >>>>> com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.StructuredActivityUnitImpl.executeChildActivities(StructuredActivityUnitImpl.java:193) >>>>> >>>>> at >>>>> com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.BPELProcessInstanceImpl.doAction(BPELProcessInstanceImpl.java:643) >>>>> >>>>> at >>>>> com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELInterpreter.execute(BPELInterpreter.java:148) >>>>> >>>>> ... 7 more >>>>> >>>>> >>>>> The interesting part is: >>>>> >>>>> Caused by: com.sun.xml.transform.sware.MissingSchemaInfoException: >>>>> Particle not found in the complex type. >>>>> element={http://ossj.org/xml/OrderManagement/v1-0}serviceOrderItems, >>>>> complexType={http://ossj.org/xml/OrderManagement/v1-0}RequestValue >>>>> >>>>> It looks like the cast hasn't been performed. >>>>> >>>>> I'm using the same casting (RequestValue -> ServiceOrderValue) for >>>>> incoming messages and that works fine. >>>>> >>>>> Does anyone have any thoughts on this? Am I doing something wrong? >>>>> Is it >>>>> a >>>>> bug? >>>>> >>>>> Many Thanks, >>>>> Bjorn >>>>> >>>>> >>>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: dev-unsubscribe@... >>> For additional commands, e-mail: dev-help@... >>> >>> >>> >>> >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@... For additional commands, e-mail: dev-help@... |
|
|
Re: [BPEL SE] MissingSchemaInfoException when assigning values to casted type element
by babram
::
Rate this Message:
|
