Igor JStarter [http://community.jboss.org/people/izgur] created the discussion
"BPEL editor - INVOKE problem" To view the discussion, visit: http://community.jboss.org/message/570235#570235 -------------------------------------------------------------- I'm using Jboss AS 5.1, ESB 4,8 and RiftSaw 2.1 in eclipse iwth JbossTools... When I try to change code by hand, the bpel suddenly doesn't know what my external web services methods and its parameters are... The partner role deletes or something like that. And I'm in a circle no matter where I change anything... I'M TRYING DO TO THIS GRAFICALLY.. When i add the invoke element to my bpel, add 2 assign, now it always messes up my artifacts.wsdl. Can somebody tell me why the INVOKE element in BPEL change my artifacts WSDL from: <?xml version="1.0"?> <definitions name="bpellGlassPojo" targetNamespace=" http://samples/bpellGlassPojo http://samples/bpellGlassPojo"; xmlns:tns=" http://samples/bpellGlassPojo http://samples/bpellGlassPojo"; xmlns:plnk=" http://docs.oasis-open.org/wsbpel/2.0/plnktype http://docs.oasis-open.org/wsbpel/2.0/plnktype"; xmlns=" http://schemas.xmlsoap.org/wsdl/ http://schemas.xmlsoap.org/wsdl/"; xmlns:wsdl=" http://glasspojo.si/ http://glasspojo.si"; > <!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ TYPE DEFINITION - List of types participating in this BPEL process The BPEL Designer will generate default request and response types but you can define or import any XML Schema type and use them as part of the message types. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ --> <plnk:partnerLinkType name="GlassFishLinkType"> <plnk:role name="GlassFishProvider" portType="wsdl:GlassPojoWS"/> </plnk:partnerLinkType> <import location="GlassPojoWSService.wsdl" namespace=" http://glasspojo.si/ http://glasspojo.si/"/> <types> <schema attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace=" http://samples/bpellGlassPojo http://samples/bpellGlassPojo"; xmlns=" http://www.w3.org/2001/XMLSchema http://www.w3.org/2001/XMLSchema";> <element name="bpellGlassPojoRequest"> <complexType> <sequence> <element name="ServiceID" type="int" /> <element name="sUserName" type="string"></element> <element name="sPassword" type="string"></element> </sequence> </complexType> </element> <element name="bpellGlassPojoResponse"> <complexType> <sequence> <element name="result" type="string"/> </sequence> </complexType> </element> </schema> </types> <!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ MESSAGE TYPE DEFINITION - Definition of the message types used as part of the port type defintions ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ --> <message name="bpellGlassPojoRequestMessage"> <part name="payload" element="tns:bpellGlassPojoRequest"/> </message> <message name="bpellGlassPojoResponseMessage"> <part name="payload" element="tns:bpellGlassPojoResponse"/> </message> <!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ PORT TYPE DEFINITION - A port type groups a set of operations into a logical service unit. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ --> <!-- portType implemented by the bpellGlassPojo BPEL process --> <portType name="bpellGlassPojo"> <operation name="process"> <input message="tns:bpellGlassPojoRequestMessage" /> <output message="tns:bpellGlassPojoResponseMessage"/> </operation> </portType> <!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ PARTNER LINK TYPE DEFINITION ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ --> <plnk:partnerLinkType name="bpellGlassPojo"> <plnk:role name="bpellGlassPojoProvider" portType="tns:bpellGlassPojo"/> </plnk:partnerLinkType> </definitions> TO... <?xml version="1.0" encoding="UTF-8" standalone="no"?> <definitions xmlns=" http://schemas.xmlsoap.org/wsdl/ http://schemas.xmlsoap.org/wsdl/"; xmlns:plnk=" http://docs.oasis-open.org/wsbpel/2.0/plnktype http://docs.oasis-open.org/wsbpel/2.0/plnktype"; xmlns:tns=" http://samples/bpellGlassPojo http://samples/bpellGlassPojo"; xmlns:vprop=" http://docs.oasis-open.org/wsbpel/2.0/varprop http://docs.oasis-open.org/wsbpel/2.0/varprop"; xmlns:wsdl=" http://glasspojo.si/ http://glasspojo.si"; xmlns:wsdl1=" http://glasspojo.si/ http://glasspojo.si/"; name="bpellGlassPojo" targetNamespace=" http://samples/bpellGlassPojo http://samples/bpellGlassPojo";> <!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ TYPE DEFINITION - List of types participating in this BPEL process The BPEL Designer will generate default request and response types but you can define or import any XML Schema type and use them as part of the message types. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ --> <plnk:partnerLinkType name="GlassFishLinkType"> <plnk:role name="GlassFishProvider" portType="wsdl:GlassPojoWS"/> </plnk:partnerLinkType> <plnk:partnerLinkType name="SecondGlassFishType"> <plnk:role name="GlassFishProv" portType="wsdl1:GlassPojoWS"/> </plnk:partnerLinkType> <import location="GlassPojoWSService.wsdl" namespace=" http://glasspojo.si/ http://glasspojo.si/"/> <types> <schema xmlns=" http://www.w3.org/2001/XMLSchema http://www.w3.org/2001/XMLSchema"; attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace=" http://samples/bpellGlassPojo http://samples/bpellGlassPojo";> <element name="bpellGlassPojoRequest"> <complexType> <sequence> <element name="ServiceID" type="int"/> <element name="sUserName" type="string"/> <element name="sPassword" type="string"/> </sequence> </complexType> </element> <element name="bpellGlassPojoResponse"> <complexType> <sequence> <element name="result" type="string"/> </sequence> </complexType> </element> </schema> </types> <!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ MESSAGE TYPE DEFINITION - Definition of the message types used as part of the port type defintions ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ --> <message name="bpellGlassPojoRequestMessage"> <part element="tns:bpellGlassPojoRequest" name="payload"/> </message> <message name="bpellGlassPojoResponseMessage"> <part element="tns:bpellGlassPojoResponse" name="payload"/> </message> <!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ PORT TYPE DEFINITION - A port type groups a set of operations into a logical service unit. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ --> <!-- portType implemented by the bpellGlassPojo BPEL process --> <portType name="bpellGlassPojo"> <operation name="process"> <input message="tns:bpellGlassPojoRequestMessage"/> <output message="tns:bpellGlassPojoResponseMessage"/> </operation> </portType> <!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ PARTNER LINK TYPE DEFINITION ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ --> <plnk:partnerLinkType name="bpellGlassPojo"> <plnk:role name="bpellGlassPojoProvider" portType="tns:bpellGlassPojo"/> </plnk:partnerLinkType> </definitions> And suddently my Projects doesn't know that the input for my main artifacts wsdl in myprojectrequest with 2 strings and the response myprojectresponse with one string. Instead I get just ... *element or type undefined* -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/570235#570235] Start a new discussion in JBoss Tools at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2128]
_______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
