[JBoss Seam] - Use of conversationId by web services
by DavidInTx
So, lets say I publish a web service that lets me do two things: log in, and view all my customers.
I first log in, and get back the conversationId in the soap response header. Then, I pass that conversationId in the soap request header in the request to list my customers, so that seam knows who I am, and I am able to request all my customers.
My concern is that the conversationId is fairly easy to guess. Even if I run soap over https, someone who gets conversationId 2 in their login response header can guess that the next conversationId would be 3, and put that in their request header, and perhaps see someone else's customers.
I'm guessing this is not an issue for the jsf interface, because I'm assuming that something checks to see the the conversationId is associated with the web server session of the user. But, that check can't be present in the web service, since there is no web server session passed in via soap. If this is a valid issue, is the fix simply having seam generate non guessable conversationIds?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4068400#4068400
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4068400
18Â years, 9Â months
[JBoss jBPM] - Re: JBPM 3.2.1 web app?does not display deployed process
by jdickins
Hi,
Thank you for the suggestion, I will try it. However, before when I've tried saving my process archive locally (pressing the button marked "save process archive locally") and when I deployed that from the web app I got the same error message as when I deployed just the process definition. Is that method what you meant?
anonymous wrote : I'm going to work through this documentation:
| http://www.jboss.com/products/jbpm/docs/deployment
| To see if the other deployment options work.
The document I found yesterday, while being interesting, did not seem to help my problem as it is not deployment in different environments that I am having a problem with but deployment in any environment.
I think the first replier was on the right track: I may have a mismatch between my Runtime and my jbpm suite although I thought I'd fixed that problem.
Looking at the basic documentation again,
http://docs.jboss.com/jbpm/v3/userguide/gettingstarted.html#downloadables...
I have the feeling in my initial set up I may have inaccurately set up the relationships between Eclipse and the Runtime and the jbpm suite. I am going to un-install and re-install on Monday and see what comes of it.
On a side note, when I am deploying, I have set my "Server Deployer" to "/jbpm-console" rather than"/jbpm-console/upload" because 1) that way it matches the url I use to view the web app and 2) when I deployed to "/jbpm-console/upload" I received an error which I thought indicated that it could not find "http://localhost:8080/jbpm-console/upload". This lead me to try to get the information I inputed into the deployment fields the match the url I was going to (duh). When I tried deploying to "/jbpm-console" I recvied no error. And my process definition did not display. I can post the error message I received when I deployed to the /upload Server Deployer if it is relevant.
I am a little nervous about this change because it goes against what the jbpmGettingStarted guide says, but it does cause my process to say that it deployed successfully.
Thank you to everyone who has commented on my question. Any thoughts on this or any other aspect of this problem would be appreciated.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4068399#4068399
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4068399
18Â years, 9Â months
[JBoss AOP] - Re: PER_INSTANCE and constructor executions, method calls, e
by flavia.rainoneï¼ jboss.com
Hello, Paul
Actually, this behaviour is not a bug. Let me explain you why.
Put simply, a constructor doesn't occur inside an instance, it creates an instance. So, before the constructor execution, we don't have an instance available. And that's why we can't associate this execution to a PerInstanceAspect: we need to choose the per instance aspect equivalent to the instance that will be intercepted.
Regarding per instance interception on call joinpoints, the per instance aspect is currently being associated with the caller, and not the called. Given that the calls are being performed from inside a static method, the per instance interception doesn't take place.
To intercept constructor executions, I advise you to use a PerVM or a PerClass aspect.
I hope this helps.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4068398#4068398
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4068398
18Â years, 9Â months
[Management, JMX/JBoss] - Issue with MBean method calls with var args
by anshunarang
I get an exception ( see below ) When I try to invoke ( remote calls ) following methods of MBean .
public List getUniqueRateCurrencyPairs(String... query);
Is there any issue with calling of MBean methods with variable args . I am able to call the methods without var args without any issue .
I am using jboss 4.0.2 .
Thanks for the help .
Exception in thread "Timer-1" java.lang.reflect.UndeclaredThrowableException
at $Proxy1.getUniqueRateCurrencyPairs(Unknown Source)
at com.integral.monitor.task.RateTaskC.run(RateTaskC.java:26)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
Caused by: javax.management.ReflectionException
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:216)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.jmx.connector.invoker.InvokerAdaptorService.invoke(InvokerAdaptorService.java:251)
at sun.reflect.GeneratedMethodAccessor100.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:121)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:127)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
at org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:164)
at sun.reflect.GeneratedMethodAccessor99.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
at org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:805)
at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:406)
at sun.reflect.GeneratedMethodAccessor98.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
at sun.rmi.transport.Transport$1.run(Transport.java:153)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.IllegalArgumentException: Unable to find operation getUniqueRateCurrencyPairs([Ljava.lang.String;)
... 39 more
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4068396#4068396
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4068396
18Â years, 9Â months
[JBoss jBPM] - JBPM3.2.1 build error
by meet_nagi
We are new to JBPM and we are evaluating it for usage in our projects.
But while building the JBPM 3.2.1 we are getting some build errors.
ant build.jpdl is the target we are using and below is the portion of error log.
Please help us in this regard.
Thanks
Error mesage
[java] preAssemble:
[java] [echo] doing preAssemble
[java] allElements:
[java] init:
[java] assembleElement:
[java] main:
[java] assemble.org.jbpm.gd.jpdl.feature:
[java] main:
[java] properties:
[java] init:
[java] gather.bin.parts:
[java] init:
[java] gather.bin.parts:
[java] children:
[java] rootFiles*_*_*:
[java] BUILD FAILED
[java] C:\jbpm.3\designer\jpdl\org.jbpm.gd.jpdl.build\mainTargets.xml:25: The following error occurred while executing this line:
[java] C:\jbpm.3\designer\jpdl\org.jbpm.gd.jpdl.build\mainTargets.xml:90: The following error occurred while executing this line:
[java] C:\jbpm.3\designer\jpdl\org.jbpm.gd.jpdl.build\customTargets.xml:8: The following error occurred while executing this line:
[java] C:\jbpm.3\designer\jpdl\org.jbpm.gd.jpdl.build\genericTargets.xml:133: The following error occurred while executing this line:
[java] C:\jbpm.3\designer\jpdl\org.jbpm.gd.jpdl.build\target\workspace\assemble.org.jbpm.gd.jpdl.feature.all.xml:4: The following error occurred while executing this line:
[java] C:\jbpm.3\designer\jpdl\org.jbpm.gd.jpdl.build\customTargets.xml:22: The following error occurred while executing this line:
[java] C:\jbpm.3\designer\jpdl\org.jbpm.gd.jpdl.build\target\workspace\assemble.org.jbpm.gd.jpdl.feature.xml:53: Execute failed: java.io.IOException: CreateProcess: zip -r -q C:\jbpm.3\designer\jpdl\org.jbpm.gd.jpdl.build\target\workspace/N.3.0.13.1/org.jbpm.gd.jpdl.feature-3.0.13.1.zip eclipse/plugins/org.jbpm.gd.jpdl_3.1.0.alpha4 error=2
[java] Total time: 12 seconds
[java] Java Result: 13
ntcall] Exiting C:\jbpm.3\designer\jpdl\org.jbpm.gd.jpdl.build\build.xml.
ect base dir set to: C:\jbpm.3\designer\jpdl\org.jbpm.gd.jpdl.build
ntcall] calling target(s) [build-feature] in build file C:\jbpm.3\designer\jpdl\org.jbpm.gd.jpdl.build\build.xml
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4068393#4068393
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4068393
18Â years, 9Â months