Reference issues with Open-ESB (Again)

5 messages Options
Embed this post
Permalink
Paul Perez

Reference issues with Open-ESB (Again)

Reply Threaded More More options
Print post
Permalink
Hello,

Once again I have some difficulties to create A reference project where I would be able to store the XSD and WSDL I want to reuse many times in my application.
A project named "ReferenceBPEL" contains many xsd and WSDL.

I create another named "DBServices". In this project, there is a wsdl that import 2 xsd found in "ReferenceBPEL". I can build the project without problem.

When deploying the application server is not able to find the referenced schemas. In the zip file used for the deployment, we can find the referenced schema in the metadata directory.
BPJBI-5009: SU.inti for TestCompApp-DBServices is started, Business Process packaged in this SU will be deployed
Failed to parser xsd document
javax.wsdl.WSDLException: WSDLException (at /definitions/types/xsd:schema): faultCode=OTHER_ERROR: An error occurred trying to resolve schema referenced at 'ReferenceBPEL/schemas/GenericFault.xsd', relative to 'file:/F:/ESB/GlassFishESBv21/glassfish/domains/domain1/jbi/service-assemblies/TestCompApp/TestCompApp-DBServices/sun-bpel-engine/wsdl/CustomerServices.wsdl'.: java.io.FileNotFoundException: This file was not found: file:/F:/ESB/GlassFishESBv21/glassfish/domains/domain1/jbi/service-assemblies/TestCompApp/TestCompApp-DBServices/sun-bpel-engine/wsdl/ReferenceBPEL/schemas/GenericFault.xsd
        at com.sun.wsdl4j.ext.impl.WSDLReaderEx.parseSchema(WSDLReaderEx.java:685)
        at com.ibm.wsdl.xml.WSDLReaderImpl.parseSchema(Unknown Source)
        at com.ibm.wsdl.xml.WSDLReaderImpl.parseTypes(Unknown Source)
        at com.ibm.wsdl.xml.WSDLReaderImpl.parseDefinitions(Unknown Source)
....


It seems to be a regression, since this feature worked well few weeks ago. I am using Glassfish V2.1 and since I wanted to use a reference in a XSLT I had to use the leave the original 2.1. Today I downloaded and installed the last BPEL build. Get the same error

The projects are in attachment.

Thanks for your help

Paul

ReferenceIssues.zip
Jun Qian

Re: Reference issues with Open-ESB (Again)

Reply Threaded More More options
Print post
Permalink
Looks like a regression in the BPEL SE. The service assembly packaging
looks OK to me. The catalog doesn't seem to be used by the BPEL SE.

Regards,
Jun

Paul Perez wrote:

> Hello,
>
> Once again I have some difficulties to create A reference project where I
> would be able to store the XSD and WSDL I want to reuse many times in my
> application.
> A project named "ReferenceBPEL" contains many xsd and WSDL.
>
> I create another named "DBServices". In this project, there is a wsdl that
> import 2 xsd found in "ReferenceBPEL". I can build the project without
> problem.
>
> When deploying the application server is not able to find the referenced
> schemas. In the zip file used for the deployment, we can find the referenced
> schema in the metadata directory.
> BPJBI-5009: SU.inti for TestCompApp-DBServices is started, Business Process
> packaged in this SU will be deployed
> Failed to parser xsd document
> javax.wsdl.WSDLException: WSDLException (at /definitions/types/xsd:schema):
> faultCode=OTHER_ERROR: An error occurred trying to resolve schema referenced
> at 'ReferenceBPEL/schemas/GenericFault.xsd', relative to
> 'file:/F:/ESB/GlassFishESBv21/glassfish/domains/domain1/jbi/service-assemblies/TestCompApp/TestCompApp-DBServices/sun-bpel-engine/wsdl/CustomerServices.wsdl'.:
> java.io.FileNotFoundException: This file was not found:
> file:/F:/ESB/GlassFishESBv21/glassfish/domains/domain1/jbi/service-assemblies/TestCompApp/TestCompApp-DBServices/sun-bpel-engine/wsdl/ReferenceBPEL/schemas/GenericFault.xsd
>         at
> com.sun.wsdl4j.ext.impl.WSDLReaderEx.parseSchema(WSDLReaderEx.java:685)
>         at com.ibm.wsdl.xml.WSDLReaderImpl.parseSchema(Unknown Source)
>         at com.ibm.wsdl.xml.WSDLReaderImpl.parseTypes(Unknown Source)
>         at com.ibm.wsdl.xml.WSDLReaderImpl.parseDefinitions(Unknown Source)
> ....
>
>
> It seems to be a regression, since this feature worked well few weeks ago. I
> am using Glassfish V2.1 and since I wanted to use a reference in a XSLT I
> had to use the leave the original 2.1. Today I downloaded and installed the
> last BPEL build. Get the same error
>
> The projects are in attachment.
>
> Thanks for your help
>
> Paul
>
> http://n2.nabble.com/file/n3935175/ReferenceIssues.zip ReferenceIssues.zip
>  


