[jBPM] - Issue while manually skipping few nodes in a process instance
by Shishir Choubey
Shishir Choubey [http://community.jboss.org/people/shishir.choubey] created the discussion
"Issue while manually skipping few nodes in a process instance"
To view the discussion, visit: http://community.jboss.org/message/535978#535978
--------------------------------------------------------------
Hi All,
I am using jBPM 3.2.2 in my project & we have developed quite complex WF using it. But in one of a WF we have scenario where I am querying the jBPM schema to get the process instance & trying to skip/close/cancel few task in it, basically i just want to skip these nodes & make sure process reach to certain node, so that it can execute further normally.
In my WF there is fork, from fork one transition goes to a subprocess & another goes to a task, both meet to a join which goes to another task. In a subprocess I have three task nodes. so my objective is, in another instance of this process based on certain decision I have identify old instance of this process (that i am able to do) and then programmatically close/skip/cancel all the task in subprocess & same for another fork transition so that old process instance can reach to the task which is after the join.
To achieve this i tried lot of things till now & facing the below issues -
1. At a time taskMgmtInstance.getTaskInstances() gives only active task instance, after closing taskInstance process will create next instance of Task.
for this I tried doing below -
//Closing all the Task
while(!CollectionUtils.isEmpty(taskInstanceCol)){
completeTask(taskInstanceCol);
taskInstanceCol = getTaskInstanceCollection(processInstance);
}
But this also wont work as in few cases it will take some time to create the task Instances.
2. As it is a subprocess in one of the fork of the main process I updated the JBPM_TASKINSTANCE table manually for all open task & forcefully end the subprocess. for other side of the fork I closed the task(as i have a single task here). So ideally the process should reach to join & the task which is after the join should be created.
But it is not the case, the process still waiting in fork (checked the jBPM schema fork end is still null).
Please reply me ASAP to this post if anybody have some idea about this.
(I tried to put all of my observations here, please let me know if any thing is not clear)
Thanks in Advance,
Shishir
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/535978#535978]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
16 years
[JBoss Web Services] - Help Needed in Migrating WebServices Application Migration from Tomcat Server to Jboss-5.1.0 server
by nishwanth vuppala
nishwanth vuppala [http://community.jboss.org/people/vnishwanth] created the discussion
"Help Needed in Migrating WebServices Application Migration from Tomcat Server to Jboss-5.1.0 server"
To view the discussion, visit: http://community.jboss.org/message/535975#535975
--------------------------------------------------------------
Hi,
I have a war file(webservices application) which has succesfully deployed in tomcat and when i m migrating the application to Jboss5.1.0 getting many issues .
Environment :
*Jax-ws SI* *2.0* -b26-ea3
*Jaxb*
*Saaj*
Jars files inside my application lib folder :
*xercesImpl.jar*
*saaj-pai,saaj-impl.jar*
*jaxb-api,jaxb-impl,jaxp-api*
*jaxws-rt,jaxrpc,jaxws-api,sax,wsdl4j-1.5.1,xalan,jsr173_api,jsr181_api,jsr250.*
When i deployed the application please find the errors below and steps i took to resolve them.
*Exception sending context initialized event to listener instance of class org.jboss.web.jsf.integration.config.JBossJSFConfigureListener
java.lang.ClassCastException: com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl*
**
*Caused by: java.lang.RuntimeException: javax.xml.soap.SOAPException: Unable to create SOAP Factory: org.jboss.ws.core.soap.SOAPFactoryImpl
at com.sun.xml.xwss.SystemHandlerDelegateImpl.<clinit>(SystemHandlerDelegateImpl.java:661)
... 77 more
Caused by: javax.xml.soap.SOAPException: Unable to create SOAP Factory: org.jboss.ws.core.soap.SOAPFactoryImpl
at javax.xml.soap.SOAPFactory.newInstance(Unknown Source)
at com.sun.xml.xwss.SystemHandlerDelegateImpl.<clinit>(SystemHandlerDelegateImpl.java:657)
... 77 more*
**
**
*kept jboss-saaj.jar in lib and removed saaj-api.jar from appln*
*ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/SDS]] (main) Exception sending context initialized event to listener instance of class com.sun.xml.ws.transport.http.servlet.WSServletContextListener
java.lang.ExceptionInInitializerError*
*removed jaxp-api.jar from application*
*ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/SDS]] (main) Exception sending context initialized event to listener instance of class com.sun.xml.ws.transport.http.servlet.WSServletContextListener
java.lang.LinkageError: loader constraints violated when linking javax/xml/namespace/QName class*
*at com.sun.xml.bind.v2.model.impl.RuntimeBuiltinLeafInfoImpl.<clinit>(RuntimeBuiltinLeafInfoImpl.java:779)
at com.sun.xml.bind.v2.model.impl.RuntimeTypeInfoSetImpl.<init>(RuntimeTypeInfoSetImpl.java:25)
at com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.createTypeInfoSet(RuntimeModelBuilder.java:78)
at com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.createTypeInfoSet(RuntimeModelBuilder.java:41)*
*removed jaxrpc,jaxb-impl,xbean,xmlpublic,jsr173 jars*
*java.lang.LinkageError: loader constraints violated when linking org/xml/sax/XMLFilter class*
*removed sax.jar from application*
*java.lang.LinkageError: loader constraints violated when linking javax/xml/bind/SchemaOutputResolver class
removed jaxb-api.jar from application*
*failed to parse runtime descriptor: java.lang.TypeNotPresentException: Type javax.xml.bind.annotation.AccessType not present
at com.sun.xml.ws.transport.http.servlet.WSServletContextListener.contextInitialized(WSServletContextListener*
*placed jaxb-api.jar in libs folder*
*java.lang.annotation.AnnotationTypeMismatchException: Incorrectly typed data found for annotation element public abstract javax.xml.bind.annotation.XmlAccessType javax.xml.bind.annotation.XmlAccessorType.value() (Found data of type Ljavax/xml/bind/annotation/AccessType;.FIELD)*
*I not able to proceed further .*
*please Help..*
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/535975#535975]
Start a new discussion in JBoss Web Services at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
16 years
Re: [jboss-user] [JBoss Tools] - Initializing a Managed Bean's Property
by Denis Golovin
Denis Golovin [http://community.jboss.org/people/dgolovin] replied to the discussion
"Initializing a Managed Bean's Property"
To view the discussion, visit: http://community.jboss.org/message/535973#535973
--------------------------------------------------------------
> John Bailo wrote:
>
> I do have a default value set.
>
> I was hoping that at the time my JSF page called the bean, it would have read in the default values and be able to use them in executing the method called by JSF. But that doesn't appear to be the case.
It should depend on bean scope. For instance request scope bean will get re-initialized on each page refresh.
> John Bailo wrote:
>
> I was looking for something like a properties file that is read on instantiation. Again it seems like manged properties of the managed bean would do this -- but I am not sure at what point the bean is instantiated and what is required to get the default value read into the bean. From what I read it seemed like it should just happen automatically once I established the managed property and added a default value.
I'm just guessing but why not this approach :) I get from http://www.icefaces.org http://www.icefaces.org
"The simplest way is to use Chaining in the faces config and call your init method. You'll have to add an empty Object of String parameter to your a setInit method.
...
<managed-property>
<property-name>init</property-name>
<value>java.lang.Object</value>
</managed-property>
....
>From a design point of view I don't like my beans doing a whole lot of initialization work I usually make a naming distinction and move all initialization code into controller. The controller can initialized the bean directly by a callback.
...
<managed-property>
<property-name>init</property-name>
<value>#{myController}</value>
</managed-property>
....
where
pubic void setInit(MyController controller){
controller.init(this);
}
"
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/535973#535973]
Start a new discussion in JBoss Tools at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
16 years
[Beginner's Corner] - java.lang.RuntimeException: drools-compiler.jar module listed in appl ication.xml does not exist within .ear
by ilango gurusamy
ilango gurusamy [http://community.jboss.org/people/ilangocal] created the discussion
"java.lang.RuntimeException: drools-compiler.jar module listed in appl ication.xml does not exist within .ear"
To view the discussion, visit: http://community.jboss.org/message/535957#535957
--------------------------------------------------------------
I have jBoss 6 installed on a Windows XP box.
I have packaged and deployed my own EAR file into the JBoss/server/default/deploy directory.
I copied the drools-compiler jar into default/lib. Is there anything I am missing here?
Why am I likely getting these errors. Thanks in advance
*17:45:26,087 ERROR [ProfileDeployAction] Failed to add deployment: referralManag*
*er.ear: org.jboss.deployers.spi.DeploymentException: Exception determining struc*
*ture: AbstractVFSDeployment(referralManager.ear)*
* at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentExcept*
*ion(DeploymentException.java:49)*
* at org.jboss.deployers.structure.spi.helpers.AbstractStructuralDeployers*
*.determineStructure(AbstractStructuralDeployers.java:85)*
* at org.jboss.deployers.plugins.main.MainDeployerImpl.determineStructure(*
*MainDeployerImpl.java:986)*
* at org.jboss.deployers.plugins.main.MainDeployerImpl.determineDeployment*
*Context(MainDeployerImpl.java:415)*
* at org.jboss.deployers.plugins.main.MainDeployerImpl.addDeployment(MainD*
*eployerImpl.java:365)*
* at org.jboss.deployers.plugins.main.MainDeployerImpl.addDeployment(MainD*
*eployerImpl.java:275)*
* at org.jboss.system.server.profileservice.repository.MainDeployerAdapter*
*.addDeployment(MainDeployerAdapter.java:86)*
* at org.jboss.system.server.profileservice.repository.ProfileDeployAction*
*.install(ProfileDeployAction.java:61)*
* at org.jboss.system.server.profileservice.repository.AbstractProfileActi*
*on.install(AbstractProfileAction.java:53)*
* at org.jboss.system.server.profileservice.repository.AbstractProfileServ*
*ice.install(AbstractProfileService.java:403)*
* at org.jboss.dependency.plugins.AbstractControllerContext.install(Abstra*
*ctControllerContext.java:378)*
* at org.jboss.dependency.plugins.AbstractController.install(AbstractContr*
*oller.java:2029)*
* at org.jboss.dependency.plugins.AbstractController.incrementState(Abstra*
*ctController.java:1050)*
* at org.jboss.dependency.plugins.AbstractController.executeOrIncrementSta*
*teDirectly(AbstractController.java:1289)*
* at org.jboss.dependency.plugins.AbstractController.resolveContexts(Abstr*
*actController.java:1213)*
* at org.jboss.dependency.plugins.AbstractController.resolveContexts(Abstr*
*actController.java:1107)*
* at org.jboss.dependency.plugins.AbstractController.install(AbstractContr*
*oller.java:873)*
* at org.jboss.dependency.plugins.AbstractController.install(AbstractContr*
*oller.java:620)*
* at org.jboss.system.server.profileservice.repository.AbstractProfileServ*
*ice.registerProfile(AbstractProfileService.java:308)*
* at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(*
*ProfileServiceBootstrap.java:259)*
* at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(*
*ProfileServiceBootstrap.java:100)*
* at org.jboss.bootstrap.impl.base.server.AbstractServer.startBootstraps(A*
*bstractServer.java:860)*
* at org.jboss.bootstrap.impl.base.server.AbstractServer$StartServerTask.r*
*un(AbstractServer.java:441)*
* at java.lang.Thread.run(Thread.java:619)*
*Caused by: java.lang.RuntimeException: Error determining structure: referralMana*
*ger.ear*
* at org.jboss.deployment.EARStructure.determineStructure(EARStructure.jav*
*a:307)*
* at org.jboss.deployers.vfs.plugins.structure.StructureDeployerWrapper.de*
*termineStructure(StructureDeployerWrapper.java:73)*
* at org.jboss.deployers.vfs.plugins.structure.VFSStructuralDeployersImpl.*
*doDetermineStructure(VFSStructuralDeployersImpl.java:197)*
* at org.jboss.deployers.vfs.plugins.structure.VFSStructuralDeployersImpl.*
*determineStructure(VFSStructuralDeployersImpl.java:222)*
* at org.jboss.deployers.structure.spi.helpers.AbstractStructuralDeployers*
*.determineStructure(AbstractStructuralDeployers.java:77)*
* ... 22 more*
*Caused by: java.lang.RuntimeException: drools-compiler.jar module listed in appl*
*ication.xml does not exist within .ear vfszip:/C:/jboss6/server/default/deploy/r*
*eferralManager.ear/*
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/535957#535957]
Start a new discussion in Beginner's Corner at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
16 years