No. It's confusing for end-user to remember conditions.
Ara.
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:xdoclet-devel-
> [EMAIL PROTECTED]] On Behalf Of Dmitri Colebatch
> Sent: Thursday, September 27, 2001 1:44 AM
> To: Ara Abrahamian
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTE
weblogic:resource-denv-escription -> weblogic:resource-env-description
Ara.
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, September 27, 2001 1:28 AM
> To: Ara Abrahamian
> Cc: [EMAIL PROTECTED]
> Subject: Re: [Xdoclet-devel] CVS update:
> 'xd
Yeah true. My aim was to make it backwards compatable. I have no
problems with deprecating jndi-name. Obviously if view-type is
"local" then we'll look for local-jndi-name, but if its not there, also
check for jndi-name before failing.
but yeah - happy to deprecated jndi-name.
cheesr
dim
On
Well, if view-type is not "both", but "local" or "remote", then why not
specify only "local-jndi-name" or "remote-jndi-name"?
In my opinion, "jndi-name" should be deprecated, and we should go for
"local-jndi-name" and "remote-jndi-name" only.
This makes the jndi stuff less confusing in my opini
How about this:
local-jndi-name
remote-jndi-name
jndi-name
the logic being that if local or remote are specified they apply, but if
they are absent _and_ view-type is _not_ both local and remote, then we
just use the jndi-name attribute?
cheers
dim
ps - sorry I've been quiet recently, ta
Couldn't see you changed anything in weblogic-ejb-jar-xml.j. Did you?
- Original Message -
From: Ara Abrahamian <[EMAIL PROTECTED]>
Date: Wednesday, September 26, 2001 11:12 pm
Subject: [Xdoclet-devel] CVS
update: 'xdoclet/core/resources/xdoclet/ejb/vendor orion-cmp-mapping.j
weblogic-e
Update of /cvsroot/xdoclet/xdoclet/core/resources/xdoclet/ejb/vendor
In directory usw-pr-cvs1:/tmp/cvs-serv5940/ejb/vendor
Modified Files:
orion-cmp-mapping.j weblogic-ejb-jar-xml.j
Log Message:
fixed Bugs item #465170 : Typos in template files
__
Bugs item #465170, was opened at 2001-09-26 04:47
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=402704&aid=465170&group_id=31602
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Jo Are Rosland (joare)
Assigned to: Nobody/Anonymous
Agree.
Ara.
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:xdoclet-devel-
> [EMAIL PROTECTED]] On Behalf Of [EMAIL PROTECTED]
> Sent: Wednesday, September 26, 2001 10:23 PM
> To: [EMAIL PROTECTED]
> Subject: [Xdoclet-devel] local-jndi-name
>
> The @ejb:bean tag has a parameter n
Hello aslak,
Wednesday, September 26, 2001, 8:57:46 PM, you wrote:
ahnn> Here ya go. I am having problems with relations too, trying to fix it.
ahnn> The docs for relation are completely wrong, so hopefully my code will
ahnn> help you a bit. The @X tags are just tags that I "commented out".
a
Here ya go. I am having problems with relations too, trying to fix it.
The docs for relation are completely wrong, so hopefully my code will
help you a bit. The @X tags are just tags that I "commented out".
I'm going to take a look at your message/session stuff now.
Aslak
- Original Messa
The @ejb:bean tag has a parameter named "jndi-name". It seems to that
that both (remote) home and local home interfaces are bound to the same
name. Shouldn't there be a different jndi name for each? At least WLS
wants different jndi names for each of the two homes.
I propose adding a new param
12 matches
Mail list logo