--

Jun Qian

NetBeans SOA Tools, http://enterprise.netbeans.org
Open ESB Community, http://open-esb.org


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Vladimir Yaroslavskiy

Re: Reference issues with Open-ESB (Again)

Reply Threaded More More options
Print post
Permalink
In reply to this post by Paul Perez
Looks like it is known bug when deployment process can't operate
with the resources located in subfolder of "src" folder.

Paul Perez wrote:

> Hello,
>
> Once again I have some difficulties to create A reference project where I
> would be able to store the XSD and WSDL I want to reuse many times in my
> application.
> A project named "ReferenceBPEL" contains many xsd and WSDL.
>
> I create another named "DBServices". In this project, there is a wsdl that
> import 2 xsd found in "ReferenceBPEL". I can build the project without
> problem.
>
> When deploying the application server is not able to find the referenced
> schemas. In the zip file used for the deployment, we can find the referenced
> schema in the metadata directory.
> BPJBI-5009: SU.inti for TestCompApp-DBServices is started, Business Process
> packaged in this SU will be deployed
> Failed to parser xsd document
> javax.wsdl.WSDLException: WSDLException (at /definitions/types/xsd:schema):
> faultCode=OTHER_ERROR: An error occurred trying to resolve schema referenced
> at 'ReferenceBPEL/schemas/GenericFault.xsd', relative to
> 'file:/F:/ESB/GlassFishESBv21/glassfish/domains/domain1/jbi/service-assemblies/TestCompApp/TestCompApp-DBServices/sun-bpel-engine/wsdl/CustomerServices.wsdl'.:
> java.io.FileNotFoundException: This file was not found:
> file:/F:/ESB/GlassFishESBv21/glassfish/domains/domain1/jbi/service-assemblies/TestCompApp/TestCompApp-DBServices/sun-bpel-engine/wsdl/ReferenceBPEL/schemas/GenericFault.xsd
>         at
> com.sun.wsdl4j.ext.impl.WSDLReaderEx.parseSchema(WSDLReaderEx.java:685)
>         at com.ibm.wsdl.xml.WSDLReaderImpl.parseSchema(Unknown Source)
>         at com.ibm.wsdl.xml.WSDLReaderImpl.parseTypes(Unknown Source)
>         at com.ibm.wsdl.xml.WSDLReaderImpl.parseDefinitions(Unknown Source)
> ....
>
>
> It seems to be a regression, since this feature worked well few weeks ago. I
> am using Glassfish V2.1 and since I wanted to use a reference in a XSLT I
> had to use the leave the original 2.1. Today I downloaded and installed the
> last BPEL build. Get the same error
>
> The projects are in attachment.
>
> Thanks for your help
>
> Paul
>
> http://n2.nabble.com/file/n3935175/ReferenceIssues.zip ReferenceIssues.zip

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Paul Perez

Re: Reference issues with Open-ESB (Again)

Reply Threaded More More options
Print post
Permalink
Hello Vladimir,

Thanks for reply.
I check if your comment can be applied to my case. But unfortunately it does not work. I test succesfully the reference feature with a simple project that surprisingly worked. I spent time to find what is the difference between my project (that does not work) and this simple project (that works).

The difference that creates the bug is :

When the BPEL is in the "process files",  reference feature works
When the BPEL is in a subdirectory of "process files", reference feature does not work.

I did not dive into the generate code but here is the entry point to find the bug AFAIK.

please let me know if you find the same behavior.

Regards

Paul




Vladimir Yaroslavskiy wrote:
Looks like it is known bug when deployment process can't operate
with the resources located in subfolder of "src" folder.

Paul Perez wrote:
> Hello,
>
> Once again I have some difficulties to create A reference project where I
> would be able to store the XSD and WSDL I want to reuse many times in my
> application.
> A project named "ReferenceBPEL" contains many xsd and WSDL.
>
> I create another named "DBServices". In this project, there is a wsdl that
> import 2 xsd found in "ReferenceBPEL". I can build the project without
> problem.
>
> When deploying the application server is not able to find the referenced
> schemas. In the zip file used for the deployment, we can find the referenced
> schema in the metadata directory.
> BPJBI-5009: SU.inti for TestCompApp-DBServices is started, Business Process
> packaged in this SU will be deployed
> Failed to parser xsd document
> javax.wsdl.WSDLException: WSDLException (at /definitions/types/xsd:schema):
> faultCode=OTHER_ERROR: An error occurred trying to resolve schema referenced
> at 'ReferenceBPEL/schemas/GenericFault.xsd', relative to
> 'file:/F:/ESB/GlassFishESBv21/glassfish/domains/domain1/jbi/service-assemblies/TestCompApp/TestCompApp-DBServices/sun-bpel-engine/wsdl/CustomerServices.wsdl'.:
> java.io.FileNotFoundException: This file was not found:
> file:/F:/ESB/GlassFishESBv21/glassfish/domains/domain1/jbi/service-assemblies/TestCompApp/TestCompApp-DBServices/sun-bpel-engine/wsdl/ReferenceBPEL/schemas/GenericFault.xsd
>         at
> com.sun.wsdl4j.ext.impl.WSDLReaderEx.parseSchema(WSDLReaderEx.java:685)
>         at com.ibm.wsdl.xml.WSDLReaderImpl.parseSchema(Unknown Source)
>         at com.ibm.wsdl.xml.WSDLReaderImpl.parseTypes(Unknown Source)
>         at com.ibm.wsdl.xml.WSDLReaderImpl.parseDefinitions(Unknown Source)
> ....
>
>
> It seems to be a regression, since this feature worked well few weeks ago. I
> am using Glassfish V2.1 and since I wanted to use a reference in a XSLT I
> had to use the leave the original 2.1. Today I downloaded and installed the
> last BPEL build. Get the same error
>
> The projects are in attachment.
>
> Thanks for your help
>
> Paul
>
> http://n2.nabble.com/file/n3935175/ReferenceIssues.zip ReferenceIssues.zip

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@open-esb.dev.java.net
For additional commands, e-mail: users-help@open-esb.dev.java.net
Vladimir Yaroslavskiy

