[JBoss-user] [JBoss jBPM] - Re: Problem during deploying my own bpel process in jbpm bpe

2005-12-17 Thread fabricio.nogueira 
Alejandro,

thanks for your reply, the  ant deploy-definition command worked now. I'm going 
to folow the next steps now. But, It's weird because those files were all 
generated by Oracle JDeveloper Bpel Designer and work with Oracle Business 
Process Manager deployment.

Maybe, this is a stupid question. But what do you mean with This makes sense 
because your process does not receive through the myEcho partner link. Are you 
saying that the service won't return anything to the process? Because, myEcho 
service returns a greeting message to the process. As you can see in the jws:


  | public class myEcho {
  | 
  | public String echo(String s){
  | return Hello,  + s + . Nice to meet you!;
  | }
  | 
  | }
  | 

Am I making a misunderstanding about what you said?

Thanks in advance,

Fabrício.




View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=3913236#3913236

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3913236


---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37alloc_id865op=click
___
JBoss-user mailing list
JBoss-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-user

[JBoss-user] [JBoss jBPM] - Re: Problem during deploying my own bpel process in jbpm bpe

2005-12-17 Thread [EMAIL PROTECTED] 
anonymous wrote : It's weird because those files were all generated by Oracle 
JDeveloper Bpel Designer and work with Oracle Business Process Manager 
deployment
Quite weird. The BPEL spec is clear in this point. From section 7.2:
anonymous wrote : The role of the business process itself is indicated by the 
attribute myRole and the role of the partner is indicated by the attribute 
partnerRole. In the degenerate case where a partnerLinkType has only one role, 
one of these attributes is omitted as appropriate

anonymous wrote : what do you mean with This makes sense because your process 
does not receive through the myEcho partner link
I meant asynchronous reception: using the partner link in a receive activity to 
get a separate response to a previous request placed with an one-way invoke 
activity. Such an interaction pattern is quite different from a 
request/response invoke activity, as it requires the process to expose a 
callback interface to the partner service.

View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=3913262#3913262

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3913262


---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
___
JBoss-user mailing list
JBoss-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-user

[JBoss-user] [JBoss jBPM] - Re: Problem during deploying my own bpel process in jbpm bpe

2005-12-16 Thread [EMAIL PROTECTED] 
This is not a deployment problem. The BPEL document  contains an error. Take a 
look at /process/partnerLinks/partnerLink[2]:
 partnerLinks
  | partnerLink name=client partnerLinkType=client:myEcho 
myRole=myEchoProvider/
  | partnerLink name=myEcho partnerRole=myEcho_Role 
myRole=myEcho_Role partnerLinkType=ns1:myEcho_PL/
  |   /partnerLinks
