Hi.
As suggested I break up my questions into separate emails. This one
covers the problems I encountered when trying to compile my wsdl.
--------------------------------------------------------------------------------------------------------
Concerning wsdlmerge:
Looking through your SAS.wsdl, I was curious why you did a
<wsdl:import> of the WSRF/WSN wsdls. At least when I created my
(much simpler) WS-Resource I did not have to do that.
I imported them in the SAS.wsdl so that I could reuse the message
definitions contained in them. Well, as compiling that wsdl did not work
I created the SASallinone.wsdl which does not import the WSRF/WSN wsdls
but instead imports the respective schema and defines the required
messages itself. So wsdlmerge did not work for me, but that is ok if
creating code via wsdl2java works in the end.
--------------------------------------------------------------------------------------------------------
Concerning wsdl2java:
Allen wrote:
C:\muse-test\wsdl>wsdl2java.bat -j2ee mini
-wsdl SASallinone.wsdl -output test -verbose
WARNING: [ID = 'NoWSRPSchema'] No WS-RP schema found
I'm not quite sure, but this may be because you don't have
ResourceMetadataDescriptor document attached to your SAS portType as
well as a reference to wsrf-rp:ResourceProperties reference. Perhaps
someone can correct me on this?
Vinh wrote:
3) The "No WS-RP schema found" can safely be ignored. It's probably
because your service has WSRP properties but no .wsrmd file, which is
not required.
I just read the wsrmd spec and added the specific attributes to the SAS
portType and created a metadata descriptor file in the directory of the
wsdl. After some trials wsdl2java accepted my changes (i.e. it did no
longer complain about wrong names or invalid wsdlLocation - however, the
warning is still there. So I think it was not the missing wsrmd file.
Allen wrote:
Another point: I noticed that you've split your schema definition for
the same namespace into two parts
...
I am not sure how a parser will interpret this, but my understanding
was that each <xsd:schema></xsd:schema> pair is separate
from the other. Was there a reason you did not include the imports and
message definitions in one <xsd:schema> pair? Also, I assume that
all the imported documents are defined in the
http://www.opengis.net/sas/1.0.0 namespace or have no namespace?
All of the imported documents (which begin with OGC-SAS) have
targetNamespace http://www.opengis.net/sas/1.0.0. The reason why I did
not put the includes and additional definitions (the
SasResourceProperties and ServiceException) into one xsd:schema element
is because I simply did not think about this possibility. :-) I have put
them into one schema element now.
To summarize: I believe that wsdl2java now works for me. At least it
generated the artifacts based upon my wsdl files.
Cheers,
Johannes
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
