Hi Scott,
You need to add this to make it work.
classpath archives=jbosscx.sar/
I'm not sure this is the correct solution?
Regards,
Adrian
After updating my cvs snaphost again the
hsqldb-default-service.xml
is failing to deploy due to
org.jboss.resource.ConnectionFactoryLoader
not
The other solution would be to put jbosscx.sar in lib. I think I prefer
the classpath solution, it is more explicit.
david jencks
On 2002.03.08 04:59:36 -0500 Adrian Brock wrote:
Hi Scott,
You need to add this to make it work.
classpath archives=jbosscx.sar/
I'm not sure this is
Scott Stark
Chief Technology Officer
JBoss Group, LLC
- Original Message -
From: David Jencks [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, March 08, 2002 4:50 AM
Subject: Re: [JBoss-dev] org.jboss.resource.ConnectionFactoryLoader not
found
I fixed the problem that was causing
javax.management.InstanceAlreadyExistsException
the jsr77 objects were modified to the current version of the spec last night.
JDBCDataSource was looking for its parent with the wrong tpye, j2eeType=JDBC when it
should have been j2eeType=JDBCResource
I fixed the problem by modifying the jms-service.xml classpath. Instead of lib, *, I
used ., and jbosscx.sar.
Then everything worked perfectly.
_
View thread online: http://main.jboss.org/thread.jsp?forum=66thread=10455
Hi Scott
Damn, thanx for your help.
Andy
I fixed the problem that was causing
javax.management.InstanceAlreadyExistsException
the jsr77 objects were modified to the current version of the spec last
night. JDBCDataSource was looking for its parent with the wrong tpye,
j2eeType=JDBC when it
It seems a little strange to put a deployable into lib/... even though
all of those do get deployed... Any reason why we don't split this? Do
away with the .sar?
--jason
David Jencks wrote:
The other solution would be to put jbosscx.sar in lib. I think I prefer
the classpath solution, it
.sar is in the deployment directory... which causes a mess when trying
to get NetBoot to function correctly.
Isn't there a patch to remove the lib bits from this .sar and place them
in lib/? That would be a better short-term solution.
--jason
Adrian Brock wrote:
Hi Scott,
You need to add
Can you just put the current jbosscx.sar in lib for now? I think the jca
rewrite I am working on may eliminate this problem. Don't spend any more
time than you need to on this, and try not to increase the number of files
we have to deal with.
david jencks
On 2002.03.08 19:05:51 -0500 Jason
Lib it will be.
--jason
David Jencks wrote:
Can you just put the current jbosscx.sar in lib for now? I think the jca
rewrite I am working on may eliminate this problem. Don't spend any more
time than you need to on this, and try not to increase the number of files
we have to deal with.
david
Nope... this won't work... SARDeployer only pays attention to .jar or
.zip files...
--jason
David Jencks wrote:
Can you just put the current jbosscx.sar in lib for now? I think the jca
rewrite I am working on may eliminate this problem. Don't spend any more
time than you need to on this,
No, no, no... this just won't work. I tried adding specific classpath
element after the * to just include this, but naming isn't up then so
it can't properly bind references...
I think the easiest thing would be to split up this file into 2.
--jason
Jason Dillon wrote:
Lib it will be.
On 2002.03.08 20:19:56 -0500 Jason Dillon wrote:
Nope... this won't work... SARDeployer only pays attention to .jar or
.zip files...
Well, unless you want to make SARDeployer deploy anything plausible it
finds, I guess you better split it up.
david
--jason
David Jencks wrote:
Can
Perhaps SARDeployer should bounce back to MainDeployer to deal with
this... but for now splitting them up is the simplest solution I can
think of.
--jason
David Jencks wrote:
On 2002.03.08 20:19:56 -0500 Jason Dillon wrote:
Nope... this won't work... SARDeployer only pays attention to .jar
This should be resolved now.
--jason
David Jencks wrote:
On 2002.03.08 20:19:56 -0500 Jason Dillon wrote:
Nope... this won't work... SARDeployer only pays attention to .jar or
.zip files...
Well, unless you want to make SARDeployer deploy anything plausible it
finds, I guess you better
After updating my cvs snaphost again the hsqldb-default-service.xml
is failing to deploy due to org.jboss.resource.ConnectionFactoryLoader
not being found:
23:53:58,196 INFO [MainDeployer] Starting deployment of package:
16 matches
Mail list logo
