-
1. Re: Deployment of (ordinary) JAR files
b.eckenfels Aug 9, 2011 11:03 AM (in response to b.eckenfels)Minor update, the deployed EJB-JAR does show up in the JNDI, but with no beans or ressources (which is expected):
[standalone@localhost:9999 /] /subsystem=naming:jndi-view
{
"outcome" => "success",
"result" => {
..."applications" => {
"net.eckenfels.sample.ejb3mdb.jar-0.0.1-SNAPSHOT.jar" => {
"java:app" => {"AppName" => {
"class-name" => "org.jboss.as.naming.context.ModularReference",
"value" => "net.eckenfels.sample.ejb3mdb.jar-0.0.1-SNAPSHOT"
}},
"modules" => {"net.eckenfels.sample.ejb3mdb.jar-0.0.1-SNAPSHOT" => {"java:module" => {"ModuleName" => {
"class-name" => "org.jboss.as.naming.context.ModularReference",
"value" => "net.eckenfels.sample.ejb3mdb.jar-0.0.1-SNAPSHOT"
}}}}
},
... -
2. Re: Deployment of (ordinary) JAR files
jaikiran Aug 9, 2011 11:26 AM (in response to b.eckenfels)1 of 1 people found this helpful1) AS 7.0.0.Final did not have support for MDBs
2) MDBs aren't bound in JNDI. That's why you don't see the JNDI names
Try latest AS7 nightly build which has MDB support.
-
3. Re: Deployment of (ordinary) JAR files
b.eckenfels Aug 9, 2011 12:03 PM (in response to jaikiran)jaikiran pai wrote:
1) AS 7.0.0.Final did not have support for MDBs
Yes, I know (now). However my question was more about the case when you drop a normal JAR, since I would expect the deployer to reject it on verification if it does not contain any deployable/managed ressource.
Thats why I asked, if a "normal" JAR is actually considered deployable for some reasons, because otherwise I would add a JIRA for missing warning/error about "empty deployments".
2) MDBs aren't bound in JNDI. That's why you don't see the JNDI names
Where in the management I can find more about the content (modules) of a deployed artifact. In the old JMX console all the objects have been listed. Is there a similiar view in the new tree?
Thans for your help
Bernd