The above error can be fixed by replacing the commons-logging.jar with the
commons-logging-1.0.4.jar. It seems that web module is expecting a newer
version of the jar
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3951212#3951212
Reply to the post :
http://
Getting the following exception when I deployed a message drive bean to use the
active-mq. adapter for jca-inflow. I followed the swiftmq rca instruction and
getting the following error.
Caused by: javax.naming.NameNotFoundException: DefaultJMSProvider not bound
at org.jnp.server.Namin
I am not seeing any documentation or example with the persistence unit support
in the persistence.xml file.
Is it already in the EJB3 RC3? If not, is it something expected to be in EJB
RC4?
Thanks
/selvan
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=39156
Thanks for the response.
Does this configuration work on the EJB3 RC3 release or do I build from the
source?
Thanks again
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3914621#3914621
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting
I configured to the JBoss (4.0.3SP1) LdapLoginModule to authenticate to the
active directory and it authenticates fine and but when it is retrieving the
memberOf (roles) for the authenticated user, the LdapLoginModule uses the
following (sAMAccountName=*) with the filter argument of the {userNam
I followed the instructions provided in the activeMQ web site to integrate the
JBoss and ActiveMQ. see ActiveMQ+JBoss Integration
1. Included the jboss.xml in the EJB3 with a different inflow container for the
MDB (using the instruction).
2. Anontated the MDB for the destination and destination
