Hi,

I'm posting both to pxe + service mix ML since I'm not really sure where the
problem comes from.

My first question is, is the AsyncDemo in ServiceMix the exact same one as the
one in PXE ?
Indeed, I couldn't find the source of the demo (the BPEL + WSDL), and PXE's
async demo has some concrete SOAP over HTTP endpoints hardcoded :
like
 <soap:address location="http://localhost:8080/pxe/soap/async/invoke"/>

is this suppsoed to work in ServiceMix's NMR ??

I thought it was only SOAP in the NMR, not SOAP over HTTP...

same stuff in the BPEL :
<from
expression="'http://localhost:8090/pxe/soap/AsyncProcess/ProcessSVC/CallbackPORT'"/>
there are concrete endpoints...


2) My second question is a technical problem :

I took the async demo, modified the filenames and namespaces.. that's all I
changed.
then I compile and package using a small .bat script :

call rradd -wsdl file:MissionPlanningProcess.wsdl MissionPlanning.rr
call bpelc -rr MissionPlanning.rr -wsdl file:MissionPlanningProcess.wsdl
file:MissionPlanning.bpel
call sarcreate -common MissionPlanning.rr -sysd pxe-system.xml
MissionPlanning.cbp pxe.sar
jar cf output\MissionPlanning-su.zip pxe.sar
cd output
echo creating Service Assembly
jar cf ..\MissionPlanning-sa.jar *
cd ..

I end up having a MissionPlanning-sa.jar, that has :
- META-INF/jbi.xml
- MissionPlanning-su.zip

the jbi.xml is the exact same one as the AsyncProces, except with the filename
modifications :
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<jbi version="1"
  xsi:schemaLocation="http://java.sun.com/xml/ns/jbi  ./jbi.xsd"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
  xmlns="http://java.sun.com/xml/ns/jbi";>

  <service-assembly>
    <identification>
      <name>MissionPlanningSA</name>
      <description>Service Assembly containing just the BPEL
deployment.</description>
    </identification>
    <service-unit>
      <identification>
        <name>MissionPlanning</name>
        <description>BPEL Service Unit</description>
      </identification>
      <target>
        <artifacts-zip>MissionPlanning-su.zip</artifacts-zip>
        <component-name>PxeBpelEngine</component-name>
      </target>
    </service-unit>
  </service-assembly>
</jbi>


so, at this point, given that the BPEL compilation is OK, this should work,
right ?

Here's the errror I get when I deploy it in serviceMix : (I use the asyncprocess
servicemix.xml, my process has the same port names, etc)
ssionPlanning
2005-09-02 10:38:00 com.fs.pxe.jbi.PxeSUManager deploy
GRAVE: Naming conflict PXE system name must be "MissionPlanning"!
[WARN] AutoDeploymentService - -Directory: deploy: Automatic install of .\deploy
\MissionPlanning-sa.jar failed <javax.jbi.management.DeploymentException: Invali
d PXE system name.>javax.jbi.management.DeploymentException: Invalid PXE system
name.
        at com.fs.pxe.jbi.PxeSUManager.deploy(PxeSUManager.java:96)
        at org.servicemix.jbi.framework.DeploymentService.deployServiceUnit(Depl
oymentService.java:495)
        at org.servicemix.jbi.framework.DeploymentService.deploy(DeploymentServi
ce.java:162)
        at org.servicemix.jbi.framework.DeploymentService.process(DeploymentServ
ice.java:106)
        at org.servicemix.jbi.framework.AutoDeploymentService$1.run(AutoDeployme
ntService.java:164)
        at org.apache.geronimo.connector.work.WorkerContext.run(WorkerContext.ja
va:291)
        at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown So
urce)
        at java.lang.Thread.run(Thread.java:595)

[INFO] AutoDeploymentService - -Directory: deploy: Finished installation of arch
ive:  MissionPlanning-sa.jar

And when I deploy the asyncProcess bundled with serviceMix, there is no
problem..
So if someone could give me an idea of what the error exactly comes from...

Thanks a lot,
Sami Dalouche






----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Reply via email to