Not so much for deployment, but for development tools.
If the user, through some tool, deletes the servlet in the
main dd, then that tool can delete information related to
that servlet in the app-server-specific dd. Again, servlets
have names so this might not be the best example.
The id
WebLogic 6+ has supported it (though not well documented at all!).
Advantage is for GUI applications having access to the same JNDI
environment that its web application cousin has - there is a
potential to reuse alot of code between the two environments.
Shared security mechanisms and client-side
Richard,
While I've not tried what you are asking about, JBoss (and any J2EE
server) will use a database via JDBC. There are two main JDBC drivers
for MS SQL Server 2000 that I would recommend. One is the DataDirect
JDBC driver (which is resold by Microsoft) and the Sprinta2000 or
Opta2000
wouldn't need
the aspect-mbean.
Have no idea if the aspect stuff plays well with the JMX micro
kernal but that might be another direction to take this.
Brian Repko
nVISIA
Original Message Follows
From: Jason Dillon [EMAIL PROTECTED]
Subject: [JBoss-dev] AspectJ and the JBoss aspect stuff
If lastRequestId is a long, then it clearly is not.
I don't think that it is in general either...not sure
if that changes with hotspot. And while it may be
under certain VMs, I don't think that you can generalize
that.
Brian
Original Message Follows
From: Hiram Chirino [EMAIL
