Why Jboss don't accepts jndi properties being passed though initial contexts
(as all other containers?).
At least this was the behaviour in the 2.4.4 version (for which I bought the
manual).
___
Have big pipes? SourceForge.net is
AFAIK all jboss versions do accept properties in new InitialContext calls,
however this is rarely the best way to specify what you are connecting to.
If you supply a jndi.properties file in an appropriate place you can change
what you are connecting to without changing your source code. (for
Benoit Xhenseval wrote:
The Java Timer and TimerTask classes already handle all of this.
One solution is to start Timer/TimerTask threads from a permanently
loaded servlet.
These servlets can then act as EJB clients to perform periodic
activities.
This solution is portable to other
hi everyone
Do anybody have any document mentioning all the steps to migrate one
application from weblogic to Jboss, please send me, it would be helpful for
me.
Thanks a lot in advance
Mahesh
___
Have big pipes? SourceForge.net is
To answer my own question, I can redeploy my application and the
messages are persisted ok. Cool.
On the other hand if I turn jboss off, and start it the messages are not
there.
If I change the Delivery Mode to PERSISTANT for my QueueSender, then
messages to persist accross a jboss
In page 255 the first paragraph says : Support for presenting the login
information via JNDI InitialContext properties is not provided.
other question i've done that nobody answered :
Is there some explanation or example in somewhere making use of JAAS between
Remote Tomcat and JBoss???
Hi all,
I have had no luck figuring out how to change the log4j.xml file so that I
don't get DEBUG messages in the server.log anymore (or on the console for
that matter). Based on looking at the file, I shouldn't be getting DEBUG. I
am using the standard file from the sourceforge
We don't support passing login information via the InitialContex simply
because it is not as flexible as using JAAS. If that is what you want
to do it is a simple matter to write an InitialContextFactory wrapper
that delegates the authentication to JAAS and then invokes the JBossNS
Having just taken on this task, I can say with certainty that you may
have no problems or plenty :). Most of our issues revolved around
understanding custom configuration differences for EJBs between the
servers. Jboss.xml, cmp configuration, and JMS configuration isn't hard
under Jboss, but it
Greetings.
JDK 1.4.0
Linux 2.4.10
jboss-all
CVS Branch 3_0 Head.
Not building
-Steve
___
Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: [EMAIL
About fifty lines from the bottom of the log4j.xml file is a bit that
looks like this:
!-- Limit JBoss categories to INFO
category name=org.jboss
priority value=INFO/
/category
--
uncomment it, and it should keep out anything under the 'INFO' level
(most of it, anyway).
11 matches
Mail list logo