Hi, currently when I deploy enterprise modules manually, their remote EJBs are null (not injected). When I deploy via NetBeans ide, RMI is someway setup and EJBs are injected. My question is what needs to be configured in Glassfish (2.x) so I could deploy modules manually, not via ide.
views:
224answers:
1
A:
(...) what needs to be configured in Glassfish (2.x) so I could deploy modules manually, not via IDE.
Nothing special AFAIK. Either:
Use autodeploy: copy foo.war/foo.ear/foo-ejb.jar/foo-application-client.jar (anything that can be legally deployed) to the
autodeploydir, which is typically$GFv2_HOME/domains/domain1/autodeploy.Use the admin console: On the right pane, under Common Tasks, click Deploy Enterprise Application (.ear).
Use the command line: with the
asadmin deploycommand line tool. Seedeploy.
Refer to the Chapter 3 Deploying an Application for full reference.
Pascal Thivent
2010-04-14 23:42:49
I always deploy via admin console and anything works except remote EJBs.
Zeratul
2010-04-14 23:47:26
@Zeratul How are they packaged exactly?
Pascal Thivent
2010-04-14 23:51:16
They are packaged as jars. They were EJB modules and the web module is war. EJB modules use cross calling of remote EJB interfaces.
Zeratul
2010-04-16 00:38:37
@Zeratul Yeah, I know that they are packaged as JAR. But what does it content exactly? Please show the content of one ejb-jar for one EJB in your question.
Pascal Thivent
2010-04-16 00:41:43
eg: http://147.32.104.190/ejb.png. -- the Validator ejb reference in other module is not injectedOn the other thought maybe they all ned to be packaged in single ear (maybe that's what NB does on the background)
Zeratul
2010-04-16 00:46:37