Oh,
So I can do
openejb.jndiname.format=ejb/projectName/{interfaceType.annotationName}
Is that right?
On 9/24/07, David Blevins <[EMAIL PROTECTED]> wrote:
>
> On Sep 24, 2007, at 5:24 PM, Karan Malhi wrote:
>
> >> Great, this is the exact idea. And if someone wants a variable they
> >> don't want see, we can definitely add it.
> > Just a weird thought coming to my mind. Thought that I should submit
> > it to the list and see if it goes somewhere.
> >
> >
> > What if we allow users to set system properties like:
> > jndiname.variable1=value1
> > jndiname.variable2=value2
> > . . . . . . . .
> > . . . . . . . .
> >
> > .... and then we allow them to
> >
> > openejb.jndiname.format={deploymentId}{variable1}{variable2}
> >
> > Point is, instead of them asking us to add a variable, we can give
> > them the facility where if a system property starts with "jndiname",
> > then the stuff after the period i.e. variable1 and variable2 in this
> > case can be used as variables in defining their own jndiname. Users
> > can define as many variables as they want this way they can customize
> > jndinames to some extent.
> > This thing came up in my mind because some people standardize the way
> > they give jndi names to their ejb's, but use the project names in the
> > ejb's jndi name e.g
> > ejb/projectName/beanName.
> >
> > I don't even know if this is doable, but I remember somebody said
> > something encouraging about posting half-baked ideas once, so felt
> > encouraged to post this on the list ;)
>
> Anything is doable :)
>
> You can definitely do that now, just include the project name in the
> template. But I can see it being useful if you wanted to be lazy and
> not specify a whole template.
>
>
> -David
>
>
--
Karan Singh Malhi
