Feature Requests item #511671, was opened at 2002-02-01 13:34
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=402707&aid=511671&group_id=31602

Category: ejbdoclet
Group: None
Status: Open
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: Support deployments to n jndi-names

Initial Comment:
I'd really like the ability to deploy the same 
bean multiple times in the SAME deployment 
descriptor, with different configurations. 
For example, I'd like to be able to deploy an 
Entity bean as both a Read-Only bean in WLS, and as a 
Read-Write bean that invalidates the Read-Only 
cached value for the Read-Only 
deployment.

It's not possible 
currently.

The question is how? What's the 
easy way? The key here is the ejb:bean jndi-name 
parameter. I think a good solution could be 
letting user define multiple ejb:bean tags, 
loop over all those ejb:bean, create a separate 
entry for each on, and so on. There should be a 
dittoing facility too, for 
example:

@ejb:bean name="foo" jndi-
name="a" type="CMP" ...
@ejb:bean jndi-
name="b"
 
b will use all attributes from a but 
will use b as jndi-name and bind to it. There should 
also be a mechanism to bind settings from other 
tags to a particular jndi-name, say 
@appserver:readonly jndi-name="b" for a 
readonly method, but only for jndi-name 
b.

Ara.

----------------------------------------------------------------------

>Comment By: Vincent Harcq (vharcq)
Date: 2002-04-09 01:14

Message:
Logged In: YES 
user_id=125677

Cool :)
But I would prefer having a 3rd and a 4th business 
interface in the ejb spec for read only calls.
Read only will be part of ejb 2.1 no ?

----------------------------------------------------------------------

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=402707&aid=511671&group_id=31602

_______________________________________________
Xdoclet-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-devel

Sponsored by http://www.ThinkGeek.com/

Reply via email to