bingo - just changing to ejb 2.1 fixed the service-endpoint in the ejb-jar.xml!

So using WSEEdoclet (with ejbdoclet) can:

*Generate ejb-jar.xml (with service-endpoint defined).
*Generate the actual *Endpoint.java files.
*Generate a reasonable webservices.xml file.

WSEE can also do:
*create basic RPC-Literal META-INF/wsdl/*.wsdl files.
*create simple jaxrpc-mapping.xml files.

The WSDL and the JAXRPC-MAPPING.XML files are the next step to find a better 
solution. 

-Be able to automatically handle complex types (Array of entity bean 
ValueObjects is a good testcase).
-Move towards WS-Basic-Profile-1.0 compliance (if needed?).

Now I feel comfortable looking at WSCOMPILE, WSDL4J, and similar tools for the 
WSDL files and the JAXRPC mapping.

View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3884042#3884042

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3884042


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to