From: Narayana Rallabandi <Narayana.Rallabandi_at_Sun.COM>
Date: Fri, 19 Dec 2008 07:09:05 +0530

Hi,

I have a problem with respect to referenced XSD in the BPEL Projects.

    * In the BPEL mapper when I have an xsd that is referencing another
      XSD (using a ../.. which would be a relative path) which is in
      another folder and if I give a relative path its giving error
      during deployment that it can not reference. (ref. stack below)
    * I had to have the import statements with respect to the other XSDs
      that are referenced from with in the top XSD under use so that
      they appear in the BPEL mapper for drilling into it to look at
      it's elements. (XMLSpy / TIBCO etc have all worked without any
      workaround!! )
    * The other thing I had to do is to have all the XSDs in the same
      folder as that of the TOP XSD .. Is there any work around for the
      same?
    * If I am using the XSDs with out namespace the "the editor does not
      know where to lookup the schema" it can not show up in the mapper
      .. Are we going to have this feature if Yes, is there any time
      line for the same?
    * I have one more observation with respect to XSD import.. Since I
      am having issue with this I tried JAXB way of handling this and
      tried to compile the xsds. I had hit error attached here.
    * I had to alter a couple of XSDs because of the following error
      while building the attached project: (I am attaching the modified
      XSDs separately for reference)
          o

            com.sun.messaging.jmq.jmsserver.util.BrokerException: Start
            message index needs to be in between 0 and -1

                    at
            com.sun.messaging.jmq.jmsserver.core.Destination.getSysMessageIDs(Destination.java:2117)

                    at
            com.sun.messaging.jmq.jmsserver.data.handlers.admin.GetMessagesHandler.handle(GetMessagesHandler.java:140)

                    at
            com.sun.messaging.jmq.jmsserver.data.handlers.admin.AdminDataHandler.handle(AdminDataHandler.java:247)

                    at
            com.sun.messaging.jmq.jmsserver.data.PacketRouter.handleMessage(PacketRouter.java:181)

                    at
            com.sun.messaging.jmq.jmsserver.service.imq.IMQIPConnection.readData(IMQIPConnection.java:1493)

                    at
            com.sun.messaging.jmq.jmsserver.service.imq.IMQIPConnection.process(IMQIPConnection.java:663)

                    at
            com.sun.messaging.jmq.jmsserver.service.imq.OperationRunnable.process(OperationRunnable.java:170)

                    at
            com.sun.messaging.jmq.jmsserver.util.pool.BasicRunnable.run(BasicRunnable.java:493)

                    at java.lang.Thread.run(Thread.java:619)

            INcoming message

            BPCOR-6151:The process instance has been terminated because
            a fault was not handled; Fault Name is
            {http://docs.oasis-open.org/wsbpel/2.0/process/executable}selectionFailure;
            Fault Data is null

            com.sun.jbi.engine.bpel.core.bpel.exception.StandardException:
            I18N: BPCOR-3025: Selection Failure occurred in
            BPEL({http://enterprise.netbeans.org/bpel/TestDeliveryAdd/TestDeliveryAdd}TestDeliveryAdd)
            at line 29!

            BPCOR-6129:Line Number is 29

            BPCOR-6130:Activity Name is Assign1

                    at
            com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELInterpreter.createVirtualFaultUnit(BPELInterpreter.java:234)

                    at
            com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELInterpreter.execute(BPELInterpreter.java:202)

                    at
            com.sun.jbi.engine.bpel.core.bpel.engine.BusinessProcessInstanceThread.execute(BusinessProcessInstanceThread.java:98)

                    at
            com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELProcessManagerImpl.process(BPELProcessManagerImpl.java:1001)

                    at
            com.sun.jbi.engine.bpel.core.bpel.engine.impl.EngineImpl.process(EngineImpl.java:258)

                    at
            com.sun.jbi.engine.bpel.core.bpel.engine.impl.EngineImpl.process(EngineImpl.java:1229)

                    at
            com.sun.jbi.engine.bpel.BPELSEInOutThread.processRequest(BPELSEInOutThread.java:632)

                    at
            com.sun.jbi.engine.bpel.BPELSEInOutThread.processMsgEx(BPELSEInOutThread.java:305)

                    at
            com.sun.jbi.engine.bpel.BPELSEInOutThread.run(BPELSEInOutThread.java:191)

            *Caused by:
            com.sun.xml.transform.sware.ElementNotFoundInComplexTypeException:
            Particle not found in the complex type.
            element={urn:nzl:telecom:SIDPhaseVIII}city,
            complexType={urn:nzl:telecom:SIDPhaseVIII}UrbanPropertyAddress*

                    at
            com.sun.xml.transform.sware.impl.DOMSorter.checkSortNeeded(DOMSorter.java:168)

                    at
            com.sun.xml.transform.sware.impl.DOMSorter.checkSortNeeded(DOMSorter.java:245)

                    at
            com.sun.xml.transform.sware.impl.ReorderTransformerImpl.transform(ReorderTransformerImpl.java:227)

                    at
            com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.AssignUnitImpl.transformDocument(AssignUnitImpl.java:443)

                    at
            com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.AssignUnitImpl.validateOrAndTransformVariable(AssignUnitImpl.java:396)

                    at
            com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.AssignUnitImpl.doAction(AssignUnitImpl.java:324)

                    at
            com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.CodeReUseHelper.executeChildActivities(CodeReUseHelper.java:65)

                    at
            com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.StructuredActivityUnitImpl.executeChildActivities(StructuredActivityUnitImpl.java:193)

                    at
            com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.StructuredActivityUnitImpl.doAction(StructuredActivityUnitImpl.java:93)

                    at
            com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.SequenceUnitImpl.doAction(SequenceUnitImpl.java:95)

                    at
            com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.CodeReUseHelper.executeChildActivities(CodeReUseHelper.java:65)

                    at
            com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.StructuredActivityUnitImpl.executeChildActivities(StructuredActivityUnitImpl.java:193)

                    at
            com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.BPELProcessInstanceImpl.doAction(BPELProcessInstanceImpl.java:650)

                    at
            com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELInterpreter.execute(BPELInterpreter.java:147)

                    ... 7 more
    *

The vendor not be willing to modify the XSDs since they could process
the same XSDs either in XMLSpy, other XML processors or Apache. Is going
by the route of AXIS the only way ?

I request for comments / suggestions / pointers if any. I am also
attaching the project containing XSDs for taking a look. Since this
problem spans multiple things I am posting to wider section. I request
each one of you take a look at the respective pieces or if you have
comments on other things please pass on!

Thanks,
Narayanaa

Stack trace for reference:

In addition to the schema change we had to move all the schemas into a
single folder, as this is a known issue in JCAPS

Note: /*Place all schemas in single folder otherwise we will get the
following error at the time of deployment*/

 

ERROR: Failed execution of Start: TestBillingSchemasFolderCA

    * Component: sun-bpel-engine

      *ERROR: (BPJBI-4001:BPELSE) BPJBI-7007:Service unit:
TestBillingSchemasFolderCA-TestBillingSchemasFolder failed to load
deployment:
E:\JCAPS6\appserver\domains\domain1\jbi\service-assemblies\TestBillingSchemasFolderCA\TestBillingSchemasFolderCA-TestBillingSchemasFolder\sun-bpel-engine
for:
{http://enterprise.netbeans.org/bpel/StubsBilling/Billingopr}PartnerLink1:
Service name: SoapRole_myRole : Endpoint name: java.lang.Exception:
BPJBI-7009:An activated endpoint already exits. {5}*

* * Component: sun-http-binding*

* ERROR: (SOAPBC_INIT_1) HTTPBC-E00203: Initialization failed.
java.lang.Exception: HTTPBC-E00362: Failed to resolve the referenced
schema at URI location:
../XSD/BES-API-BillingAccountManagementServiceInterface.xsd*

Cleaning up...

[stop-service-assembly]

    Stopping a service assembly...

        host=localhost

        port=4848

        name=TestBillingSchemasFolderCA

ERROR: Failed execution of Stop: TestBillingSchemasFolderCA

ERROR: (JBIMA0486) Cannot stop service assembly
TestBillingSchemasFolderCA. Service assembly is already shutdown.

C:\Documents and Settings\rr0019941\My
Documents\NetBeansProjects\TestBillingSchemasFolderCA\nbproject\build-impl.xml:213:
Start failure.

BUILD FAILED (total time: 23 seconds)