Cannot generate provider in petalsstudio

classic Classic list List threaded Threaded
22 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Cannot generate provider in petalsstudio

Philip
I started again to work on Petals Studio 1.3.2, and I am not able anymore to create a Provider SU for a SOAP webservice.
I tried with java 6 SDK and a java7 SDK : same error. i also unzipped again the Petals sudio : same error...

I always get the following : any idea? The symptom is that the jbi.xml is not creted in the jbi folder :(

java.lang.NullPointerException
        at org.eclipse.bpel.common.wsdl.helpers.UriAndUrlHelper.getRelativeLocationToUri(UriAndUrlHelper.java:188)
        at org.eclipse.bpel.common.wsdl.importhelpers.WsdlImportHelper.analyzeResources(WsdlImportHelper.java:223)
        at org.eclipse.bpel.common.wsdl.importhelpers.WsdlImportHelper.importWsdlOrXsdAndDependencies(WsdlImportHelper.java:94)
        at com.ebmwebsourcing.petals.services.su.wizards.AbstractServiceUnitWizard.importWSDLFileInProvideSUProject(AbstractServiceUnitWizard.java:294)
        at com.ebmwebsourcing.petals.services.su.wizards.AbstractServiceUnitWizard.doFinish(AbstractServiceUnitWizard.java:264)
        at com.ebmwebsourcing.petals.services.su.wizards.AbstractServiceUnitWizard.access$0(AbstractServiceUnitWizard.java:253)
        at com.ebmwebsourcing.petals.services.su.wizards.AbstractServiceUnitWizard$1.execute(AbstractServiceUnitWizard.java:213)
        at org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(WorkspaceModifyOperation.java:106)
        at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344)
        at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:118)
        at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.jav
Reply | Threaded
Open this post in threaded view
|

Re: Cannot generate provider in petalsstudio

Vincent Zurczak
Hi,

This error indicates a problem while importing a WSDL dependency (e.g. a XML schema).
Are you sure your WSDL is valid? Is it available somewhere, so that I can test it? Either your WSDL is invalid, or it is not supported correctly (bug).

Since I plan to release a maintenance version of the studio really soon, it is the right moment to fix it.
« Petals M.D. »
Reply | Threaded
Open this post in threaded view
|

Re: Cannot generate provider in petalsstudio

Philip
This post was updated on .
here is the WSDL.
Is is accepted by SOAPUI, and generated on .net platform
 ws_dba.wsdl
Reply | Threaded
Open this post in threaded view
|

Re: Cannot generate provider in petalsstudio

Vincent Zurczak
Hi,

I do not see your WSDL.
Could you fix this?
« Petals M.D. »
Reply | Threaded
Open this post in threaded view
|

Re: Cannot generate provider in petalsstudio

Philip
I included it as a link in previous post.
Thanks
Reply | Threaded
Open this post in threaded view
|

Re: Cannot generate provider in petalsstudio

Vincent Zurczak
I will also need the document at: http://dvlp.websvc.company.com/ws_dba_wcfservice/ws_dba.svc?wsdl=wsdl0

Thanks,
Vincent.
« Petals M.D. »
Reply | Threaded
Open this post in threaded view
|

Re: Cannot generate provider in petalsstudio

Philip
here it is : ws_dba.wsdl0.wsdl
Reply | Threaded
Open this post in threaded view
|

Re: Cannot generate provider in petalsstudio

Philip
I don't know if it will help, but the problem is linked to the interoperability between some clients and WCF webservices that are using includes for nested wsdl and xsd.
See the interesting link : http://weblogs.thinktecture.com/cweyer/2007/05/improving-wcf-interoperability-flattening-your-wsdl.html
Reply | Threaded
Open this post in threaded view
|

Re: Cannot generate provider in petalsstudio

Vincent Zurczak
The WSDL import manager is supposed to take care of looping and crossed imports.
I will take a look at this tomorrow morning, since I am in a meeting today.
« Petals M.D. »
Reply | Threaded
Open this post in threaded view
|

Re: Cannot generate provider in petalsstudio

Vincent Zurczak
I found 5 minutes to take a look at it.
I will also need other files.
=> http://dvlp.websvc.company.com/ws_dba_wcfservice/ws_dba.svc?xsd=xsd1
=> http://dvlp.websvc.company.com/ws_dba_wcfservice/ws_dba.svc?xsd=xsd2

Thanks.
« Petals M.D. »
Reply | Threaded
Open this post in threaded view
|

Re: Cannot generate provider in petalsstudio

Philip
I have included the 3 xsd ( 0, 1 and 2)
ws_dba.xsd0ws_dba.xsd1ws_dba.xsd2

