nd up with n rows in the table.
The strange part:
if I restart jboss and run the jsp, the table get's dropped correctly
and I'm back to one row.
Anyone seen this (or anything similar) before, or have any idea if this
is:
a. an oracle driver issue?
b. a connection pooling issue?
c. stu
] Started
Much to my frustration, only the first specified additional connector actually get's started. Is this a known limitation? a bug? Or am I doing something wrong?
Any assistance would be greatly appreciated.
--
Dan Berger [[EMAIL PROTECTED]]
"We are what we repeat
ually get's started. Is this a known limitation? a bug? Or am I doing something wrong?
Any assistance would be greatly appreciated.
--
Dan Berger [[EMAIL PROTECTED]]
"We are what we repeatedly do. Excellence, then, is not an act,
faultEntityFactory.newInstance(DefaultEntityFactory.java:54)
Now that line (54) is nothing special - it's just doing this:
tEntity = new BaseEntity();
where BaseEntity is a class in the same package as the factory.
Can anyone attempt to explain why that might be?
--
Dan Ber
On Fri, 2002-02-01 at 10:41, Dan Berger wrote:
1. I wanted to setup a res-ref in the jboss-web.xml to map the bound
location (java:/EntityFactory) to something under comp/env - the ref
gets built, but when I try to dereference it, after tickling the static
block, I get a
[ERROR,Default
On Fri, 2002-02-01 at 10:41, Dan Berger wrote:
2. I have a simple JNDI viewer in JSP - it list's a specified context,
grabs the NameClassPairs and spits them out in a table. I deployed this
jsp in the same WAR (contained in the same EAR) as the object factory -
but EntityFactory
uot;
Scott Stark
Chief Technology Officer
JBoss Group, LLC
--
Dan Berger [[EMAIL PROTECTED]]
"We are what we repeatedly do. Excellence, then, is not an act,
but a habit."
In either case, I get an exception "Factory not bound."
I've tried adding a jndi.properties file to the jar containing the class - only to discover (by code inspection) that JBoss only looks for jndi.properties files once - on startup; not on each application deployment.
Any suggestion