Re: OpenESB

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

Parent Message unknown Re: OpenESB

by Kiran Bhumana-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


CCing nb alias. Both of these are editor issues. The first issue seems to be a WSDL import issue, related to WSDL editor. I think it will be helpful to debug and suggest something if you can put the snippets of what happens when you import.
On the same note, the second issue is not very clear from your description. Soap end points are not generated when you build the CA. When you build CA, the CA project just attempts to link the endpoints in a way that underlying runtime JBI understands. When you built the Java based WSDL service, maybe your WSDL consists of the service and endpoint. Are you sure there is a service and endpoint in the imported WSDL? I am assuming you imported this WSDL and used one of the WSDL's operation to invoke the service.

-Kiran B.

stfengineer wrote:
There are 2 issues, when we do external wsdl import using the URL, the
imported wsdl file doesn't have any prefix. So in order to create the
partner link we need to rename this wsdl file to add a prefix i.e. to make
it xyz.wsdl, it originally imports it with just .wsdl. Secondly after we do
all that, when we build the CA no soap endpoint is generated for this 
partner link. Normally for our java wsdl it generates the endpoint
automatically. 

Thanks



Kiran Bhumana-2 wrote:
  
You should be able to call the WCF as long as either side is using the 
compatible versions of the spec. OpenESB as of date supports only WSDL 
1.1. I am not aware of any example calling WCF service although I 
noticed users on the forums have tried calling .net webservices and got 
it working.

Can you explain what doesn't work? or what you see as errors when 
calling WCF service?

-Kiran B

stfengineer wrote:
    
Hello, I am new to OpenESB, I have a question for everyone. We have a WCF
webservice which we are trying to call in a BPEL process in OpenESB
(Netbeans). But it doesn't work. When we call the java webservice,
everything works fine. Is there any example available on how to call WCF
webservice in openESB? does the openESB supports both wsdl1 and 2. Any
help
would be appreciated

Thanks
  
      
-- 
Kiran Bhumana
Open ESB Community (http://open-esb.org)


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...



    

  

-- 
Kiran Bhumana
Open ESB Community (http://open-esb.org)

Parent Message unknown Re: OpenESB

by Murali Pottlapelli :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

 From BPEL it is possible to call SOAP 1.2 EP via EJB WS, is that OK?

Regards
Murali

Sean Keane wrote:

> stfengineer ,
>
> can you try and generate the WSDL from a file, instead of the URL to
> see if this resolves your issue.  Also, it seems to only have a SOAP
> 1.2 endpoint, which is currently not supported by the HTTP BC.  You
> can create an EJB client which does support SOAP 1.2.
>
> Sean
>
> Kiran Bhumana wrote:
>>
>> CCing nb alias. Both of these are editor issues. The first issue
>> seems to be a WSDL import issue, related to WSDL editor. I think it
>> will be helpful to debug and suggest something if you can put the
>> snippets of what happens when you import.
>> On the same note, the second issue is not very clear from your
>> description. Soap end points are not generated when you build the CA.
>> When you build CA, the CA project just attempts to link the endpoints
>> in a way that underlying runtime JBI understands. When you built the
>> Java based WSDL service, maybe your WSDL consists of the service and
>> endpoint. Are you sure there is a service and endpoint in the
>> imported WSDL? I am assuming you imported this WSDL and used one of
>> the WSDL's operation to invoke the service.
>>
>> -Kiran B.
>>
>> stfengineer wrote:
>>> There are 2 issues, when we do external wsdl import using the URL, the
>>> imported wsdl file doesn't have any prefix. So in order to create the
>>> partner link we need to rename this wsdl file to add a prefix i.e. to make
>>> it xyz.wsdl, it originally imports it with just .wsdl. Secondly after we do
>>> all that, when we build the CA no soap endpoint is generated for this
>>> partner link. Normally for our java wsdl it generates the endpoint
>>> automatically.
>>>
>>> Thanks
>>>
>>>
>>>
>>> Kiran Bhumana-2 wrote:
>>>  
>>>> You should be able to call the WCF as long as either side is using the
>>>> compatible versions of the spec. OpenESB as of date supports only WSDL
>>>> 1.1. I am not aware of any example calling WCF service although I
>>>> noticed users on the forums have tried calling .net webservices and got
>>>> it working.
>>>>
>>>> Can you explain what doesn't work? or what you see as errors when
>>>> calling WCF service?
>>>>
>>>> -Kiran B
>>>>
>>>> stfengineer wrote:
>>>>    
>>>>> Hello, I am new to OpenESB, I have a question for everyone. We have a WCF
>>>>> webservice which we are trying to call in a BPEL process in OpenESB
>>>>> (Netbeans). But it doesn't work. When we call the java webservice,
>>>>> everything works fine. Is there any example available on how to call WCF
>>>>> webservice in openESB? does the openESB supports both wsdl1 and 2. Any
>>>>> help
>>>>> would be appreciated
>>>>>
>>>>> Thanks
>>>>>  
>>>>>      
>>>> --
>>>> Kiran Bhumana
>>>> Open ESB Community (http://open-esb.org)
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@...
>>>> For additional commands, e-mail: dev-help@...
>>>>
>>>>
>>>>
>>>>    
>>>
>>>  
>>
>> --
>> Kiran Bhumana
>> Open ESB Community (http://open-esb.org)
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@... For
> additional commands, e-mail: dev-help@...