Hello Masahiro,
Please read in line for my responses to your questions....In general we
are currently in the process of (re)writing docs for all three projects
and will hopefully resolve any confusion.
Thanks!
-Sal
>Hello.
>
>
>My name is Masahiro Kurosawa.
>Give me a few minutes to answer some questions.
>
>At first, about
Tutorial(http://ws.apache.org/ws-fx/wsrf/tutorial/index.html).
>
>(1) About "Introduction" section of "Runing Apollo's Wsdl2Java tool on
>a WSRF WSDL" page.
>Q. What's "a resource.cfg file"? Such a file not found...
>
The resource.cfg file is actually called jndi-config.xml ....At some
point we must have renamed the file and did not change the documentation
on this. The file is generated when Wsdl2Java is called. The file
contains JNDI information about your service/resource and generated home.
>(2) About "Implementing the SetResourcePropertyCallback" section of
>"Writing Callback Objects" page.
>Q. deleteProperty example says Apollo will never call delete for a
>prop whose minOccurs != 0, but Comment property in FileSystem.wsdl is
minOccurs="0". Is it just 'cause Tutorial does not be >synchronized
>with actual WSDL file?
>
You are correct. The docs are currently not in synch with the
Filesystem.wsdl. The comment in the docs make it seem like the Comment
resource property has a minOccurs > 0...And is saying that delete(..)
will never be called. Upon inspection of the WSDL file, it has a
minOccurs="0" which means delete(..) will be called!!!!
I'm glad you caught this!! I can see you understand what we meant...even
if our docs were bad :-)
>Then about tools for development of services.
>
>(3) Is it same in final release version that we must copy template WSDL
>file and uncomment the blocks of portTypes and resoruce properties we
want to support, or just 'cause beta version?
>I except such tools as "WSDLPreprocessor" (called "GTWSDL2WSDL" in
>older version) or "GenerateBinding" that Globus Toolkit 4 contains.
>
The template wsdl is what we currently use to help you build your wsdl
file. You may write it entirely by hand if you wish, we are just trying
to make it less frustrating to write.
We opted against the use of the Globus GTWSDL2WSDL since it relied on a
proprietary way of dealing with WSDL inheritance, and we know that WSDL
inheritance is being define in newer versions of the WSDL
specification. While we thought it is a useful utility, we did not want
to confuse things by including it.
I believe an ideal tool would be some sort of a gui-based tool which
would allow you to choose the port types you would like and add your own
stuff, then finally generate the wsdl for you....but that really isn't
on the road map.
>(4) Will the files generated by Wsdl2Java/WsnWsdl2Java tool be bound
>together as an archive like GAR file? I hope *.class files be one JAR
>file at least when final version is released.
>
The files generated by Wsdl2Java (and all its extensions) will be
written into directories by default. The generated XmlBeans classes
will always be jarred.
We will probably add something to the generated build.xml file to jar
all the class files before deployment (or maybe after compile)....
The reason we cannot simply jar the output from Wsdl2Java is because you
will need to implement some code, so from that perspective you wouldn't
want the files compiled straight out of Wsdl2Java.
Once you've implemented your code and you type: >ant compile deploy
We should jar the class files and deploy to your webapp. We all agree
that this would make it easier for you to delete the code from the
webapp etc....
Hope that helps!!
Thank you,
-Sal Campana
>Regards.
>
>-----
>Masahiro Kurosawa
>- Hitachi, Ltd., Software Divisition
>- [EMAIL PROTECTED]
------------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
