Hi, I've been reading the tutorial on http://wiki.jboss.org/wiki/Wiki.jsp?page=WebservicesAndEJB3 about using EJB3 in a web service project.
What happens in this tutorial is that a EJB2.1 Session Bean is used as an intermediate control to the underlying EJB3 beans. So I have an EJB2.1 SB that speaks to a (local) EJB3 SB that handles en persists EJB3 Entity beans. Now, the thing is: I made a wsdl file (manualy) and I used a XML Schema in the type definition. In one function the wscompile task generates an class that has the same name as one of the entity beans. And in fact, they are exactly the same except for the package-name. Do I have to convert between the 2 types programmaticaly? Or is there a way to simplify this process? My second idea was to have the packageName that corresponds to the EJB3 Entity beans in the wscompile config.xml. That way, the beans that are generated by wscompile would have the same packagename as the entity beans. But that didn't work out quite allright. Maybe if I talk to the underlying EJB3 SB I should use the remote interface so I can "narrow" it to the generated (wscompile) classes. Any ideas or experiences around this subject? greetings, Kristof Taveirne View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3920989#3920989 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3920989 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
