[JBoss jBPM] - Re: Changes don't commit on the database
by iantimothy
Hello.
I'm guessing that somewhere in your code, you should be having these lines:
JbpmConfiguration jbpmConfiguration = JbpmConfiguration.getInstance();
JbpmContext jbpmContext = jbpmConfiguration.createJbpmContext();
// Your code below these lines...
I think what you could try doing is put the above two lines inside a try block, catch any exceptions and then finally close the context i.e.
try{
JbpmConfiguration jbpmConfiguration = JbpmConfiguration.getInstance();
JbpmContext jbpmContext = jbpmConfiguration.createJbpmContext();
//your code...
}
catch(Exception e){
throw e;
}
finally{
jbpmContext.close();
}
I think it is good practice to close the context each time you create a new one in a method to ensure what you are doing persists.
Sometimes the method that you are writing needs to do call other methods which require the use of a JbpmContext. Instead of creating a new JbpmContext in those other methods, you could pass the first JbpmContext created to them.
I have also just started using Jbpm, but so far this seems to work for me. If I have said anything wrong, maybe the seniors in this forum could add to it or correct it.
Hopefully, your problem will be solved soon. Take care.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4035629#4035629
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4035629
19 years
[Installation, Configuration & Deployment] - install jboss mail server
by leonz11
After installing jboss mail server M5 sucessfully on 4.0.5 AS, I got the following errors when I started the AS:
2007-04-08 16:38:36,453 DEBUG [org.jboss.deployment.scanner.URLDeploymentScanner] Failed to deploy: org.jboss.deployment.scanner.URLDeploymentScanner$DeployedURL@7f0312bd{ url=file:/C:/jboss4.0.5/server/default/deploy/mail.ear/, deployedLastModified=0 }
org.jboss.deployment.DeploymentException: - nested throwable: (java.lang.reflect.UndeclaredThrowableException)
at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:196)
......
......
Caused by: java.lang.reflect.UndeclaredThrowableException
at org.jboss.system.ServiceCreator.install(ServiceCreator.java:236)
at org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigurator.java:449)
at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:171)
... 80 more
Caused by: java.lang.NoClassDefFoundError: org/jboss/aop/JoinPoint at java.lang.Class.getDeclaredConstructors0(Native Method)
at java.lang.Class.privateGetDeclaredConstructors(Class.java:2357)
at java.lang.Class.getConstructor0(Class.java:2671)
at java.lang.Class.getConstructor(Class.java:1629)
at org.jboss.mx.server.MBeanServerImpl.instantiate(MBeanServerImpl.java:1232)
at org.jboss.mx.server.MBeanServerImpl.instantiate(MBeanServerImpl.java:286)
at org.jboss.mx.server.MBeanServerImpl.createMBean(MBeanServerImpl.java:344)
at org.jboss.system.ServiceCreator.install(ServiceCreator.java:157)
When I searched the jboss-aop.jar, there is no such class "org/jboss/aop/JoinPoint", JoinPoint class is at "org/jboss/aop/JoinPoint/JoinPoint.class". Is there a version issue for mail server? jboss-aop.jar version problem? can sb help?
Thanx,
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4035627#4035627
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4035627
19 years
[JBoss Seam] - Re: Multiple Domain Quesiton
by rjstanford
"fhh" wrote : You said:
| P.S.: When I said the "the hostname I use to reach your machine is entirely under my control" I was not talking about http referers. I was refering to the idea of the original poster to make security depend on the hostname you use to access the site.
I generally agree with what you're saying, this is a touch pendantic, but... Technically if you support multiple apps on multiple hostnames, that's exactly what you're doing. You're using the security in the appserver as opposed to rolling your own, but its otherwise exactly the same. After all, your JBoss server is serving both pages, and acting differently based entirely on the URL.
Also please note that in my (original poster's) case, in no way shape or form would I consider not securing the controlling hostname's pages. This would merely be a convenience, not-security-related feature so that when someone requested the "unknown" URL from one of the hostnames that should not know anything about it, they receive the 404 error which, if you think about it, does mean "The complete URL as you stated it does not exist," not "This server doesn't know anything about the second half of this URL on any of its hosted domains."
I would not recommend, as the previous poster mentioned, sending a 404 error to someone using the correct administrative URL who was not logged in (or not logged in as an admin). That does break consistency, doesn't follow the definition of a 404, and eliminates the opportunity to ask them to re-authenticate themselves. In my case, no-one will ever be able to access the page through the stated URL, so I'll stand by my 404 delivery.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4035624#4035624
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4035624
19 years