Re: Reference issues with Open-ESB (Again)

Reply Threaded More More options
Print post
Permalink
Hello Paul,

It is exactly what I meant. Files in subfolder of src ("Process Files")
are not resolved during deployment. I remember that this bug was filed
against runtime. but just now can't find it's number.

Thanks,
Vladimir

Paul Perez wrote:

> Hello Vladimir,
>
> Thanks for reply.
> I check if your comment can be applied to my case. But unfortunately it does
> not work. I test successfully the reference feature with a simple project
> that surprisingly worked. I spent time to find what is the difference
> between my project (that does not work) and this simple project (that
> works).
>
> The difference that creates the bug is :
>
> When the BPEL is in the "process files",  reference feature works
> When the BPEL is in a subdirectory of "process files", reference feature
> does not work.
>
> I did not dive into the generate code but here is the entry point to find
> the bug AFAIK.
>
> please let me know if you find the same behavior.
>
> Regards
>
> Paul
>
> Vladimir Yaroslavskiy wrote:
>> Looks like it is known bug when deployment process can't operate
>> with the resources located in subfolder of "src" folder.
>>
>> Paul Perez wrote:
>>> Hello,
>>>
>>> Once again I have some difficulties to create A reference project where I
>>> would be able to store the XSD and WSDL I want to reuse many times in my
>>> application.
>>> A project named "ReferenceBPEL" contains many xsd and WSDL.
>>>
>>> I create another named "DBServices". In this project, there is a wsdl
>>> that
>>> import 2 xsd found in "ReferenceBPEL". I can build the project without
>>> problem.
>>>
>>> When deploying the application server is not able to find the referenced
>>> schemas. In the zip file used for the deployment, we can find the
>>> referenced
>>> schema in the metadata directory.
>>> BPJBI-5009: SU.inti for TestCompApp-DBServices is started, Business
>>> Process
>>> packaged in this SU will be deployed
>>> Failed to parser xsd document
>>> javax.wsdl.WSDLException: WSDLException (at
>>> /definitions/types/xsd:schema):
>>> faultCode=OTHER_ERROR: An error occurred trying to resolve schema
>>> referenced
>>> at 'ReferenceBPEL/schemas/GenericFault.xsd', relative to
>>> 'file:/F:/ESB/GlassFishESBv21/glassfish/domains/domain1/jbi/service-assemblies/TestCompApp/TestCompApp-DBServices/sun-bpel-engine/wsdl/CustomerServices.wsdl'.:
>>> java.io.FileNotFoundException: This file was not found:
>>> file:/F:/ESB/GlassFishESBv21/glassfish/domains/domain1/jbi/service-assemblies/TestCompApp/TestCompApp-DBServices/sun-bpel-engine/wsdl/ReferenceBPEL/schemas/GenericFault.xsd
>>>         at
>>> com.sun.wsdl4j.ext.impl.WSDLReaderEx.parseSchema(WSDLReaderEx.java:685)
>>>         at com.ibm.wsdl.xml.WSDLReaderImpl.parseSchema(Unknown Source)
>>>         at com.ibm.wsdl.xml.WSDLReaderImpl.parseTypes(Unknown Source)
>>>         at com.ibm.wsdl.xml.WSDLReaderImpl.parseDefinitions(Unknown
>>> Source)
>>> ....
>>>
>>>
>>> It seems to be a regression, since this feature worked well few weeks
>>> ago. I
>>> am using Glassfish V2.1 and since I wanted to use a reference in a XSLT I
>>> had to use the leave the original 2.1. Today I downloaded and installed
>>> the
>>> last BPEL build. Get the same error
>>>
>>> The projects are in attachment.
>>>
>>> Thanks for your help
>>>
>>> Paul
>>>
>>> http://n2.nabble.com/file/n3935175/ReferenceIssues.zip
>>> ReferenceIssues.zip
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]