Thanks, I was really not sure what was needed to get this together. It
looks like the main jboss branch did not get the latest unversioned
jbosscx.jar, so I took the liberty to fix that.
Thanks for updating the documentation too.
--jason
On Thu, 21 Jun 2001, Scott M Stark wrote:
I updated
Get rid of the version number. Make sure that the CVS tags are in synch
between the jboss and jbosscx modules. Whenever you update the
jbosscx.jar in jboss, there should be a tag in both modules so that
you can always obtain the jbosscx source from which the jbosscx.jar was
created.
Do
On Wed, Jun 20, 2001 at 02:22:16PM -0700, Jason Dillon wrote:
Get rid of the version number. Make sure that the CVS tags are in synch
between the jboss and jbosscx modules. Whenever you update the
jbosscx.jar in jboss, there should be a tag in both modules so that
you can always obtain
See: http://www.jboss.org/CVSAdmin.jsp
- Original Message -
From: Jason Dillon [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, June 20, 2001 2:22 PM
Subject: Re: [JBoss-dev] Fixed very small problem with ConnectionFactoryLoader
Get rid of the version number. Make sure
Follow the steps detailed on the web site, i.e. add a tag to the
jboss module when you update the jar file. Add a tag with the same
name to the jbosscx module when you do this.
Please excuse me if I am missing something obvious, but I don't quite get
what I need to do. I looked at the tags
On Tue, Jun 19, 2001 at 07:55:05PM -0700, Jason Dillon wrote:
Hello, I ran into a problem with ConnectionFactoryLoader
PrincipalMappingProperties was not set or when it was set like this:
attribute name=PrincipalMappingProperties/attribute
This would cause the princMapProps to remain a
