I used your new wrapper with the 3.0 Release Candidate 1 and it seems to work (at
least I don't get the exception any more).
I did the following to get this fix to work with JBoss-3.0_Jetty_RC1:
1. Deployed your new jboss-local-jdbc.rar
2. Removed the old jboss.jdbc.rar
3. Modified my
Thanks for the feedback. I expect to be adding it to 3.0 shortly -- my
experience is also that it has less problems.
Thanks
david jencks
On 2002.04.24 18:47:41 -0400 Justin Almquist wrote:
I used your new wrapper with the 3.0 Release Candidate 1 and it seems to
work (at least I don't get the
I wrote a new local jca-jdbc wrapper fixing this and other problems and checked it
into 3.1 alpha (this is cvs head, checkout with no branch tags). It ends up getting
built as jboss-local-jdbc.rar. Due to jdbc changes in jdk1.4, it gets built
differently for different jdk's (makes me want
Thanks for your help.
I'm looking forward to the patch.
* * *
View thread online: http://jboss.org/forums/thread.jsp?forum=66thread=12641
___
Jboss-development mailing list
[EMAIL PROTECTED]
Does method boundary mean bean method boundary or any
method boundary (helper classes used within a beans method) ?
* * *
View thread online: http://jboss.org/forums/thread.jsp?forum=66thread=12641
___
Jboss-development mailing list
[EMAIL PROTECTED]
I have the same problem with oracle and the SEROPTO Type 4
JDBC driver.
The code i use runs on the alpha and on the beta release
of JBoss, but it doesn't run on the RC1.
I open and close one connection within the boundary of one Bean method, but also use
this connection in different
helper
I am using the CVS as of this morning. When I try to create a new entity
I get the following backtrace. I am using the postgresql-service with
the SecurityDomainJndiName atrribute commented out. I am also seeing
weird messages to the STDOUT before
18:59:05,143 INFO [STDOUT] !getCompany_id
