In an earlier post to the thread "ConnectionManager on 3.2.0RC2," David
Jencks said:
"There are actually essentially no consequences. Using
the depends tag would make your ds deployment wait for
the transaction manager to get started before it gets
deployed. However you can't use it in 3.2RC2, just 3.2
cvs.
"I haven't seen the tx manager deploy after a datasource,
but it is theoretically possible. The warning is there
in 3.2 due to slightly careless backporting from head.
What you should IMNSHO actually do is use the cvs version
of jboss 3.2 and the *-ds.xml format files where this
dependency is generated for you."
Based on those statements, why would I continue to receive the warning that
I included in the post that started this thread, especially since I'm using
JBoss 3.2.0 RC3? Even before reading the above post, I didn't expect to
need to list in a *-ds.xml file a dependency on the transaction manager.
David's statements confirm this expectation.
Is anyone else experiencing this problem with RC3?
Craig
-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger
for complex code. Debugging C/C++ programs can leave you feeling lost and
disoriented. TotalView can help you find your way. Available on major UNIX
and Linux platforms. Try it free. www.etnus.com
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
