@Dan: sorry for this duplicate .. I always forget to use reply all
instead of reply. So the message was not delivered to the list.
Daniel Kulp schrieb:
On Thu October 1 2009 4:48:55 am Christian Schneider wrote:
Hi Dan,
for CXF-2275 there is currently no way to include the wsdl in the jar of
the current project. I think this should be added as you explained that
in some cases the wsdl is necessary at runtime.
I'm not so sure this is really necessary. I think the best option would be
for them at runtime to specify the location of the "live" wsdl when creating
the Service object. Like 'http://blah.com/services/foo?wsdl"; or similar.
Thus, the wsdl wouldn't need to be added to the jar, but could also be used.
Why do you think a link to a external location is a good idea here? It
would mean that the service implementation depends on the server that
hosts the WSDL. The advantage of adding the WSDL to the jar would also
be that it is documented which WSDL was used when building the jar.
I also have to still add a test for the feature. Trygve advised to use
maven project with two subprojects for the test. One that creates the
wsdl and one that includes it and builds code from it.
I plan to add this to the systests.
Ick.. Have fun. :-) I really hate trying to write tests for maven
plugins. I'm not sure, but you MAY be able to look at the unit test
frameworks for the remote-resources plugin. It supposedly uses the maven
invoker stuff to invoke maven internally. Not really sure though.
I have almost finished the test. I added a subproject to systests named
wsdl_maven that contains the two subprojects.
So at the moment the only test is to create and retrieve the wsdl and
generate code. Some more advanced method would of course be better.
Do you think this could work for the start?
Greetings
Christian
--
Christian Schneider
---
http://www.liquid-reality.de