It defines a bidirectional relationship between the process and an external 
service. Now follow the partner link type reference to 
{http://localhost:8081/axis/myEcho.jws}myEcho_PL:
plnk:partnerLinkType name=myEcho_PL
  | plnk:role name=myEcho_Role
  | plnk:portType name=impl:myEcho/
  | /plnk:role
  | /plnk:partnerLinkType
It declares an unidirectional relationship, since it contains only one role 
subelement. This makes sense because your process does not receive through the 
myEcho partner link. In this situation, the partner link has no reason to 
assign a role to the BPEL service. Therefore, you should drop the myRole 
attribute.

View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=3913222#3913222

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3913222


---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
___
JBoss-user mailing list
JBoss-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-user

[JBoss-user] [JBoss jBPM] - Re: Problem during deploying my own bpel process in jbpm bpe

2005-12-15 Thread [EMAIL PROTECTED] 
First, let me elaborate on the error message. /process/variables/variable[3] is 
the XPath to the offending element:
variables
  | variable name=inputVariable 
messageType=client:myEchoRequestMessage/
  | variable name=outputVariable 
messageType=client:myEchoResponseMessage/
  | variable name=Invoke_1_echo_InputVariable 
messageType=ns1:echoRequest/
  | variable name=Invoke_1_echo_OutputVariable 
messageType=ns1:echoResponse/
  |   /variables
By message type not found I mean ns1:echoRequest does not exist in the WSDL 
documents known to the process deployer (referenced in file 
bpel-definition.xml). 

Going to your WSDL document, I see a myEchoRequestMessage, but not a 
echoRequest. Also, the namespace URI associated with ns1 in the process 
document (http://localhost:8081/axis/myEcho.jws) does not match the target 
namespace of your WSDL definitions(http://xmlns.oracle.com/myEcho). Check it 
out.

View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=3912833#3912833

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3912833


---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
___
JBoss-user mailing list
JBoss-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-user

[JBoss-user] [JBoss jBPM] - Re: Problem during deploying my own bpel process in jbpm bpe

2005-12-15 Thread fabricio.nogueira 
Thanks Alejandro,

I'll check it out.

View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=3912863#3912863

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3912863


---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
___
JBoss-user mailing list
JBoss-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-user

[JBoss-user] [JBoss jBPM] - Re: Problem during deploying my own bpel process in jbpm bpe

2005-12-15 Thread [EMAIL PROTECTED] 
Fabricio,

I'm very interested in verifying our BPEL extension is able to run processes 
designed in other products' editors. Let me know your results.

View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=3912940#3912940

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3912940


---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
___
JBoss-user mailing list
JBoss-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-user

[JBoss-user] [JBoss jBPM] - Re: Problem during deploying my own bpel process in jbpm bpe

2005-12-15 Thread fabricio.nogueira 
Ok Alejandro,

I'll post all my success and insuccess with this experience.

Thanks,

Fabricio.

View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=3912952#3912952

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3912952


---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
___
JBoss-user mailing list
JBoss-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-user

[JBoss-user] [JBoss jBPM] - Re: Problem during deploying my own bpel process in jbpm bpe

2005-12-15 Thread fabricio.nogueira 
Hello Alejandro and Jbpm users,

I think I don't know how to deploy this bpel process. I'll try to explain how 
JDeveloper Bpel designer created the files. When I modelled my bpel process I 
noticed that a wsdl file for the web service that I'm calling was generated and 
I didn't put it in my previous bpel-definition.xml file. Now I have my myEcho 
folders structured as:

  | myEcho
  |hibernate.properties
  |jndi.properties
  |log4j.properties
  |build.properties
  |build.xml
  |[definition]
  |   bpel-definition.xml
  |   myEcho.bpel
  |   myEcho.wsdl
  |   myEcho1.wsdl
  | 

And the files are:

bpel-definition.xml

  | !-- specifies the location of the process definition --
  | bpelDefinition location=myEcho.bpel xmlns=http://jbpm.org/bpel;
  |   xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
  |   xsi:schemaLocation=http://jbpm.org/bpel
  |   http://jbpm.org/bpel/bpel_definition_1_0.xsd;
  |   
  |   !-- makes WSDL interface elements available to the process --
  |   imports
  | wsdl namespace=http://xmlns.oracle.com/myEcho; 
location=myEcho.wsdl/
  | wsdl namespace=http://localhost:8081/axis/myEcho.jws; 
location=myEcho1.wsdl/
  |   /imports
  |   
  | /bpelDefinition
  | 

myEcho.bpel file is:


  | !--
  |   
/
 
  |   // Oracle JDeveloper BPEL Designer 
  |   // 
  |   // Created: Thu Dec 08 22:17:32 BRST 2005
  |   // Author:  Fasilva
  |   // Purpose: Synchronous BPEL Process
  |   
/
 
  | --
  | process name=myEcho targetNamespace=http://xmlns.oracle.com/myEcho; 
xmlns=http://schemas.xmlsoap.org/ws/2003/03/business-process/; 
xmlns:xsd=http://www.w3.org/2001/XMLSchema; 
xmlns:bpws=http://schemas.xmlsoap.org/ws/2003/03/business-process/; 
xmlns:xp20=http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.Xpath20;
 xmlns:ns1=http://localhost:8081/axis/myEcho.jws; 
xmlns:ldap=http://schemas.oracle.com/xpath/extension/ldap; 
xmlns:bpelx=http://schemas.oracle.com/bpel/extension; 
xmlns:client=http://xmlns.oracle.com/myEcho; 
xmlns:ora=http://schemas.oracle.com/xpath/extension; 
xmlns:orcl=http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.ExtFunc;
  | 
  | !-- = --
  | !-- PARTNERLINKS --
  | !-- List of services participating in this BPEL process --
  | !-- = --
  | 
  |   partnerLinks
  | partnerLink name=client partnerLinkType=client:myEcho 
myRole=myEchoProvider/
  | partnerLink myRole=myEcho_Role name=myEcho 
partnerRole=myEcho_Role partnerLinkType=ns1:myEcho_PL/
  |   /partnerLinks
  | 
  | !-- = --
  | !-- VARIABLES --
  | !-- List of messages and XML documents used within this BPEL process  --
  | !-- = --
  | 
  |   variables!-- Reference to the message passed as input during 
initiation --
  | variable name=inputVariable 
messageType=client:myEchoRequestMessage/
  | 
  | !-- Reference to the message that will be returned to the requester --
  | 
  | variable name=outputVariable 
messageType=client:myEchoResponseMessage/
  | variable name=Invoke_1_echo_InputVariable 
messageType=ns1:echoRequest/
  | variable name=Invoke_1_echo_OutputVariable 
messageType=ns1:echoResponse/
  |   /variables
  | 
  | !-- = --
  | !-- ORCHESTRATION LOGIC --
  | !-- Set of activities coordinating the flow of messages across the --
  | !-- services integrated within this business process --
  | !-- = --
  | 
  |   sequence name=main
  | !-- 
  |  Receive input from requestor. 
  |  Note: This maps to operation defined in myEcho.wsdl
  | --
  | receive name=receiveInput partnerLink=client 
portType=client:myEcho operation=process variable=inputVariable 
createInstance=yes/
  | 
  | !-- Generate reply to synchronous request --
  | 
  | scope name=Scope_1
  |   sequence name=Sequence_1
  | assign name=InEcho
  |   copy
  | from variable=inputVariable part=payload 
query=/client:myEchoProcessRequest/client:input/
  | to variable=Invoke_1_echo_InputVariable part=s/
  |   /copy
  | /assign
  | invoke name=myEcho partnerLink=myEcho portType=ns1:myEcho 
operation=echo inputVariable=Invoke_1_echo_InputVariable 
outputVariable=Invoke_1_echo_OutputVariable/
  | assign name=EchoOut
  |   copy
  | from variable=Invoke_1_echo_OutputVariable