Hi ;
I have a processDefinition where I modeled a general Exception handler. But, the process seems to ignore that handler :( So I tried to place the exception handler in one specific action, and... Nothing is happening. The handler is ignored
<?xml version="1.0" encoding="UTF-8"?>
|
| <process-definition name="jbpm_process">
|
| <exception-handler>
| <action class="*****.actions.ProcessExceptionHandler"/>
| </exception-handler>
|
| </process-definition>
Any suggestions?
thkx in advance
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4193128#4193128
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4193128
I'm thinking I might be able to inject an interceptor in my EJB3 interceptor chain - write my own annotation like @InterruptOnTimeout - and when the method is called, the interceptor looks for the existance of this annotation on the method and if it finds it, it grabs the transaction and adds my own checked action to it (I am assuming the interceptor has the ability to call some APIs to do this).
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4193123#4193123
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4193123
Thank you for your quick reply.
I don't have any jar file in the workspace -
I guess that the jar is created during the deplyoment to the server's "deploy" directory.
Anyway, the problem happens also after restarting (Eclipse & machine).
For some reason, EJB client project is deployed as a jar file, but the EJB project itself (beans implementation) is deployed as group of flat files... maybe this is the root of the problem?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4193120#4193120
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4193120
"gcompienne" wrote : So I have the feeling it could still highlight something strange somewhere.
|
| But anyway, the given workaround ...
Actually I don't see this as a workaround. :-)
Although this is marked as workaround in mentioned JIRA issue.
It's a normal behavior on how you load classes,
when the deployment is deleted --> undeployed.
Unless you make a temp copy of it,
I don't see how else you're still gonna access that resource.
It's probably the fact that we now do it differently
due to VFS's capability of handling resources as they are (even nested one's),
that makes this example a bit unexpected - since almost everybody else does it the old way == temp copy.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4193114#4193114
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4193114
Okay so the same fix did work in 2.7... just missed an important line along the way.
Here is the diff file from the 2.7 svn branch that should add support:
http://codingislife.com/share/jbp/guest/JBossPortalGuestRolePatch.diff
If you don't feel like recompiling I also have the portal-security-lib.jar:
http://codingislife.com/share/jbp/guest/portal-security-lib.jar
With this, the role name "Guest" should be active when a person is not logged in. Here is an example of the deployment xml from portlet-instances.xml:
| <deployment>
| <if-exists>overwrite</if-exists>
| <instance>
| <instance-id>GuestPortletInstance</instance-id>
| <portlet-ref>TestPortlet</portlet-ref>
| <security-constraint>
| <policy-permission>
| <action-name>view</action-name>
| <role-name>Guest</role-name>
| </policy-permission>
| </security-constraint>
| </instance>
| </deployment>
|
I didn't try it with page security (as in an -object.xml) but I'd imagine it should work the same.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4193108#4193108
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4193108
"YogeshGLX" wrote :
| Why I need to specify this "Combined Connection Factory" attribute?
| Well, as you can guess, I'm pretty newbie here, and so I am not to able to figure out why this is MANDATORY and why the bridge collapses before it is even made if this is not specified and that too with NPE?
|
|
All that stuff is JCA configuration, not JBoss Messaging configuration. I'd suggest asking in the JCA forum.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4193104#4193104
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4193104
Ok guys, found out on my own, a rather dumb mistake on my part:
In RemoteJMSProvider configuration, I forgot to add attribute FactoryRef, i.e.
<!-- The combined connection factory -->
| <attribute name="FactoryRef">XAConnectionFactory</attribute>
I added it and everything went smoothly!
I still have one more dumb question though, if anybody can take time to enlighten me:
Why I need to specify this "Combined Connection Factory" attribute?
Well, as you can guess, I'm pretty newbie here, and so I am not to able to figure out why this is MANDATORY and why the bridge collapses before it is even made if this is not specified and that too with NPE?
Thanks anyway!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4193101#4193101
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4193101