[JBoss Messaging] - Changing defaultDS to postgres: NoSuchMethodException
by chuckanut
I am trying to change the DefaultDS to postgres by following the wiki doc. I have copied the example files into the correct locations. I am using Jboss4.0.3SP1 and Postgres 8.0.3.
When I start up JBoss, I can see that the DefaultDS gets created because the tables hilosequences and timers are created. Also, It shows up in the jmx-console as started and bound to DefaultDS. The problem is with the JDBCPersistence manager. I get the following error. Any ideas?
| 17:18:27,641 ERROR [MainDeployer] Could not create deployment: file:/C:/sift-root/eclipse-workspace/sift2/jbos
| s/jboss-4.0.3SP1/server/messaging/deploy/jboss-messaging.sar/postgresql-persistence-service.xml
| org.jboss.deployment.DeploymentException: org.jboss.messaging.core.plugin.JDBCPersistenceManager.<init>(); - n
| ested throwable: (java.lang.NoSuchMethodException: org.jboss.messaging.core.plugin.JDBCPersistenceManager.<ini
| t>())
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3979761#3979761
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3979761
19 years, 8 months
[JBoss Seam] - Handling of exception from @RolesAllowed failure
by texan
Configuration: JBoss 4.0.4GA, Seam 1.0.1, MyFaces 1.1.3 with Facelets. The app itself is working fine.
I added an @RolesAllowed annotation to a stateless session bean and tried clicking the button that invokes that action (using a user who doesn't have that Role).
As expected, it throws "SecurityException", which is caught by org.jboss.ejb3.security.RoleBasedAuthorizationInterceptor and wrapped with "EJBAccessException".
I created my own interceptor to try to catch this exception and return a JSF page name to tell the user that they don't have permission.
Sadly, even when I catch throwable in my interceptor, the exception seems to go straight by and ends up kicking out a "javax.faces.el.EvaluationException" from MyFaces.
Some extra information:
1. I tried single stepping in the debugger, and saw my interceptor invoked. When I executed "invocation.proceed()", it never reached my "catch" clause.
2. I tried putting my interceptor before the SeamInterceptor and also after it (last in the list), with no effect.
Let me know if I should attach some code.
The simple question I have (I'm a novice with many things, including JAAS configuration) is, how do I configure the desitation page for this type of permission problem, or how do I catch the exception before it reaches JSF?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3979756#3979756
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3979756
19 years, 8 months