Hi,
There is a bit of confusion in my mind concerning jboss-auto.jcml.
I received JNDI Name already exists exception because at one time my
jboss.jcml was wrong.
My fault OK.
Then I deleted jboss-auto.jcml and it the server starts OK.
So my question is Is jboss-auto.jcml really needed ?
- If no
User: starksm
Date: 01/03/23 01:58:54
Modified:src/bin run.bat run.sh
Log:
Update to use the JAXP1.1 xml parser properties for choosing the
xml parser implementation. Set the default choice to the crimson
parser that ships with the jaxp1.1 ri.
Revision ChangesPath
Just to reinforce Filip's point about Oracle doing a lot of caching already
in the server, it's not clear how much benefit there is to the Java client
side stuff.
That being said, it looks like you have to turn on the caching by calling
some Oracle specific methods, it's not on by default.
When a bean doesn't pass the verifier it is "undeployed" and in our case the
LRU cache barf an NPE.
It doesn't look very good and probably has to do with some "non-initialized"
field that is supposed to do some work.
We can predictably say that people will screw their deployment and the error
User: kunle
Date: 01/03/23 18:42:25
Modified:business faq.html
Log:
A few minor changes
Revision ChangesPath
1.7 +37 -14newsite/business/faq.html
Index: faq.html
===
RCS file:
Hi folks. I'm back :) I had to deal with getting
relocated in Atlanta. I'm with CNN now. A few people
had brought to my attention that they were unable to
run with the latest JBoss documentation and thanks to
Arun the problem has been found and we need to
urgently correct the getting started
User: starksm
Date: 01/03/23 22:32:08
Modified:src/build build.bat build.sh build.xml
Log:
Complete the migration of JBossMQ to JAXP1.1
Revision ChangesPath
1.2 +1 -2 jbossmq/src/build/build.bat
Index: build.bat
User: starksm
Date: 01/03/23 22:32:08
Added: src/lib crimson.jar jaxp.jar
Removed: src/lib xml.jar
Log:
Complete the migration of JBossMQ to JAXP1.1
Revision ChangesPath
1.1 jbossmq/src/lib/crimson.jar
Binary file
1.1
A while back there was a thread on the 'debug' variable within JAWS. I
was quite vocal in saying that it should not be static final and that it
should be mutable at run time. I've made this configurable through jaws.xml.
This still defaults to false, but can be turned on for an ejb-jar by
