Thanks for your help!
the first solution with the context lookup is working just fine!
the latter solution does not work and it throws a NullPointerException in both
use cases (for existing and non existing user).
I only tried it in portal 2.6.2.
| ex.getMessage() : null
|
anonymous wrote : I use Transaction Manager obtained with the jndi name
java:/TransactionManager
PMN: what do you mean by this?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4140091#4140091
Reply to the post :
I mean that UserTransaction is a subset of the TransactionManager and is not
suitable in all environments, I think. That maybe teh cause of teh roblem but I
am not an expert on the topic... Try to use directly the TransactionManager.
Hope this helps ...
View the original post :
PMN,
could you show how you get the TransactionManager? I tried with different jndis
(java:comp/TransactionManager, TransactionManager,
javax.transaction.TransactionManager)but to no avail. :(
Sorry for the pain I cause with my beginner's questions.
View the original post :
The AS must be running
TransactionManager tm= (TransactionManager) new
InitialContext().lookup(java:/TransactionManager);
In 2.6.4 sources there is a test portlet that get the current transaction like
this. (I never tried it)
private Transaction getCurrentTransaction()
|{
|
look like the exception is from the transaction ;
andif i'm correct, findUserByUserName return null when user not found. On my
own code i use bean instead and throw the exception by myself :
|
| MBeanServer mbeanServer = MBeanServerLocator.locateJBoss();
| UserModule userModule =
I use Transaction Manager obtained with the jndi name java:/TransactionManager
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4139950#4139950
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4139950
Could it be that because it throws an exception when the user does not exist
you never get to the ut.commit() and that's why that particular exception is
being thrown? Just a wild shot in the dark.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4139731#4139731
I know of a similar issue which has been fixed in 2.6.4.GA which is our latest
stable release. Can you see if your problem is resolved there?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4139742#4139742
Reply to the post :
