[JBoss Portal] - Authentication
by vsramineni
Intialy i posted this question in user forum but i didn't got the reply.
Hai,
Iam using DatabaseServerLoginModule as Login module to my application.
I configured login-config.xml and i placed users.properties,roles.properties
in conf folder of jboss.
When i login into the portal using users which are created by me , in portal header iam not getting logged in as : ,logout and other links, instead of
these iam getting login link again and this is not happening when i login as
admin (this is also there in my users list) .
This is may be due to my users are not there in portal database.
please give me some suggestions regarding this. Iam new to all these things
JBoss-portal 2.6-CR2
thanks
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4054344#4054344
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4054344
19Â years
[EJB 3.0] - Message Driven Bean with TIBCO EMS - Wrong Connection factor
by harleybl
In the past we have been using message driven beans with TIBCO EMS integrated directly into our JBoss installations. In order to facilitate this we provide an invoker-bindings tag in the jboss.xml of the ejb's jar like this
| <invoker-bindings>
| <invoker> <invoker-proxy-binding-name>tib-message-driven-bean</invoker-proxy-binding-name>
| </invoker>
| </invoker-bindings>
|
|
And have the tib-message-driven-bean invoker set up in our standardjboss.xml configuration file.
This all works well and good for EJB 2.1 style message driven beans.
On a new project we are trying to use EJB 3.0 and am having trouble using the message driven beans. When trying the following example:
| @MessageDriven(
| activationConfig = {
| @ActivationConfigProperty(propertyName = "destination",
| propertyValue = "ems/queue.sample"),
| @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue") }
| )
| public class LoggingMDB implements MessageListener
| {
| private Log mLogger = LogFactory.getLog( LoggingMDB.class );
| public void onMessage( Message message )
| {
| mLogger.info( message.toString() );
| }
| }
|
The project builds fine but on deployment I get the following exception. It appears that JBoss is looking in the wrong connection factory. How does one specify the connection factory?
2007-06-14 08:46:39,639 WARN [org.jboss.resource.adapter.jms.inflow.JmsActivation] Failure in jms activation org.jboss.resource.adapter.jms.inflow.JmsActivationSpec@c344b4(ra=org.jboss.resource.adapter.jms.JmsResourceAdapter(a)1501268 destination=ems/queue.sample isTopic=false tx=true durable=false reconnect=10 provider=java:/DefaultJMSProvider user=null maxMessages=1 minSession=1 maxSession=15 keepAlive=60000 useDLQ=true DLQHandler=org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler DLQJndiName=queue/DLQ DLQUser=null DLQMaxResent=5)
java.lang.ClassCastException: com.tibco.tibjms.naming.TibjmsFederatedQueue
at org.jboss.mq.SpyConnectionConsumer.(SpyConnectionConsumer.java:107)
at org.jboss.mq.SpyConnection.createConnectionConsumer(SpyConnection.java:128)
at org.jboss.resource.adapter.jms.inflow.JmsServerSessionPool.setupConsumer(JmsServerSessionPool.java:262)
at org.jboss.resource.adapter.jms.inflow.JmsServerSessionPool.start(JmsServerSessionPool.java:91)
at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupSessionPool(JmsActivation.java:536)
at org.jboss.resource.adapter.jms.inflow.JmsActivation.setup(JmsActivation.java:309)
at org.jboss.resource.adapter.jms.inflow.JmsActivation$SetupActivation.run(JmsActivation.java:585)
at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:204)
at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:275)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:743)
at java.lang.Thread.run(Thread.java:595)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4054343#4054343
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4054343
19Â years
[JBoss Seam] - Re: Request parameters
by KnisterPeter
Ok, I could create a simple bean component and specify @In("#{param...}").
But I get this exception for my bean:
java.lang.IllegalArgumentException: Can not set java.lang.Integer field de.llynch.kingpin.bean.ConfigBean.campaignId to java.lang.String
| sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:146)
| sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:150)
| sun.reflect.UnsafeObjectFieldAccessorImpl.set(UnsafeObjectFieldAccessorImpl.java:63)
| java.lang.reflect.Field.set(Field.java:657)
| org.jboss.seam.util.Reflections.set(Reflections.java:63)
| org.jboss.seam.Component.setFieldValue(Component.java:1555)
| org.jboss.seam.Component.access$500(Component.java:135)
| org.jboss.seam.Component$BijectedField.set(Component.java:2285)
| org.jboss.seam.Component.injectAttributes(Component.java:1368)
| org.jboss.seam.Component.inject(Component.java:1195)
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4054340#4054340
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4054340
19Â years