One of the thing's I'd like to know is, where does Glassfish determine the name of beans associated with a given EJB? Is there a config file someplace that I'm not aware of?
-----Original Message-----
From: Kieran Dunne [mailto:Kieran.Dunne_at_agilex.com]
Sent: Thursday, August 20, 2009 2:31 PM
To: users_at_glassfish.dev.java.net
Subject: FW: Deploying application in domain failed; Error loading deployment descriptors for module [AdapterDocQueryEJB] -- Referencing error: This bundle has no bean of name [AdapterDocQuerySecured]
Mark S. White suggested that I post this to the Glassfish forum instead of the GlassfishESB forum. Original posting follows,
thanks,
Kieran
=========================
Description
Inconsistent results when deploying an EJB module to Glassfish. Operation
has been tried on 4 developer machines; it works on two but fails on the
other two. All four machines have the same build of Glassfish running. On
the machines that can deploy, they can always deploy the EJB. On the
machines that fail, the deployment always fails. Code has been pulled from
subversion; all four machines are attempting to deploy the same source code.
The error message is:
Deploying application in domain failed; Error loading deployment
descriptors for module [AdapterDocQueryEJB] -- Referencing error: This
bundle has no bean of name [AdapterDocQuerySecured]
In the Netbeans IDE, we have confirmed that there is an Enterprise Bean
named AdapterDocQuerySecured as well as a Webservice named
AdapterDocQuerySecured. Under src\conf there is a sun-ejb-jar.xml file.
sun-ejb-jar.xml has this entry:
<ejb
<ejb-nameAdapterDocQuerySecured</ejb-name
<webservice-endpoint
<port-component-nameAdapterDocQuerySecured</port-component-name
<endpoint-address-uri/NhinConnect/AdapterDocQuerySecured</endpoint-address-uri
<login-config
<auth-methodCLIENT-CERT</auth-method
<realmcertificate</realm
</login-config
<transport-guaranteeCONFIDENTIAL</transport-guarantee
</webservice-endpoint
</ejb
We examined the contents of the build directory on a machine that deploys
the module and a machine that cannot deploy the module and the contents in
both directories were identical. Also, during the course of debugging, we
created a second EJB named AdapterDocQueryEJB2, which serviced the same
wsdl. Attempting to deploy that EJB resulted in this error message:
Deploying application in domain failed; Error loading deployment descriptors
for module [AdapterDocQueryEJB2] -- Referencing error: This bundle has no
bean of name [AdapterDocQuerySecured]
The WSDL is SAML enabled, which may be contributing to the behavior.
Any help or insight would be greatly appreciated.
Thanks,
Kieran
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
For additional commands, e-mail: users-help_at_glassfish.dev.java.net