Wittold at the bank we built our ears with an OSGI build
would this help the op insofar as to specifically export-packages of the package names of the beans the op wants to access remotelyThis would have the additional benefit of placing the export-package declaration in the manifest?
http://wso2.org/library/tutorials/develop-osgi-bundles-using-maven-bundle-plugin#Exporting%20packages
http://fusesource.com/docs/esb/4.4/esb_deploy_osgi/BestPractices-BuildBundles.html#BestPractices-BuildBundles-AEPWAV
Dzięki
Dzieki
Martin
______________________________________________
Nie zmienia ani nie zakłóca tego przekazuNie zmienia ani nie zakłóca tego przekazu
Date: Sat, 29 Dec 2012 12:28:59 +0100
Subject: Re: Accessing an EJB in an ear from a war
From: pljosh.mail_at_gmail.com
To: users_at_glassfish.java.net
Yes, you have to package everything into same ear or separate remote interfaces and bundle them with other applications, so they can access remote beans. The fact that this is all single JVM does not matter.
Regards,
Witold Szczerba
---
Sent from my mobile phone.
On Dec 28, 2012 3:18 PM, <forums_at_java.net> wrote:
Hi, thank you for the response mvatkina! So does that mean local EJB access
is only possible within an ear? I cannot have local access in our scenario
described above (from VirtualWeb.war to an EJB in TestEar.ear)? It's the same
Glassfish instance, same JVM...
--
[Message sent by forum member 'chris1234']
View Post: http://forums.java.net/node/893478