Bpel: problems importing schema from http-url

Question

i have problems importing the schema "http://schemas.xmlsoap.org/ws/2003/03/addressing/". I'm using JDeveloper 10.1.3.3.0.4157 and SoaSuite 10.1.3.1.0 with the patch 10.1.3.3.0.
The problem can be reproduced very easily:
* create a new "BPEL Process Project" from template "Synchronous BPEL Process" and use all default settings
     -> deploying to my local app-server works
* add a new variable to the process
     * select "Element" as type
     * click "Browse Elements..."
     * click "Import Schema File..."
     * enter "http://schemas.xmlsoap.org/ws/2003/03/addressing/"
     * select "Imported Schemas/addressing/EndpointReference"
     * finish creating variable
* save all and deploy
     -> the ant console shows the following error:
BUILD FAILED
C:\oracle\JDeveloper\jdev\mywork\TejTest\BPELProcess1\build.xml:79: A problem occured while connecting to server "127.0.0.1" using port "8888": bpel_BPELProcess1_1.0.jar failed to deploy. Exception message is: ORABPEL-05215
Fehler beim Laden von Prozess.
Bei der Prozessdomäne sind folgende Fehler beim Laden des Prozesses "BPELProcess1" (Revision "1.0") aufgetreten: BPEL-Validierung nicht erfolgreich.
Validierung der BPEL-Quelle nicht erfolgreich. Fehler:
[Fehler ORABPEL-10902]: Kompilierung nicht erfolgreich
[Beschreibung]: in "bpel.xml", XML-Parsing nicht erfolgreich. Grund "nicht definiertes Teilelement.
In WSDL-Datei bei "file:/C:/oracle/product/10.1.3.1/OracleAS_1/bpel/domains/default/tmp/.bpel_BPELProcess1_1.0_c64929dfd2dacf95db3c9da081c1797d.tmp/BPELProcess1.wsdl" ist das Teilelement der Nachricht "{http://xmlns.oracle.com/BPELProcess1}BPELProcess1ProcessRequest" in keinem der Schemas definiert.
Vergewissern Sie sich, dass die Schreibweise des QName-Elements korrekt ist und dass der WSDL-Import vollständig ausgeführt wurde.
[Mögliche Behebung]: n/v.
Wenn Sie ein Patch auf dem Server installiert haben, stellen Sie sicher, dass die bpelcClasspath-Domäneneigenschaft die Patch-Klassen enthält.
at com.collaxa.cube.engine.deployment.CubeProcessHolder.bind(CubeProcessHolder.java:285)
at com.collaxa.cube.engine.deployment.DeploymentManager.deployProcess(DeploymentManager.java:862)
at com.collaxa.cube.engine.deployment.DeploymentManager.deploySuitcase(DeploymentManager.java:728)
at com.collaxa.cube.ejb.impl.BPELDomainManagerBean.deploySuitcase(BPELDomainManagerBean.java:445)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
sorry for the german message, i couldn't get the english version. basically it says that "{http://xmlns.oracle.com/BPELProcess1}BPELProcess1ProcessRequest" is not defined in any schema, what is very strange because before importing the schema from http..., the element ...BPELProcess1ProcessRequest has been found.
another strange thing is that if i download the schema from http://schemas.xmlsoap.org/ws/2003/03/addressing/ and import it from a local file, everything works as expected.

Answer 1

When importing a schema there are two attributes to the import element to be aware of: namespace and schemaLocation. I think this is the basis of confusion, particularly where the same value is used for both in this case.
I suspect that the schema import works for ax90033 because the schemaLocation is being specified as "http://schemas.xmlsoap.org/ws/2003/03/addressing/".
The W3C has some further information on this at http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/structures.html#element-import which gives an indication of the complexity that lies behind schema imports.
Peter
http://soastation.blogspot.com