> Actually, in Glassfish there are no developer-visible stubs in the Remote case either. If
> the caller and target EJB are in the same .ear, there is no difference in terms of the
> packaging requirements between the Local EJB view and the Remote EJB view.
This means to me that ALL WAR projects need to become part of the EAR project
containing the EJBs an ENTITIES ... right?
To maintain a somewhat *faster* development environment while editing JSP/JSP
sources I wanted to have the WAR separate from the slower deploying fat EAR.
And I tried to work this way but ran into problems.
Calling the remote interfaces of my session beans was no problem but when I
started sending Entity POJOS through the remote interface I ran into Corba
Marshalling Exceptions.
Do I have do use a kind of CLIENT jar with the separate deployed WAR??
Thanks for your comments,
Bernd
[Message sent by forum member 'bernd_zedv' (bernd_zedv)]
http://forums.java.net/jive/thread.jspa?messageID=253999