« Return to Thread: Error when deploying a Composite Project

Re: Error when deploying a Composite Project

by Bugzilla from dchris@gmail.com :: Rate this Message:

Reply to Author | View in Thread

I used Glassfish and OpenESB which were installed by Netbeans 6.5.1 (full). I don't know exactly which version of OpenESB was provided. I will see if I can update then.

Regards,
Chris.

On Wed, Apr 15, 2009 at 11:44 PM, Jun Qian <Jun.Qian@...> wrote:
Hi Chris,

I tried your project with GlassFish ESB v2.1 Milestone 2 and I didn't have any deployment issue. Which version of runtime did you use?

BTW, you might want to join the open-esb users mailing list [1]. You will get more prompt design time and runtime help from there.

Thanks,
Jun

[1] https://open-esb.dev.java.net/MailingLists.html



Chris wrote:
Hi,

I'm experiencing a problem when deploying a BPEL process (and the error does not really help me):
WARNING: (JBIMA0405)  le démarrage de l'assemblage de services CompoEmergency a partiellement réussi ; certaines unités de service n'ont pas démarré.
   * Component: sun-bpel-engine
     ERROR: (BPJBI-4001:BPELSE) BPJBI-7004:Service unit CompoEmergency-EmergencyBPELEngine failed to load deployment /home/chris/apps/glassfish-v2.1/domains/domain1/jbi/service-assemblies/CompoEmergency/CompoEmergency-EmergencyBPELEngine/sun-bpel-engine : BPJBI-6024:Error while loading BPEL file /home/chris/apps/glassfish-v2.1/domains/domain1/jbi/service-assemblies/CompoEmergency/CompoEmergency-EmergencyBPELEngine/sun-bpel-engine/EmergencyItinerary.bpel, Exception details are Cannot parse BPEL (see below):
==> Compiling XSDs failed (file:/home/chris/apps/glassfish-v2.1/domains/domain1/jbi/service-assemblies/CompoEmergency/CompoEmergency-EmergencyBPELEngine/sun-bpel-engine/Partners/ItineraryService/ItineraryServiceService.wsdl, file:/home/chris/apps/glassfish-v2.1/domains/domain1/jbi/service-assemblies/CompoEmergency/CompoEmergency-EmergencyBPELEngine/sun-bpel-engine/Partners/RoadStatusService/RoadStatusServiceService.wsdl, file:/home/chris/apps/glassfish-v2.1/domains/domain1/jbi/service-assemblies/CompoEmergency/CompoEmergency-EmergencyBPELEngine/sun-bpel-engine/Partners/WasteCollection/WasteCollectionService.wsdl).

I guess there is a problem with my XSD file? but which one and why? XSD files were automatically created, I did not edit anything manually.

Note that my BPEL process fails validation with the following output:
/home/chris/NetBeansProjects/ASSET/EmergencyBPELEngine/src/EmergencyItinerary.bpel:26: 8
ERROR: The variable "GetCollectionTrucksLocationIn" is not initialized, but used.
/home/chris/NetBeansProjects/ASSET/EmergencyBPELEngine/src/EmergencyItinerary.bpel:25: 8
ERROR: The variable "GetAdvisedAreasIn" is not initialized, but used.
/home/chris/NetBeansProjects/ASSET/EmergencyBPELEngine/src/EmergencyItinerary.bpel:24: 8
ERROR: The variable "GetDiscouragedAreasIn" is not initialized, but used.

This validation problem is caused by the following bug:
http://openide.netbeans.org/issues/show_bug.cgi?id=149735

Since the BPEL file looks correct, I checked "Allow build and deploy with errors" to build and deploy the project.
I don't know if the deployment problem is caused by the validation problem: it does not look like it since it would not affect the XSD files.

Regards,
Chris.

P.S: I'm using Netbeans 6.5.1


--

Jun Qian

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


 « Return to Thread: Error when deploying a Composite Project