WSDL import does not import my schema file

Question

I have a local WSDL that imports a schema. When I create a new partner link, I get the dialogue box that tells me it has to make a local copy. It makes the local copy. It still refers to my schema import (which has a relative path) but it does not move the schema as well.
Am I doing something wrong or is this a bug?
Thanks,
Greg

Answer 1

This is not exactly the behavior I am seeing.
This is what I see: Lets say that I have a WSDL file that resides in c:\mywsdls\pp-wsif.wsdl. It has an import statement in my wsdl for the schema types that is relative (../schema/schema.xsd). Lets also assume that my BPEL process project resides in c:\<BPEL_HOME>\mywork\bpelproj.
When I go to create a partner link using my local wsdl file, two wsdl files show up in my BPEL project. One is an exact copy of pp-wisf.wsdl and one is the pp-wisfRef.wsdl. The pp-wisfRef.wsdl has the partner link stuff and it also references the wsdl in c:\<BPEL_HOME>\mywork\bpelproj, not my original wsdl.
Now is when my problem comes up. the "new" pp-wisf.wsdl file still has that import with a relative path. But, since the wsdl file got moved and the xsd did not that relative path is no longer valid. Thus, my origial problem.
There is an obvious work around to edit my wsdls to fix the paths but I am wondorering if I am doing something wrong or if this is in fact a bug.
Greg