Netbeans/AXIS2/BPEL - Fail to call hello world web service from BPEL

View: New views
7 Messages — Rating Filter:   Alert me  

Netbeans/AXIS2/BPEL - Fail to call hello world web service from BPEL

by dawg :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi,

I'm trying to do a very very basic thing, and yet miserably fail...

Steps:
1. Axis2 web service from java - create an empty class with sample method
2. Generate WSDL from it (trying to attach Axis2Test.wsdl)
3. This is an important point now - the wsdl is created with 3 ports: soap11, soap12 and http, later when I'll add this wsdl to a BPEL sample project and try to build the composite application I will get a warning about that.
4. Since I'm running axis2 on tomcat, and the bpel engine on glassfish, I'm also manually changing the address of the newly created service to port 8084 instead of 8080. Is there anywhere I can change it so the generation will use it and I won't have to manually interfere?
5. Create a sample synchronous BPEL project with the composite sample application. (process file attached)
6. Drag the hello.wsdl to the workflow as a new partnerlink
7. add assign1, invoke, assign2 to the workflow
8. build the composite app - the following warnings are given:

WARNING: Missing WSDL extension plug-in for "http://schemas.xmlsoap.org/wsdl/soap12/" or missing binding component definition in the config file.

WARNING: 1 or more consumers with 3 ports [{http://testing/}Axis2TestPortType]
        Port[0]: Axis2TestSOAP11port_http, {http://testing/}Axis2TestSOAP11Binding
        Port[1]: Axis2TestSOAP12port_http, {http://testing/}Axis2TestSOAP12Binding
        Port[2]: Axis2TestHttpport, {http://testing/}Axis2TestHttpBinding
        Consumer[0]: {http://enterprise.netbeans.org/bpel/SynchronousSample/SynchronousSample_1}HelloPL.Axis2TestRole_partnerRole

9. Create a test case and try to run it.

Failure 1:

BPJBI-6018:EndPoint Reference is not available from the JBI corresponding to the service name {http://enterprise.netbeans.org/bpel/SynchronousSample/SynchronousSample_1}HelloPL1 and endpoint name Axis2TestRole_partnerRole

In Glassfish log: (attached a glassfish log from the time of the error)
java.lang.RuntimeException: BPJBI-6018:EndPoint Reference is not available from the JBI corresponding to the service name {http://enterprise.netbeans.org/bpel/SynchronousSample/SynchronousSample_1}HelloPL1 and endpoint name Axis2TestRole_partnerRole
        at com.sun.jbi.engine.bpel.EngineChannel.invoke(EngineChannel.java:235)
        at com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELProcessManagerImpl.invoke(BPELProcessManagerImpl.java:699)
        at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.invoke(InvokeUnitImpl.java:369)

java.lang.Exception: BPCOR-6135:A fault was not handled in the process scope; Fault Name is {http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault; Fault Data is <?xml version="1.0" encoding="UTF-8"?><jbi:message xmlns:sxeh="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling" type="sxeh:faultMessage" version="1.0" xmlns:jbi="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper"><jbi:part>BPJBI-6018:EndPoint Reference is not available from the JBI corresponding to the service name {http://enterprise.netbeans.org/bpel/SynchronousSample/SynchronousSample_1}HelloPL1 and endpoint name Axis2TestRole_partnerRole</jbi:part></jbi:message>. Sending errors for the pending requests in the process scope before terminating the process instance

What is going wrong here?????!!!?

Thanks,
Dawg

glassfish_err.log
Axis2Test.wsdlSynchronousSample.bpel

Re: Netbeans/AXIS2/BPEL - Fail to call hello world web service from BPEL

by dawg :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Additional comment: I must be doing something very wrong, coz I tried the same thing with JAX-WS, which creates only one binding, and runs on glassfish rather than tomcat, so no manual intervention, and still, getting the same error, what am I doing wrong?

dawg wrote:
Hi,

I'm trying to do a very very basic thing, and yet miserably fail...

Steps:
1. Axis2 web service from java - create an empty class with sample method
2. Generate WSDL from it (trying to attach Axis2Test.wsdl)
3. This is an important point now - the wsdl is created with 3 ports: soap11, soap12 and http, later when I'll add this wsdl to a BPEL sample project and try to build the composite application I will get a warning about that.
4. Since I'm running axis2 on tomcat, and the bpel engine on glassfish, I'm also manually changing the address of the newly created service to port 8084 instead of 8080. Is there anywhere I can change it so the generation will use it and I won't have to manually interfere?
5. Create a sample synchronous BPEL project with the composite sample application. (process file attached)
6. Drag the hello.wsdl to the workflow as a new partnerlink
7. add assign1, invoke, assign2 to the workflow
8. build the composite app - the following warnings are given:

WARNING: Missing WSDL extension plug-in for "http://schemas.xmlsoap.org/wsdl/soap12/" or missing binding component definition in the config file.

WARNING: 1 or more consumers with 3 ports [{http://testing/}Axis2TestPortType]
        Port[0]: Axis2TestSOAP11port_http, {http://testing/}Axis2TestSOAP11Binding
        Port[1]: Axis2TestSOAP12port_http, {http://testing/}Axis2TestSOAP12Binding
        Port[2]: Axis2TestHttpport, {http://testing/}Axis2TestHttpBinding
        Consumer[0]: {http://enterprise.netbeans.org/bpel/SynchronousSample/SynchronousSample_1}HelloPL.Axis2TestRole_partnerRole

9. Create a test case and try to run it.

Failure 1:

BPJBI-6018:EndPoint Reference is not available from the JBI corresponding to the service name {http://enterprise.netbeans.org/bpel/SynchronousSample/SynchronousSample_1}HelloPL1 and endpoint name Axis2TestRole_partnerRole

In Glassfish log: (attached a glassfish log from the time of the error)
java.lang.RuntimeException: BPJBI-6018:EndPoint Reference is not available from the JBI corresponding to the service name {http://enterprise.netbeans.org/bpel/SynchronousSample/SynchronousSample_1}HelloPL1 and endpoint name Axis2TestRole_partnerRole
        at com.sun.jbi.engine.bpel.EngineChannel.invoke(EngineChannel.java:235)
        at com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELProcessManagerImpl.invoke(BPELProcessManagerImpl.java:699)
        at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.invoke(InvokeUnitImpl.java:369)

java.lang.Exception: BPCOR-6135:A fault was not handled in the process scope; Fault Name is {http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault; Fault Data is <?xml version="1.0" encoding="UTF-8"?><jbi:message xmlns:sxeh="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling" type="sxeh:faultMessage" version="1.0" xmlns:jbi="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper"><jbi:part>BPJBI-6018:EndPoint Reference is not available from the JBI corresponding to the service name {http://enterprise.netbeans.org/bpel/SynchronousSample/SynchronousSample_1}HelloPL1 and endpoint name Axis2TestRole_partnerRole</jbi:part></jbi:message>. Sending errors for the pending requests in the process scope before terminating the process instance

What is going wrong here?????!!!?

Thanks,
Dawg

glassfish_err.log
Axis2Test.wsdlSynchronousSample.bpel

Re: Netbeans/AXIS2/BPEL - Fail to call hello world web service from BPEL

by Vitaly Bychkov :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

The BPEL 2.0 specification says about support of the wsdl 1.1 and  soap 1.1.
In your case you tried to use soap  binding 1.2 which  As I know is not supported for now.

Do you really need soap binding 1.2 ?

Could you tried with soap1.1 ?


Vitaly.


dawg wrote:
Additional comment: I must be doing something very wrong, coz I tried the
same thing with JAX-WS, which creates only one binding, and runs on
glassfish rather than tomcat, so no manual intervention, and still, getting
the same error, what am I doing wrong?


dawg wrote:
  
Hi,

I'm trying to do a very very basic thing, and yet miserably fail...

Steps:
1. Axis2 web service from java - create an empty class with sample method
2. Generate WSDL from it (trying to attach Axis2Test.wsdl)
3. This is an important point now - the wsdl is created with 3 ports:
soap11, soap12 and http, later when I'll add this wsdl to a BPEL sample
project and try to build the composite application I will get a warning
about that. 
4. Since I'm running axis2 on tomcat, and the bpel engine on glassfish,
I'm also manually changing the address of the newly created service to
port 8084 instead of 8080. Is there anywhere I can change it so the
generation will use it and I won't have to manually interfere?
5. Create a sample synchronous BPEL project with the composite sample
application. (process file attached)
6. Drag the hello.wsdl to the workflow as a new partnerlink
7. add assign1, invoke, assign2 to the workflow
8. build the composite app - the following warnings are given:

WARNING: Missing WSDL extension plug-in for
"http://schemas.xmlsoap.org/wsdl/soap12/" or missing binding component
definition in the config file.

WARNING: 1 or more consumers with 3 ports
[{http://testing/}Axis2TestPortType]
        Port[0]: Axis2TestSOAP11port_http,
{http://testing/}Axis2TestSOAP11Binding
        Port[1]: Axis2TestSOAP12port_http,
{http://testing/}Axis2TestSOAP12Binding
        Port[2]: Axis2TestHttpport, {http://testing/}Axis2TestHttpBinding
        Consumer[0]:
{http://enterprise.netbeans.org/bpel/SynchronousSample/SynchronousSample_1}HelloPL.Axis2TestRole_partnerRole

9. Create a test case and try to run it.

Failure 1:

BPJBI-6018:EndPoint Reference is not available from the JBI corresponding
to the service name
{http://enterprise.netbeans.org/bpel/SynchronousSample/SynchronousSample_1}HelloPL1
and endpoint name Axis2TestRole_partnerRole

In Glassfish log: (attached a glassfish log from the time of the error)
java.lang.RuntimeException: BPJBI-6018:EndPoint Reference is not available
from the JBI corresponding to the service name
{http://enterprise.netbeans.org/bpel/SynchronousSample/SynchronousSample_1}HelloPL1
and endpoint name Axis2TestRole_partnerRole
        at
com.sun.jbi.engine.bpel.EngineChannel.invoke(EngineChannel.java:235)
        at
com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELProcessManagerImpl.invoke(BPELProcessManagerImpl.java:699)
        at
com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.invoke(InvokeUnitImpl.java:369)

java.lang.Exception: BPCOR-6135:A fault was not handled in the process
scope; Fault Name is
{http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault;
Fault Data is <?xml version="1.0" encoding="UTF-8"?><jbi:message
xmlns:sxeh="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling"
type="sxeh:faultMessage" version="1.0"
xmlns:jbi="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper"><jbi:part>BPJBI-6018:EndPoint
Reference is not available from the JBI corresponding to the service name
{http://enterprise.netbeans.org/bpel/SynchronousSample/SynchronousSample_1}HelloPL1
and endpoint name Axis2TestRole_partnerRole</jbi:part></jbi:message>.
Sending errors for the pending requests in the process scope before
terminating the process instance

What is going wrong here?????!!!?

Thanks,
Dawg

 http://www.nabble.com/file/p19914887/glassfish_err.log glassfish_err.log 
 http://www.nabble.com/file/p19914887/Axis2Test.wsdl Axis2Test.wsdl 
http://www.nabble.com/file/p19914887/SynchronousSample.bpel
SynchronousSample.bpel 

    

  


Re: Netbeans/AXIS2/BPEL - Fail to call hello world web service from BPEL

by dawg :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Thanks for your reply Vitaly.

What I've tried is this:

In the generated wsdl from axis, I removed the entries soap12 and http bindings from the port definition. I'm not sure this is enough or the right way to do it, coz it resulted in a different error - something to do with wrong address.

What is the proper way to create a wsdl1.1 soap 1.1 webservice?

Thanks,
Dawg


Vitaly Bychkov wrote:
The BPEL 2.0 specification says about support of the wsdl 1.1 and  soap 1.1.
In your case you tried to use soap  binding 1.2 which  As I know is not
supported for now.

Do you really need soap binding 1.2 ?

Could you tried with soap1.1 ?


Vitaly.


dawg wrote:
> Additional comment: I must be doing something very wrong, coz I tried the
> same thing with JAX-WS, which creates only one binding, and runs on
> glassfish rather than tomcat, so no manual intervention, and still, getting
> the same error, what am I doing wrong?
>
>
> dawg wrote:
>  
>> Hi,
>>
>> I'm trying to do a very very basic thing, and yet miserably fail...
>>
>> Steps:
>> 1. Axis2 web service from java - create an empty class with sample method
>> 2. Generate WSDL from it (trying to attach Axis2Test.wsdl)
>> 3. This is an important point now - the wsdl is created with 3 ports:
>> soap11, soap12 and http, later when I'll add this wsdl to a BPEL sample
>> project and try to build the composite application I will get a warning
>> about that.
>> 4. Since I'm running axis2 on tomcat, and the bpel engine on glassfish,
>> I'm also manually changing the address of the newly created service to
>> port 8084 instead of 8080. Is there anywhere I can change it so the
>> generation will use it and I won't have to manually interfere?
>> 5. Create a sample synchronous BPEL project with the composite sample
>> application. (process file attached)
>> 6. Drag the hello.wsdl to the workflow as a new partnerlink
>> 7. add assign1, invoke, assign2 to the workflow
>> 8. build the composite app - the following warnings are given:
>>
>> WARNING: Missing WSDL extension plug-in for
>> "http://schemas.xmlsoap.org/wsdl/soap12/" or missing binding component
>> definition in the config file.
>>
>> WARNING: 1 or more consumers with 3 ports
>> [{http://testing/}Axis2TestPortType]
>>         Port[0]: Axis2TestSOAP11port_http,
>> {http://testing/}Axis2TestSOAP11Binding
>>         Port[1]: Axis2TestSOAP12port_http,
>> {http://testing/}Axis2TestSOAP12Binding
>>         Port[2]: Axis2TestHttpport, {http://testing/}Axis2TestHttpBinding
>>         Consumer[0]:
>> {http://enterprise.netbeans.org/bpel/SynchronousSample/SynchronousSample_1}HelloPL.Axis2TestRole_partnerRole
>>
>> 9. Create a test case and try to run it.
>>
>> Failure 1:
>>
>> BPJBI-6018:EndPoint Reference is not available from the JBI corresponding
>> to the service name
>> {http://enterprise.netbeans.org/bpel/SynchronousSample/SynchronousSample_1}HelloPL1
>> and endpoint name Axis2TestRole_partnerRole
>>
>> In Glassfish log: (attached a glassfish log from the time of the error)
>> java.lang.RuntimeException: BPJBI-6018:EndPoint Reference is not available
>> from the JBI corresponding to the service name
>> {http://enterprise.netbeans.org/bpel/SynchronousSample/SynchronousSample_1}HelloPL1
>> and endpoint name Axis2TestRole_partnerRole
>>         at
>> com.sun.jbi.engine.bpel.EngineChannel.invoke(EngineChannel.java:235)
>>         at
>> com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELProcessManagerImpl.invoke(BPELProcessManagerImpl.java:699)
>>         at
>> com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.invoke(InvokeUnitImpl.java:369)
>>
>> java.lang.Exception: BPCOR-6135:A fault was not handled in the process
>> scope; Fault Name is
>> {http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault;
>> Fault Data is <?xml version="1.0" encoding="UTF-8"?><jbi:message
>> xmlns:sxeh="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling"
>> type="sxeh:faultMessage" version="1.0"
>> xmlns:jbi="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper"><jbi:part>BPJBI-6018:EndPoint
>> Reference is not available from the JBI corresponding to the service name
>> {http://enterprise.netbeans.org/bpel/SynchronousSample/SynchronousSample_1}HelloPL1
>> and endpoint name Axis2TestRole_partnerRole</jbi:part></jbi:message>.
>> Sending errors for the pending requests in the process scope before
>> terminating the process instance
>>
>> What is going wrong here?????!!!?
>>
>> Thanks,
>> Dawg
>>
>>  http://www.nabble.com/file/p19914887/glassfish_err.log glassfish_err.log
>>  http://www.nabble.com/file/p19914887/Axis2Test.wsdl Axis2Test.wsdl
>> http://www.nabble.com/file/p19914887/SynchronousSample.bpel
>> SynchronousSample.bpel
>>
>>    
>
>  

Re: Netbeans/AXIS2/BPEL - Fail to call hello world web service from BPEL

by Vitaly Bychkov :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Dawk you can't simply remove binding part because it defines the concrete part of the wsdl i.e. which address and which protocol e.c. to use.

I guess that your wsdl is wsdl2.0.
I'm not sure if there is any convertors from wsdl 2.0 to wsdl 1.1 :(

You can try manually create wsdl 1.1 by the netbeans wsdl wizard.
Wsdl 1.1 uses soap binding 1.1.

Unfortunatelly I can't see any of your project files
http://www.nabble.com/file/p19914887/Axis2Test.wsdl
.....
because of :
HTTP ERROR: 410

This file has been deleted.
RequestURI=/file/p19914887/Axis2Test.wsdl


Could you please attach it into the letter.


Thank you,
Vitaly.




dawg wrote:
Thanks for your reply Vitaly. 

What I've tried is this:

In the generated wsdl from axis, I removed the entries soap12 and http
bindings from the port definition. I'm not sure this is enough or the right
way to do it, coz it resulted in a different error - something to do with
wrong address. 

What is the proper way to create a wsdl1.1 soap 1.1 webservice?

Thanks,
Dawg



Vitaly Bychkov wrote:
  
The BPEL 2.0 specification says about support of the wsdl 1.1 and  soap
1.1.
In your case you tried to use soap  binding 1.2 which  As I know is not 
supported for now.

Do you really need soap binding 1.2 ?

Could you tried with soap1.1 ?


Vitaly.


dawg wrote:
    
Additional comment: I must be doing something very wrong, coz I tried the
same thing with JAX-WS, which creates only one binding, and runs on
glassfish rather than tomcat, so no manual intervention, and still,
getting
the same error, what am I doing wrong?


dawg wrote:
  
      
Hi,

I'm trying to do a very very basic thing, and yet miserably fail...

Steps:
1. Axis2 web service from java - create an empty class with sample
method
2. Generate WSDL from it (trying to attach Axis2Test.wsdl)
3. This is an important point now - the wsdl is created with 3 ports:
soap11, soap12 and http, later when I'll add this wsdl to a BPEL sample
project and try to build the composite application I will get a warning
about that. 
4. Since I'm running axis2 on tomcat, and the bpel engine on glassfish,
I'm also manually changing the address of the newly created service to
port 8084 instead of 8080. Is there anywhere I can change it so the
generation will use it and I won't have to manually interfere?
5. Create a sample synchronous BPEL project with the composite sample
application. (process file attached)
6. Drag the hello.wsdl to the workflow as a new partnerlink
7. add assign1, invoke, assign2 to the workflow
8. build the composite app - the following warnings are given:

WARNING: Missing WSDL extension plug-in for
"http://schemas.xmlsoap.org/wsdl/soap12/" or missing binding component
definition in the config file.

WARNING: 1 or more consumers with 3 ports
[{http://testing/}Axis2TestPortType]
        Port[0]: Axis2TestSOAP11port_http,
{http://testing/}Axis2TestSOAP11Binding
        Port[1]: Axis2TestSOAP12port_http,
{http://testing/}Axis2TestSOAP12Binding
        Port[2]: Axis2TestHttpport,
{http://testing/}Axis2TestHttpBinding
        Consumer[0]:
{http://enterprise.netbeans.org/bpel/SynchronousSample/SynchronousSample_1}HelloPL.Axis2TestRole_partnerRole

9. Create a test case and try to run it.

Failure 1:

BPJBI-6018:EndPoint Reference is not available from the JBI
corresponding
to the service name
{http://enterprise.netbeans.org/bpel/SynchronousSample/SynchronousSample_1}HelloPL1
and endpoint name Axis2TestRole_partnerRole

In Glassfish log: (attached a glassfish log from the time of the error)
java.lang.RuntimeException: BPJBI-6018:EndPoint Reference is not
available
from the JBI corresponding to the service name
{http://enterprise.netbeans.org/bpel/SynchronousSample/SynchronousSample_1}HelloPL1
and endpoint name Axis2TestRole_partnerRole
        at
com.sun.jbi.engine.bpel.EngineChannel.invoke(EngineChannel.java:235)
        at
com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELProcessManagerImpl.invoke(BPELProcessManagerImpl.java:699)
        at
com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.invoke(InvokeUnitImpl.java:369)

java.lang.Exception: BPCOR-6135:A fault was not handled in the process
scope; Fault Name is
{http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault;
Fault Data is <?xml version="1.0" encoding="UTF-8"?><jbi:message
xmlns:sxeh="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling"
type="sxeh:faultMessage" version="1.0"
xmlns:jbi="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper"><jbi:part>BPJBI-6018:EndPoint
Reference is not available from the JBI corresponding to the service
name
{http://enterprise.netbeans.org/bpel/SynchronousSample/SynchronousSample_1}HelloPL1
and endpoint name Axis2TestRole_partnerRole</jbi:part></jbi:message>.
Sending errors for the pending requests in the process scope before
terminating the process instance

What is going wrong here?????!!!?

Thanks,
Dawg

 http://www.nabble.com/file/p19914887/glassfish_err.log
glassfish_err.log 
 http://www.nabble.com/file/p19914887/Axis2Test.wsdl Axis2Test.wsdl 
http://www.nabble.com/file/p19914887/SynchronousSample.bpel
SynchronousSample.bpel 

    
        
  
      

    

  



Re: Netbeans/AXIS2/BPEL - Fail to call hello world web service from BPEL

by dawg :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

I'll paste it, attachment apparently didn't work so good:

The original WSDL:

<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:axis2="http://testing/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:ns0="http://testing/xsd" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:ns1="http://org.apache.axis2/xsd" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" targetNamespace="http://testing/">
    <wsdl:types>
        <xs:schema xmlns:ns="http://testing/xsd" attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://testing/xsd">
    <xs:element name="hello">
        <xs:complexType>
            <xs:sequence>
                <xs:element minOccurs="0" name="name" nillable="true" type="xs:string"/>
            </xs:sequence>
        </xs:complexType>
    </xs:element>
    <xs:element name="helloResponse">
        <xs:complexType>
            <xs:sequence>
                <xs:element minOccurs="0" name="return" nillable="true" type="xs:string"/>
            </xs:sequence>
        </xs:complexType>
    </xs:element>
</xs:schema>
    </wsdl:types>
    <wsdl:message name="helloRequest">
        <wsdl:part name="parameters" element="ns0:hello"/>
    </wsdl:message>
    <wsdl:message name="helloResponse">
        <wsdl:part name="parameters" element="ns0:helloResponse"/>
    </wsdl:message>
    <wsdl:portType name="Axis2TestPortType">
        <wsdl:operation name="hello">
            <wsdl:input message="axis2:helloRequest" wsaw:Action="urn:hello"/>
            <wsdl:output message="axis2:helloResponse" wsaw:Action="urn:helloResponse"/>
        </wsdl:operation>
    </wsdl:portType>
    <wsdl:binding name="Axis2TestSOAP11Binding" type="axis2:Axis2TestPortType">
        <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
        <wsdl:operation name="hello">
            <soap:operation soapAction="urn:hello" style="document"/>
            <wsdl:input>
                <soap:body use="literal"/>
            </wsdl:input>
            <wsdl:output>
                <soap:body use="literal"/>
            </wsdl:output>
        </wsdl:operation>
    </wsdl:binding>
    <wsdl:binding name="Axis2TestSOAP12Binding" type="axis2:Axis2TestPortType">
        <soap12:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
        <wsdl:operation name="hello">
            <soap12:operation soapAction="urn:hello" style="document"/>
            <wsdl:input>
                <soap12:body use="literal"/>
            </wsdl:input>
            <wsdl:output>
                <soap12:body use="literal"/>
            </wsdl:output>
        </wsdl:operation>
    </wsdl:binding>
    <wsdl:binding name="Axis2TestHttpBinding" type="axis2:Axis2TestPortType">
        <http:binding verb="POST"/>
        <wsdl:operation name="hello">
            <http:operation location="Axis2Test/hello"/>
            <wsdl:input>
                <mime:content type="text/xml" part="hello"/>
            </wsdl:input>
            <wsdl:output>
                <mime:content type="text/xml" part="hello"/>
            </wsdl:output>
        </wsdl:operation>
    </wsdl:binding>
    <wsdl:service name="Axis2Test">
        <wsdl:port name="Axis2TestSOAP11port_http" binding="axis2:Axis2TestSOAP11Binding">
            <soap:address location="http://localhost:8084/axis2/services/Axis2Test"/>
        </wsdl:port>
        <wsdl:port name="Axis2TestSOAP12port_http" binding="axis2:Axis2TestSOAP12Binding">
            <soap12:address location="http://localhost:8084/axis2/services/Axis2Test"/>
        </wsdl:port>
        <wsdl:port name="Axis2TestHttpport" binding="axis2:Axis2TestHttpBinding">
            <http:address location="http://localhost:8084/axis2/services/Axis2Test"/>
        </wsdl:port>
    </wsdl:service>
</wsdl:definitions>


Parent Message unknown Re: Netbeans/AXIS2/BPEL - Fail to call hello world web service from BPEL

by Vitaly Bychkov :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Sujit, thank you for corrections.
It's great !



Sujit Biswas wrote:
Hi Dawk,

now there is support for   "WSDL 1.1 with Binding Extension for SOAP 1.2",


more info here http://wiki.open-esb.java.net/Wiki.jsp?page=HTTPBC.SOAP12

for this you have to update to the latest version of openesb.

Thanks,
Sujit




Vitaly Bychkov wrote:
Dawk you can't simply remove binding part because it defines the concrete part of the wsdl i.e. which address and which protocol e.c. to use.

I guess that your wsdl is wsdl2.0.
I'm not sure if there is any convertors from wsdl 2.0 to wsdl 1.1 :(

You can try manually create wsdl 1.1 by the netbeans wsdl wizard.
Wsdl 1.1 uses soap binding 1.1.

Unfortunatelly I can't see any of your project files
http://www.nabble.com/file/p19914887/Axis2Test.wsdl
.....
because of :
HTTP ERROR: 410

This file has been deleted.
RequestURI=/file/p19914887/Axis2Test.wsdl


Could you please attach it into the letter.


Thank you,
Vitaly.
  




dawg wrote:
Thanks for your reply Vitaly. 

What I've tried is this:

In the generated wsdl from axis, I removed the entries soap12 and http
bindings from the port definition. I'm not sure this is enough or the right
way to do it, coz it resulted in a different error - something to do with
wrong address. 

What is the proper way to create a wsdl1.1 soap 1.1 webservice?

Thanks,
Dawg



Vitaly Bychkov wrote:
  
The BPEL 2.0 specification says about support of the wsdl 1.1 and  soap
1.1.
In your case you tried to use soap  binding 1.2 which  As I know is not 
supported for now.

Do you really need soap binding 1.2 ?

Could you tried with soap1.1 ?


Vitaly.


dawg wrote:
    
Additional comment: I must be doing something very wrong, coz I tried the
same thing with JAX-WS, which creates only one binding, and runs on
glassfish rather than tomcat, so no manual intervention, and still,
getting
the same error, what am I doing wrong?


dawg wrote:
  
      
Hi,

I'm trying to do a very very basic thing, and yet miserably fail...

Steps:
1. Axis2 web service from java - create an empty class with sample
method
2. Generate WSDL from it (trying to attach Axis2Test.wsdl)
3. This is an important point now - the wsdl is created with 3 ports:
soap11, soap12 and http, later when I'll add this wsdl to a BPEL sample
project and try to build the composite application I will get a warning
about that. 
4. Since I'm running axis2 on tomcat, and the bpel engine on glassfish,
I'm also manually changing the address of the newly created service to
port 8084 instead of 8080. Is there anywhere I can change it so the
generation will use it and I won't have to manually interfere?
5. Create a sample synchronous BPEL project with the composite sample
application. (process file attached)
6. Drag the hello.wsdl to the workflow as a new partnerlink
7. add assign1, invoke, assign2 to the workflow
8. build the composite app - the following warnings are given:

WARNING: Missing WSDL extension plug-in for
"http://schemas.xmlsoap.org/wsdl/soap12/" or missing binding component
definition in the config file.

WARNING: 1 or more consumers with 3 ports
[{http://testing/}Axis2TestPortType]
        Port[0]: Axis2TestSOAP11port_http,
{http://testing/}Axis2TestSOAP11Binding
        Port[1]: Axis2TestSOAP12port_http,
{http://testing/}Axis2TestSOAP12Binding
        Port[2]: Axis2TestHttpport,
{http://testing/}Axis2TestHttpBinding
        Consumer[0]:
{http://enterprise.netbeans.org/bpel/SynchronousSample/SynchronousSample_1}HelloPL.Axis2TestRole_partnerRole

9. Create a test case and try to run it.

Failure 1:

BPJBI-6018:EndPoint Reference is not available from the JBI
corresponding
to the service name
{http://enterprise.netbeans.org/bpel/SynchronousSample/SynchronousSample_1}HelloPL1
and endpoint name Axis2TestRole_partnerRole

In Glassfish log: (attached a glassfish log from the time of the error)
java.lang.RuntimeException: BPJBI-6018:EndPoint Reference is not
available
from the JBI corresponding to the service name
{http://enterprise.netbeans.org/bpel/SynchronousSample/SynchronousSample_1}HelloPL1
and endpoint name Axis2TestRole_partnerRole
        at
com.sun.jbi.engine.bpel.EngineChannel.invoke(EngineChannel.java:235)
        at
com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELProcessManagerImpl.invoke(BPELProcessManagerImpl.java:699)
        at
com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.invoke(InvokeUnitImpl.java:369)

java.lang.Exception: BPCOR-6135:A fault was not handled in the process
scope; Fault Name is
{http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault;
Fault Data is <?xml version="1.0" encoding="UTF-8"?><jbi:message
xmlns:sxeh="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling"
type="sxeh:faultMessage" version="1.0"
xmlns:jbi="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper"><jbi:part>BPJBI-6018:EndPoint
Reference is not available from the JBI corresponding to the service
name
{http://enterprise.netbeans.org/bpel/SynchronousSample/SynchronousSample_1}HelloPL1
and endpoint name Axis2TestRole_partnerRole</jbi:part></jbi:message>.
Sending errors for the pending requests in the process scope before
terminating the process instance

What is going wrong here?????!!!?

Thanks,
Dawg

 http://www.nabble.com/file/p19914887/glassfish_err.log
glassfish_err.log 
 http://www.nabble.com/file/p19914887/Axis2Test.wsdl Axis2Test.wsdl 
http://www.nabble.com/file/p19914887/SynchronousSample.bpel
SynchronousSample.bpel