Hello; thank you for your reply. Of course we aren't doing anything with
Tomcat. The chapter you mention talks about setting up a keystore for pushing
a certificate out at clients who wish to connect to your secure website; we're
having problems pulling a certificate from a secure server to wh
We're seeing some bizarre behavior in a production setting where a datasource
to an Informix database is handing us connections that produce network errors
if invoked.
Is there some way to tell JBoss to boot all connections out of the pool and
replace them with new ones? I can't make head or t
Hello; when I boot JBoss with the -Djavax.net.debug=all property, and execute
an HTTPS connection from code running under JBoss, my connection attempt fails
during the SSL handshake, and the javax.net.debug output tells me that the
truststore location is the empty string.
I would have expected
I am seeing the same behavior, even with the recommended environment settings.
In my case, I have some code running on a JBoss 4.0.3SP1 server trying to act
as a client to a JBoss 3.2.6 server. Obviously I can't just use the client
libraries supplied by JBoss 4.03SP1 for this purpose.
How woul
Thanks, Peter; I know I can get away with that. You can actually get away with
quite a bit less:
| final InitialContext ic = new InitialContext(new Hashtable() { {
this.put(Context.PROVIDER_URL, "localhost"); } });
|
...if everything has been set up for the defaults.
It looks like the ans
What's the recipe for creating a JNDI binding from a servlet? Obviously I know
the JNDI APIs. However, a new InitialContext() call does not find the local
JNDI tree. I'd like to be able to do exactly this:
final InitialContext c = new InitialContext();
| c.rebind(someName, thingToBind);
...b
Hello. I'm working with a framework that makes liberal use of singletons.
This of course is not good in a web application context.
Normally the way you eliminate singletons if you can't update the source code
is to make sure that the library that uses a singleton is loaded in its own
classloa
...and my .ear as built deploys just fine on Sun's reference application
server, which handles manifest class-path entries properly.
OK, time to figure out how to beat JBoss with a lead pipe sufficiently hard to
convince it to obey the specification
View the original post :
http://www.jbos
Yes, thank you. The specific error is:
NoClassDefFoundError: No ClassLoaders found for config.ConfigAnchor
...which is a JBoss-specific error, I have to guess.
I was wrong in the sense that a Class.forName() is not happening; there is a
specific reference to config.ConfigAnchor. So, as you say,
Let me refine my last post. I believe it is the specification's intention that
"normal" utility jars in an ear are available for inclusion in a classpath, but
should not be included in that classpath by default.
So framework.jar can be roped in to someone else's classpath by way of a
MANIFEST.
Since I'm just talking to myself here, I figure I'll do it here so others can
find this in a Google search later.
To illustrate how most (every other) environments handle classloading and
Manifest Class-Path entries, try this little experiment.
Create three jars, a.jar, b.jar and c.jar. Give a
I am using JBoss 4.0.3SP1 on Windows XP Professional.
I have an isolated ear with its own loader repository (via jboss-app.xml). Its
classloader is set to look inwards first before delegating to its parent
(java2ClassloadingCompliance=false).
Inside the ear I have a garden variety utility jar,
Now, I read the documentation and found this:
server/classpath: This element specifies one or more external JARs that should
be deployed with the MBean(s). The optional archives attribute specifies a
comma separated list of the JAR names to load, or the * wild card to signify
that all jars shou
I am not sure where to ask this question, so I'll start here. I'm using JBoss
3.2.6 on Windows.
I need to enforce a particular order in the classpath in /lib.
In my /conf/jboss-service.xml there is a entry like this:
I thought that would enforce an order, but I've since come to realize that
14 matches
Mail list logo