my actual case is that i have one EJB module that was never part of an
enterprise app - has some entity beans and a SFSB (call it x).
the other EJB module (originally part of an enterpise app) has one SLSB
(call it y).
and, there is the war module.
i deploy the EJB module containing "x". beautiful - before i can blink
my eyes, the module is deployed and the glassfish log says a few
interesting things like: **RemoteBusinessJndiName: persistence;
remoteBusIntf: "x"
then i deploy the EJB module containing "y". marvelous - moments later
the module is deployed and the glassfish log says:
**RemoteBusinessJndiName: configure; remoteBusIntf: "y"
things are going so good, but ...
i deploy the war module. the first thing the glassfish log says is:
Class [ L"x" ] not found. Error while loading [ "y"]
Error in annotation processing: java.lang.NoClassDefFound: L"x" ;
then the log continues saying great things about initializing Java
Server Faces and Seam.
the log says that the web-app failed to deploy, but the admin console
shows that the web-app did deploy.
i am guessing that glassfish is maintaining the JNDI names for "x" and
"y". "x" is remote to "y". "x" is used by "y" - but, those two modules
appear to be happy. only when the web-app deploys, it complains.
i don't get it.
note that "persistence" and "configure" are the mappedNames of "x" and
"y", respectively.
note that this email is also posted on the openesb user's maillist.
sorry about the cross post - it was a mistake on my part. i am keeping
this thread going because Mr Gainty was graciously providing some ideas.
________________________________
From: Martin, Ray
Sent: Friday, February 27, 2009 9:11 AM
To: users_at_glassfish.dev.java.net
Subject: RE: RE: enterprise app modules added to composite app
i have Seam running in Glassfish from Netbeans enterprise app.
the thing that bit me for a while was that jboss-seam.jar CANNOT be in
the war module - it can reside as a library only in the ejb module. i
have all other seam jars added to both the ejb module and the war
module.
when deploying an enterprise app, there must be something going on under
the covers of Netbeans that i do not know anything about, but it is
apparently very helpful. because (though it takes forever) the enterpise
app with seam will deploy and run. but, when moving to a composite app,
whatever was doing me 'big favors' in the enterprise app does not do the
same because a composite app is a different paradigm. currently, i am
trying to take just the war module adn the ejb module and deploy them
separately to Glassfish (not deploying the enterprise app). one of the
first things that i did was to change the interface off the (only one
for a started) EJB from local to remote and set a global JNDI name in
ejb-jar.xml and set the following in the EJB -
@Stateful(mappedName="configure")
while trying to individually deploy the ejb module and the war module, i
have been making progress. i am at the point of working on
components.xml to assure that the war module is aware of the bean in the
ejb module.
i was going to share the error that i am currently getting, but my
glassfish will not start this morning - getting an "MBean registry not
found"
________________________________
From: Martin Gainty [mailto:mgainty_at_hotmail.com]
Sent: Wednesday, February 25, 2009 3:40 PM
To: Users GlassFish.dev.java.net
Subject: RE: enterprise app modules added to composite app
Ive been able to get SEAM to work in JBOSS (but not GF)
supposedly.. these SEAM projects are working in GF..
there are configuration files missing from build scripts so building
means
googling for the build projects..
If you're under time pressure I would stick with SEAM deploys (2.2) from
Jboss
http://www.seamframework.org/
let me know if are able to get your seam app deployed in GF..
https://techdayscode.dev.java.net/servlets/ProjectDocumentList?folderID=
7555
Martin
______________________________________________
Disclaimer and confidentiality note
Everything in this e-mail and any attachments relates to the official
business of Sender. This transmission is of a confidential nature and
Sender does not endorse distribution to any party other than intended
recipient. Sender does not necessarily endorse content contained within
this transmission.
________________________________
Date: Wed, 25 Feb 2009 10:33:49 -0500
From: armart3_at_tycho.ncsc.mil
To: users_at_glassfish.dev.java.net
Subject: RE: RE: enterprise app modules added to composite app
Thanx.
i too have domain1 with my web.xml located respective to yours.
my web page is built by the EJB module - Seam.
my current line of chasing around in circles is that possibly the local
interface on the ejb from the ejb-module of the enterprise app is no
longer valid in a composite app. so, i changed the interface of the EJB
to Remote. i added an enterprise-beans tag to ejb-jar.xml. the tag is
not liked - on deploy, i get a complaint about that tag requires
"
http://java.sun.com.xml.ns/javaee":ejb-client-jar
<
http://java.sun.com.xml.ns/javaee%22:ejb-client-jar%20>
i have yet to learn the meaning of this and how to fix - or even if i am
chasing in the right direction.
________________________________
From: Martin Gainty [mailto:mgainty_at_hotmail.com]
Sent: Wednesday, February 25, 2009 9:47 AM
To: Users GlassFish.dev.java.net
Subject: RE: enterprise app modules added to composite app
Ray
depends on the location of your webapps web.xml and sun-web.xml
configuration files
$GLASSFISH_HOME/domains/domain1/generated/xml/j2ee-modules/hello/WEB-INF
/web.xml contents
<web-app version="2.4" xmlns="
http://java.sun.com/xml/ns/j2ee"
xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="
http://java.sun.com/xml/ns/j2ee
http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
<display-name>hello</display-name>
<distributable/>
</web-app>
$GLASSFISH_HOME/domains/domain1/generated/xml/j2ee-modules/hello/WEB-INF
/sun-web.xml contents
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE sun-web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Application
Server 9.0 Servlet 2.5//EN"
"
http://www.sun.com/software/appserver/dtds/sun-web-app_2_5-0.dtd">
<sun-web-app>
<context-root>hello</context-root>
</sun-web-app>
http://localhost:8080/hello
Assuming your hello webapp is deployed to a working domain (in my case
that is domain1)
HTH
Martin
USCitizen(Contractor)
______________________________________________
Disclaimer and confidentiality note
Everything in this e-mail and any attachments relates to the official
business of Sender. This transmission is of a confidential nature and
Sender does not endorse distribution to any party other than intended
recipient. Sender does not necessarily endorse content contained within
this transmission.
________________________________
Date: Wed, 25 Feb 2009 08:53:49 -0500
From: armart3_at_tycho.ncsc.mil
To: users_at_glassfish.dev.java.net
Subject: enterprise app modules added to composite app
i have an enterprise app, Example with the usual modules Example-ejb and
Example-war.
in a composite app, i select "Add JBI Module" - from the selection
window, i add Example-ejb adn Example-war.
the sun-web.xml file in Example-war says the context is /Example-war
after deploying the composite app, and setting the browser to
http://localhost:8080/Example-war - i can only get 503 requested service
not available.
the admin console shows the modules Example-war and Example-ejb deployed
in the composite app.
the context has not changed has it?
________________________________
Windows Live(tm) Hotmail(r)...more than just e-mail. See how it works.
<
http://windowslive.com/howitworks?ocid=TXT_TAGLM_WL_t2_hm_justgotbetter
_howitworks_022009>
________________________________
Access your email online and on the go with Windows Live Hotmail. Sign
up today.
<
http://windowslive.com/online/hotmail?ocid=TXT_TAGLM_WL_HM_AE_Access_02
2009>