Gary, Just for the sake of completeness, can you please try to call getTransaction() on the TransactionManager instance returned, and then issue code along the lines ...
(User)Transaction tx = mgr.getTransaction(); int status = tx.getStatus(); Thanks for your help in advance Werner PS Once you have done so and your code still compiles ... ;-), can you please create a new issue at http://jira.codehaus.org/browse/CASTOR, and attach the relevant information of this thread. Once you've done so, I'll take care of the rest and commit a patch within a few days. As a result of this thread (and a couple of other pending issues, I most likely will delay the 1.0.1 release scheduled for tomorrow for a few days. PSS Just out of curiosity, what database are you using (given that you are running on Websphere ... ) ? [EMAIL PROTECTED] wrote: > Hi Werner, > > here's the test servlet and output for WAS6 Transaction Manager... > > > [08/05/06 12:55:47:724 BST] 00000043 Main I Calling > getTransactionManager() > [08/05/06 12:55:47:726 BST] 00000043 Main I TM instance set > to [EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]> > > package tx; > > import java.io.IOException; > import javax.servlet.Servlet; > import javax.servlet.ServletException; > import javax.servlet.http.HttpServlet; > import javax.servlet.http.HttpServletRequest; > import javax.servlet.http.HttpServletResponse; > > import java.util.logging.Logger; > import javax.transaction.TransactionManager; > import com.ibm.ws.Transaction.TransactionManagerFactory; > > public class Main extends HttpServlet implements Servlet { > > static Logger log = Logger.getLogger("Main"); > > /* (non-Java-doc) > * @see javax.servlet.http.HttpServlet#HttpServlet() > */ > public Main() { > super(); > } > > /* (non-Java-doc) > * @see javax.servlet.http.HttpServlet#doGet(HttpServletRequest arg0, > HttpServletResponse arg1) > */ > protected void doGet(HttpServletRequest arg0, HttpServletResponse arg1) > throws ServletException, IOException { > > log.info("Calling getTransactionManager()"); > TransactionManager mgr = > TransactionManagerFactory.getTransactionManager(); > log.info("TM instance set to "+mgr.toString()); > > } > > } > ------------------------------------------------------------------------ > *From:* Werner Guttmann [mailto:[EMAIL PROTECTED] > *Sent:* 08 May 2006 10:06 > *To:* [email protected] > *Subject:* RE: [castor-user] [XML] Problem with IBM RAD 6 & WebSphere 6 > > Well, actually, I thought you'd knock up that servlet yourself .. ;-), > trying to execute > > (WebSphere)TransactionManager mgr = > com.ibm.ws.Transaction.TransactionManagerFactory.getTransactionManager(); > > Thanks > Werner > > ------------------------------------------------------------------------ > *From:* [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > *Sent:* Montag, 08. Mai 2006 10:43 > *To:* [email protected] > *Subject:* RE: [castor-user] [XML] Problem with IBM RAD 6 & WebSphere 6 > > of course, send it over and I'll send you back the results > > Gary > > ------------------------------------------------------------------------ > *From:* Werner Guttmann [mailto:[EMAIL PROTECTED] > *Sent:* 08 May 2006 09:41 > *To:* [email protected] > *Subject:* RE: [castor-user] [XML] Problem with IBM RAD 6 & WebSphere 6 > > Gary, I have seen the new issue, thanks. Wrt to the > transaction(manager) handling stuff, would you be in a position to > deploy e.g. a small test servlet that tries to execute the code > given by you ? If you can run this code successfully, I'll provide a > new TransactionManagerFactory implementation for WSAD 6.0.x ... > > Werner > > > ------------------------------------------------------------------------ > *From:* [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > *Sent:* Montag, 08. Mai 2006 10:37 > *To:* [email protected] > *Subject:* RE: [castor-user] [XML] Problem with IBM RAD 6 & > WebSphere 6 > > Hi Werner, > > I've submitted a new issue on my problem. > As for obtaining a TransactionManager instance, in tx.jar: > > WebSphereTransactionManager mgr = > > com.ibm.ws.Transaction.TransactionManagerFactory.getTransactionManager(); > > Not tried it, but that's what's in the lib directory of WAS 6.0.2.9. > > Regards, > Gary Bennett > > > ------------------------------------------------------------------------ > *From:* Werner Guttmann [mailto:[EMAIL PROTECTED] > *Sent:* 08 May 2006 08:53 > *To:* [email protected] > *Subject:* RE: [castor-user] [XML] Problem with IBM RAD 6 & > WebSphere 6 > > Gary, > > can you please file a new issue at > http://jira.codehaus.org/browse/CASTOR, and describe in detail > your problem. In addition, we need information from you how with > Websphere 6.0.x a TransactionManager instance can be obtained > from Websphere. As always, IBM seems to be changing this area of > code at random .. ;-). > > Regards > Werner > > > ------------------------------------------------------------------------ > *From:* [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > *Sent:* Montag, 08. Mai 2006 09:33 > *To:* [email protected] > *Subject:* RE: [castor-user] [XML] Problem with IBM RAD 6 & > WebSphere 6 > > Yes, first thing I checked. > The same file works with WebSphere 6.0.0 but not with > WebSphere 6.0.1 > > > > > ------------------------------------------------------------------------ > *From:* ELVART, CHRISTOPHER (SBCSI) [mailto:[EMAIL PROTECTED] > *Sent:* 05 May 2006 17:17 > *To:* [email protected] > *Subject:* RE: [castor-user] [XML] Problem with IBM RAD 6 & > WebSphere 6 > > Every time I have struggled with "content not allowed in > prolog" errors it has always turned out that there was a > space before the opening < in the xml. > > Have you checked this? > > Thanks, > Chris Elvart > AT&T > > > ------------------------------------------------------------------------ > > > Visit our website at http://www.ubs.com > > This message contains confidential information and is intended only > for the individual named. If you are not the named addressee you > should not disseminate, distribute or copy this e-mail. Please > notify the sender immediately by e-mail if you have received this > e-mail by mistake and delete this e-mail from your system. > > E-mail transmission cannot be guaranteed to be secure or error-free > as information could be intercepted, corrupted, lost, destroyed, > arrive late or incomplete, or contain viruses. The sender therefore > does not accept liability for any errors or omissions in the contents > of this message which arise as a result of e-mail transmission. If > verification is required please request a hard-copy version. This > message is provided for informational purposes and should not be > construed as a solicitation or offer to buy or sell any securities or > related financial instruments. > > > > ------------------------------------------------------------------------ > > ------------------------------------------------- > If you wish to unsubscribe from this list, please > send an empty message to the following address: > > [EMAIL PROTECTED] > ------------------------------------------------- ------------------------------------------------- If you wish to unsubscribe from this list, please send an empty message to the following address: [EMAIL PROTECTED] -------------------------------------------------
