Issue For BPEL SE When Using Real Web Service And Complex Type Message Definition

[leod]

Hello all ,

I want to have your opinion before sending an issue for bpel se.

You find in attachements two project :

- one project who work correctly with simple bpel in casa who call a real web service with input and output message define with simple type string (soap rpc literal)

- one project (the same) but input and output message define by xml shema , type complex (soap document literal)

I have the same problem with exception , if that is not a string , it's impossible to catch it

Thanks in advance if you have response

WORK.zip

NOT_WORK.zip

PS: I work with jdk1.6.0_11 and glassfishESB build : 200905151554

[leod]

up

leod wrote:

Hello all ,

I want to have your opinion before sending an issue for bpel se.

You find in attachements two project :

- one project who work correctly with simple bpel in casa who call a real web service with input and output message define with simple type string (soap rpc literal)

- one project (the same) but input and output message define by xml shema , type complex (soap document literal)

I have the same problem with exception , if that is not a string , it's impossible to catch it

Thanks in advance if you have response

WORK.zip

NOT_WORK.zip

PS: I work with jdk1.6.0_11 and glassfishESB build : 200905151554

[Senthil Prabhu]

Some javascript/style in this post has been disabled (why?)

Hi leod
I tried the two attached projects and there seems to be an issue.

1) When you use "String" parameters in the WebApplication Webservice and call it from BPEL, the project works fine.

2) When you use "XML Schema" based parameters in the WebApp Webservice and call it from BPEL, the project throws Selection Failure exception.
During initial analysis, I found that the message that reached the WebApp Webservice has null values.  The following line of code

    public org.netbeans.xml.schema.xmlschematest.Output wsdlTESTOperation(org.netbeans.xml.schema.xmlschematest.Input part1) {
        System.out.println(part1.getA()+part1.getB());

produces the following output in the server logs

[#|2009-10-07T18:03:10.062+0530|INFO|sun-appserver2.1|javax.enterprise.system.stream.out|_ThreadID=26;_ThreadName=httpSSLWorkerThread-8080-1;|
nullnull|#]

I'm investigating further and will let you know about the progress.

--
Senthil.

leod wrote:

up


leod wrote:
  

Hello all ,

I want to have your opinion before sending an issue for bpel se.

You find in attachements two project :

- one project who work correctly with simple bpel in casa who call a real
web service with input and output message define with simple type string
(soap rpc literal)

- one project (the same) but input and output message define by xml shema
, type complex (soap document literal)

I have the same problem with exception , if that is not a string , it's
impossible to catch it

Thanks in advance if you have response

 http://n2.nabble.com/file/n3741927/WORK.zip WORK.zip 

 http://n2.nabble.com/file/n3741927/NOT_WORK.zip NOT_WORK.zip 

PS: I work with jdk1.6.0_11 and glassfishESB build : 200905151554

    

[leod]

that is exactly that
when i use xml shema it always return null and i dont know why

--- En date de : Mer 7.10.09, Senthil Prabhu (via Nabble) <[hidden email]> a écrit :

De: Senthil Prabhu (via Nabble) <[hidden email]>
Objet: Re: Issue For BPEL SE When Using Real Web Service And Complex Type Message Definition
À: "leod" <[hidden email]>
Date: Mercredi 7 Octobre 2009, 14h50

Hi leod
I tried the two attached projects and there seems to be an issue.

1) When you use "String" parameters in the WebApplication Webservice and call it from BPEL, the project works fine.

2) When you use "XML Schema" based parameters in the WebApp Webservice and call it from BPEL, the project throws Selection Failure exception.
During initial analysis, I found that the message that reached the WebApp Webservice has null values.  The following line of code

    public org.netbeans.xml.schema.xmlschematest.Output wsdlTESTOperation(org.netbeans.xml.schema.xmlschematest.Input part1) {
        System.out.println(part1.getA()+part1.getB());

produces the following output in the server logs

[#|2009-10-07T18:03:10.062+0530|INFO|sun-appserver2.1|javax.enterprise.system.stream.out|_ThreadID=26;_ThreadName=httpSSLWorkerThread-8080-1;|
nullnull|#]

I'm investigating further and will let you know about the progress.

--
Senthil.

leod wrote:

up


leod wrote:
  

Hello all ,

I want to have your opinion before sending an issue for bpel se.

You find in attachements two project :

- one project who work correctly with simple bpel in casa who call a real
web service with input and output message define with simple type string
(soap rpc literal)

- one project (the same) but input and output message define by xml shema
, type complex (soap document literal)

I have the same problem with exception , if that is not a string , it's
impossible to catch it

Thanks in advance if you have response

 http://n2.nabble.com/file/n3741927/WORK.zip WORK.zip 

 http://n2.nabble.com/file/n3741927/NOT_WORK.zip NOT_WORK.zip
 

PS: I work with jdk1.6.0_11 and glassfishESB build : 200905151554

    

---

View message @ http://n2.nabble.com/Issue-For-BPEL-SE-When-Using-Real-Web-Service-And-Complex-Type-Message-Definition-tp3741927p3781631.html
To unsubscribe from Re: Issue For BPEL SE When Using Real Web Service And Complex Type Message Definition, click here.

[leod]

Hi Senthil , Do you have news about my problem ?

It's very important for my job

I ask you an other question during monday

 

regards

 

--- En date de : Mer 7.10.09, Senthil Prabhu (via Nabble) <[hidden email]> a écrit :

De: Senthil Prabhu (via Nabble) <[hidden email]>
Objet: Re: Issue For BPEL SE When Using Real Web Service And Complex Type Message Definition
À: "leod" <[hidden email]>
Date: Mercredi 7 Octobre 2009, 14h50

Hi leod
I tried the two attached projects and there seems to be an issue.

1) When you use "String" parameters in the WebApplication Webservice and call it from BPEL, the project works fine.

2) When you use "XML Schema" based parameters in the WebApp Webservice and call it from BPEL, the project throws Selection Failure exception.
During initial analysis, I found that the message that reached the WebApp Webservice has null values.  The following line of code

    public org.netbeans.xml.schema.xmlschematest.Output wsdlTESTOperation(org.netbeans.xml.schema.xmlschematest.Input part1) {
        System.out.println(part1.getA()+part1.getB());

produces the following output in the server logs

[#|2009-10-07T18:03:10.062+0530|INFO|sun-appserver2.1|javax.enterprise.system.stream.out|_ThreadID=26;_ThreadName=httpSSLWorkerThread-8080-1;|
nullnull|#]

I'm investigating further and will let you know about the progress.

--
Senthil.

leod wrote:

up


leod wrote:
  

Hello all ,

I want to have your opinion before sending an issue for bpel se.

You find in attachements two project :

- one project who work correctly with simple bpel in casa who call a real
web service with input and output message define with simple type string
(soap rpc literal)

- one project (the same) but input and output message define by xml shema
, type complex (soap document literal)

I have the same problem with exception , if that is not a string , it's
impossible to catch it

Thanks in advance if you have response

 http://n2.nabble.com/file/n3741927/WORK.zip WORK.zip 

 http://n2.nabble.com/file/n3741927/NOT_WORK.zip NOT_WORK.zip 

PS: I work with jdk1.6.0_11 and glassfishESB build : 200905151554

    

---

View message @ http://n2.nabble.com/Issue-For-BPEL-SE-When-Using-Real-Web-Service-And-Complex-Type-Message-Definition-tp3741927p3781631.html
To unsubscribe from Re: Issue For BPEL SE When Using Real Web Service And Complex Type Message Definition, click here.