[EJB 3.0] - Re: application-defined resources for MDBs
by ekrisjo
Am i making any sense? ill try to rephrase a bit...
This is my interpretation: most application servers uses a server specific deployment descriptor (or annotation) element that maps the logical JNDI name as used by the module (EJB,WAR) to the deployment environment JNDI name. This descriptor is defined and packaged in the module, not in the application (EAR).
Let's assume I have packaged and tested a set of modules which will be exposed as reusable modules from (for example) a maven repository. I pick appropriate modules to be assembled in applications. I have a hard time understanding how modules containing MDBs can be packaged in multiple applications (deployed in the same server) and still avoid "deployment environment jndi name" conflicts.
Servlet context can be bound using application.xml. Deployment environment JNDI names for SLSBs can be generated depending on what application it was deployed in (JBoss works this way?). I think persitence.xml can be packaged in the application and modules can use logical names to reference "application-defined" datasources? All of these approches avoid conflicts by binding the logical name when assembling the application, not when assembling the module.
But, for MDBs i have not found any similar way of "lately" bind the logical name of a queue to the deployment environment JNDI name?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3959317#3959317
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3959317
19 years, 9 months
[Security & JAAS/JBoss] - Re: Problem accessing EJB unchecked method from a servlet (w
by j2ee_junkie
Victor,
There are many options you can try.
1.) combine the "other" and "db_store" domains into one and use for webapp#1, webapp#2, and ejb. Thus if a user is not authenticated by DBSLM, the URLM will.
2.) Use a run-as role with the servlet
3.) Use EJB3.0. The ability to assign a security domain to a method of a bean is very usefull. Then you could have two accessors, one for each security domain.
4.)etc, etc, etc...
I learned a long time ago, if I hit a brick wall trying to do something in JBoss, it is usually because it was the wrong way of doing it.
enjoy, cgriffith
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3959312#3959312
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3959312
19 years, 9 months
[EJB 3.0] - EJB3 and Filter Annotation
by sellerjd
I'm wondering if EJB3 has, or will have, support for the Filter annotation as in Hibernate (@Filter).
Reason:
I'm looking for a non-hibernate specific solution to the following problem:
FooTable
-- fooName
-- fooType
-- fooActive_Y_N
I'd like every query of the FooTable to filter results and only return those records that have fooActive_Y_N == Y. I'd like this to take place throughout the system and not build the criteria with this Restriction every time, nor use QueryByExample with the property set. I'd like the DAO to know nothing about this except in cases where non-active records are requested.
I believe I can implement an interceptor to accomplish this, but was wondering if there was a way to do the same with a simple annotation in EJB3, as there is in Hibernate.
Thanks much
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3959308#3959308
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3959308
19 years, 9 months