Thanks
Reply | Threaded
Open this post in threaded view
|

Re: Cannot generate provider in petalsstudio

Vincent Zurczak
This post was updated on .
Hi,

I have taken a look at what you gave me.
And I cannot validate the "WSDL0" file.

WSDL0 imports XSD0 with the namespace "http://dba.company.com".
But XSD0 has "http://dba.company.com/" for target namespace (additional slash at the end).

WSDL0 imports XSD2 with the namespace "http://schemas.datacontract.org/2004/07/Sybase.PowerBuilder.WCFNVO".
But XSD2 has "http://schemas.datacontract.org/2004/07/dba.company.com" for target namespace (not the same at all).

If your WSDL is invalid, it is normal that the studio cannot import it.
Could you check if the original WSDL is valid?

« Petals M.D. »
Reply | Threaded
Open this post in threaded view
|

Re: Cannot generate provider in petalsstudio

Philip
I have extracted the wsdl ( no more wsdl1 import) ant the 3 xsd in the zip file attached.
Thanks
wsdl_and_xsd.zip
Reply | Threaded
Open this post in threaded view
|

Re: Cannot generate provider in petalsstudio

Vincent Zurczak
This post was updated on .
I have taken your last version and updated the import references.
The WSDL cannot be validated in Eclipse with respect to the WS-I compliance. So, it is valid, but probably not WS-I compliant. And I was able to import it with the studio (no issue or log entry).

I tested a trunk version, a version 1.3.1 and 1.3.2.
I also noticed this WSDL is different from the previous one. The first import is different (not the same namespace). Can you make another test and tell me if you still have errors with this WSDL?
« Petals M.D. »
Reply | Threaded
Open this post in threaded view
|

Re: Cannot generate provider in petalsstudio

Philip
I regenerated the wcf service from scratch.
the WSI compliance has been validated by SOAPUI.
It still fails in Petals Studio
The wsdl ( starting with wsdl:definitions name="n_ws_dba" targetNamespace="http://tempuri.org/") imports another namespace ( <wsdl:import namespace="http://my.company.com" location="http://myserver/ws_dba_wcfservice/n_ws_dba.svc?wsdl=wsdl0" /> 
) which in turn imports some XSD files.
By configuring IIS, I have flattened all the xsds in the wsdl, but it seems that Petals does not handle the include of a namespace . Is it exact ?
Philip
Reply | Threaded
Open this post in threaded view
|

Re: Cannot generate provider in petalsstudio

Vincent Zurczak
Like I said, the last WSDL you sent me was successfully imported with the studio.
But it is not the same than the first one you sent in this topic. In the first one, there was no import of a namespace "http://tempuri.org/". And the import of the first WSDL failed.

So, right now, I cannot reproduce your problem.
We can make another try if you want. Regenerate the WSDL under the shape you want, reproduce the problem with the studio, and then send me all the WSDL files.
« Petals M.D. »
Reply | Threaded
Open this post in threaded view
|

Re: Cannot generate provider in petalsstudio

Philip
I did the test again on a simple .NET WCF webservice.
In the zip included, all the wsdl and xsd are included (untouched) , + the stack trace in Petals Studio.
I did try to generate the Provider directly from the webservice URI, and also by loading the wsdl file from the filesystem.
Thanks

Philip
Studio_wsdl_problem.zip
Reply | Threaded
Open this post in threaded view
|

Re: Cannot generate provider in petalsstudio

Vincent Zurczak
Hi,

I have taken the last WSDL.
The imports are all referenced by URL ( http://accept.xxxx/perfo_wcfservice/n_test.svc?wsdl=wsdl0 ). Since this URL is not available, I have to update the "location" and "schemaLocation" attributes. The resulting WSDL is valid and successfully imported in the studio (version 1.3.2).

I guess that when you loaded the WSDL from the local file system, the WSDL was also referencing the imports by the full URL (and not a relative one). Is that right?

If true, then the only explanation is that there is a bug with the import URL.
I will investigate further this part. ;)
« Petals M.D. »
Reply | Threaded
Open this post in threaded view
|

Re: Cannot generate provider in petalsstudio

Vincent Zurczak
This post has NOT been accepted by the mailing list yet.
Hi,

Phillp, could you test a more recent version to see if this problem still occurs?
I had made some changes in the WSDL import and I would like to test if it also fix your issue.
« Petals M.D. »
Reply | Threaded
Open this post in threaded view
|

Re: Cannot generate provider in petalsstudio

Vincent Zurczak
This post has NOT been accepted by the mailing list yet.
I finally found a web-hosted WSDL that allowed me to reproduce the problem.
=> http://jira.petalslink.com/browse/PETALSSTUD-287
« Petals M.D. »
12