Re: [jboss-user] [jBPM] - How to configure 4.3 the right way?
by Marcel de Koster
Marcel de Koster [http://community.jboss.org/people/marcel.de.koster] replied to the discussion
"How to configure 4.3 the right way?"
To view the discussion, visit: http://community.jboss.org/message/536832#536832
--------------------------------------------------------------
Hi Christian,
I will post the class file. I'm currently using 4.2. And upgrading from 4.1 to 4.2 gave us some painfull issues, so we are waiting to upgrade to 4.3 till we are live. I used the original jar file but with this class file (with package of course) in my own jar. For me it gets picked up before the jbpm one. So no recompiling of whole jbpm-pvm.jar was required.
I don't have any info on jbpm 3 and it's performance. I am only amazed at the fact that jbpm 4 isn't as far as we expected it to be. Timer and Spring parts are still in incubation, while we are using it. We wanted to use the newest version of jbpm, since we expected it to be mature enough once we went live. I am a bit disappointed. Mainly because jbpm 4 has been here for a while now. And the version number isn't giving away it's real status. But that is just my opinion.
Regards,
Marcel
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/536832#536832]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
16 years
[JBoss AOP] - Aspect problem when deployed in 2 war files with PER_VM scope.
by sri varsh
sri varsh [http://community.jboss.org/people/rsrivarsh] created the discussion
"Aspect problem when deployed in 2 war files with PER_VM scope."
To view the discussion, visit: http://community.jboss.org/message/536830#536830
--------------------------------------------------------------
Hi,
I am using jboss aop for creating trace aspects for logging method entry and exit..
We have 2 war files deployed in the same jboss server.
Both the war files have their own TraceAspect class (in fact it is a single TraceAspect class which is copied into both war files).
We use loadtime weaving and the jboss-aop.xml for TraceAspect has scope as PER_VM.
Scenario
--------
When we give the first request on war1 endpoint the aop trace works fine.
and when we give request on war2 endpoint we get the following.
java.lang.IllegalArgumentException: Can not set TraceAspect field org.jboss.aop.advice.TraceAspect211.aspectField to TraceAspect
at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:146)
at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:150)
at sun.reflect.UnsafeObjectFieldAccessorImpl.set(UnsafeObjectFieldAccessorImpl.java:63)
at java.lang.reflect.Field.set(Field.java:657)
at org.jboss.aop.advice.PerVmAdvice.generateInterceptor(PerVmAdvice.java:134)
at org.jboss.aop.advice.PerVmAdvice.generateOptimized(PerVmAdvice.java:56)
at org.jboss.aop.advice.AdviceFactory.create(AdviceFactory.java:68)
at org.jboss.aop.Advisor.createInterceptorChain(Advisor.java:618)
at org.jboss.aop.Advisor.pointcutResolved(Advisor.java:888)
at org.jboss.aop.Advisor.resolveMethodPointcut(Advisor.java:650)
at org.jboss.aop.ClassAdvisor.createInterceptorChains(ClassAdvisor.java:607)
at org.jboss.aop.ClassAdvisor.access$300(ClassAdvisor.java:82)
at org.jboss.aop.ClassAdvisor$1.run(ClassAdvisor.java:299)
at java.security.AccessController.doPrivileged(Native Method)
at org.jboss.aop.ClassAdvisor.attachClass(ClassAdvisor.java:271)
When we give the first request on war2 endpoint the aop trace works fine.
and when we give request on war1 endpoint we get similar error as metioned above.
We tried changing the scope of the aspect to PER_CLASS still we get the same error
(And the PerClassAdvice calls PerVmAdvice in the stacktrace).
Jboss as - 4.2.3 GA
jboss-aop-1.5.6.GA ( which is included in the 4.2.3 server)
Kindly requesting any help on this issue.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/536830#536830]
Start a new discussion in JBoss AOP at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
16 years
[Javassist] - Create a proxy of proxy
by Bozhidar Bozhanov
Bozhidar Bozhanov [http://community.jboss.org/people/Glammy] created the discussion
"Create a proxy of proxy"
To view the discussion, visit: http://community.jboss.org/message/536818#536818
--------------------------------------------------------------
I'm using the following code to create a proxy:
public Object createProxiedInstance(Object originalInstance) throws Exception {
Class<?> originalClass = instance.getClass();
ProxyFactory factory = new ProxyFactory();
factory.setSuperclass(originalClass);
factory.setHandler(new MethodHandler() {..});
Class<T> proxyClass = factory.createClass();
return proxyClass.newInstance();
}
It works fine if a pass a normal object. However, if I pass an object that is already a proxy (created by the same method, but with a different method handler), I get:
javassist.bytecode.DuplicateMemberException: duplicate method: setHandler in com.mypackage.Bean_$$_javassist_0_$$_javassist_1
I could work this around by combining the method handler of the original proy and the one of the new proxy, but is there a way to make proxies of proxies, as if the proxies were normal objects?
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/536818#536818]
Start a new discussion in Javassist at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
16 years
Re: [jboss-user] [jBPM] - Some Questions about jbpm
by Sameeh Harfoush
Sameeh Harfoush [http://community.jboss.org/people/sameeh.harfoush] replied to the discussion
"Some Questions about jbpm"
To view the discussion, visit: http://community.jboss.org/message/536811#536811
--------------------------------------------------------------
Hello,
Find my answers in blue below
1)Does Jbpm has a jackrabbit Connector?
2)Does Jbpm supports conditional workflow?
Yes, Jbpm has <rules-decision> tag to support conditional workflow but it is till in incubation
3)what about alerts ?
I think you manage alerts using Automatic activities (java, script, mail)
4)Single sign on with other server?
5)Managing a GUI with list of tasks?
The GUI eclipse plugin doesn’t play well with tags that are still in incubation like <group> tag
6)web affinity ?
JBPM comes with web based process editor called Signavio. But it only support BPMN1.2 not JPDL…almost useless
7)Reporting?
No internal reporting engine. Unlike Drools Flow that has BIRT based reporting engine
8)ability to assign a task to a user according to external criteria?
This is possible via task assignee, groups and swimlanes
9)Support Form?
Pretty good
10)archiving a path in a workflow?
Yes, JBPM has History-service that gibes you the possibility to query the engine for history workflow activities
Cheers*
*
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/536811#536811]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
16 years
Re: [jboss-user] [JBoss Web Services Development] - CXF jms integration
by Jim Ma
Jim Ma [http://community.jboss.org/people/jim.ma] replied to the discussion
"CXF jms integration"
To view the discussion, visit: http://community.jboss.org/message/536798#536798
--------------------------------------------------------------
> Right, we need proper integration through SPI here. The point is that we need to trigger destination (queue) creation during deployment. That is done using the API a given AS container provides; for instance on AS trunk, right now we'd probably end up creating a configuration for HornetQ to be used by HornetQ deployers (HornetQCoreConfigRealDeployer ?).
> As Richard's correctly saying, we should not use those AS API directly in JBWS CXF in order to maintain proper abstraction, so we need to enrich the JBossWS SPI (few additions in org.jboss.wsf.spi.deployment might be enough) for having those info (it's probably just the name of the destinations) available in a container independent way. That part of the SPI could be populated by CXF specific deployment aspect that parses the provided or generated jboss-cxf.xml.
> Later in the chain, we'd have another deployment aspect (coming from the container integration) that uses the new SPI info to create the JMS medatadata (HornetQ conf, for isntance) and provides the requirements for the JMS deployers to run.
IMHO, we do not need to provide the function to trigger the desination creation. We always assume that user already have this Queue/Topic deployed before webservice jms endpoint deployment or the jms deployment is deployed with jms endpoint, like how the MDB is deployed.
> All this assumes we review the current WSDeploymentAspectDeployer that forces every deployment aspect to be bound to the web deployers, given the JBossWebMetaData input/ouput. I imagine some minor changes might also be required a bit earlier in the deployer chain.
Agreed. The WSDeploymentAspectDeployer is one of the key class we need to think about how to change its behavior and handle other deployment without JBossWebMetaData input/output.
At the moment , I think parsing the jms endpoint deployment descirptor (like jbossws-endpoint.xml) and creating the service and endpoint work should be put in front of WSDeploymentAspectDeployer chain. I am analysing it more to see what else we need to change .
> Jim, I'd encourage you to create branches like a did when working on cxf/jaxrpc issue and start doing changes there. Either Richard or me can help you step by step there, till we have something working that can be merged to trunk. This way you can also start now that 3.3.0 is not released yet (this work is targeted for 4.x)
Will do.
Thanks.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/536798#536798]
Start a new discussion in JBoss Web Services Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
16 years