July 2008 - jboss-user - Jboss List Archives

[JBoss jBPM] - Re: Deploy the jBPM 3.2.3 JBoss 4.2 / 4.3

by marcusk

Right. I'm not sure you're getting my point. Let me try again. Apparently the latest stable version of jBPM (3.2.3) does not work "out-of-the-box" with the latest version of JBoss AS (4.2.2), which was released 8 months earlier (2008-06-16 and 2007-10-22 respectively, according to the download pages. JBoss 4.2.0 is even older, so that only makes things worse). This is contrary to what the readme file in jBPM (which does not refer to a specific version) suggests. Would it not be very easy to modify this document to include some mention of the problem and how to solve it? Certainly that would be a worthy investment considering the effort it would save for new/prospective users? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4165322#4165322 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4165322

17 years, 9 months

1
0
0 / 0

[JBoss jBPM] - BPEL Correlation & Eventhandling

by naera

For my bachelor thesis I am working on the implementation of a specific BPEL Process and I am stuck since days with an CorrelationViolation. I optain an CorrelationViolation when I invoke the openServiceCall operation. If I delete the whole Eventhandler part, the invoking of the openServiceCall isn't a problem at all, and the correlation worked with before with several recieve/return paires instead of event handler, but this won't serve the purpose. Any kind of help would highly be appreciated. Thanks Environment: AS: jboss-4.2.2.GA BPEL Engine: jbpm-bpel-1.1.GA OS: Windows XP Pro SP2 optained error 15:00:39,640 ERROR [StartListener] request delivery failed due to non-recoverable exception, giving up | org.jbpm.bpel.graph.exe.BpelFaultException: org.jbpm.bpel.graph.exe.FaultInstance@1be6f3c[name={http://docs.oasis-open.org/wsbpel/2.0/process/executable}correlationViolation] | at org.jbpm.bpel.integration.exe.CorrelationSetInstance.checkInitialized(CorrelationSetInstance.java:117) | at org.jbpm.bpel.integration.exe.CorrelationSetInstance.getProperties(CorrelationSetInstance.java:92) | at org.jbpm.bpel.integration.def.Correlations.getReceptionProperties(Correlations.java:72) | 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.hibernate.proxy.pojo.javassist.JavassistLazyInitializer.invoke(JavassistLazyInitializer.java:173) | at org.jbpm.bpel.integration.def.Correlations_$$_javassist_43.getReceptionProperties(Correlations_$$_javassist_43.java) | at org.jbpm.bpel.integration.jms.RequestListener.formatSelector(RequestListener.java:106) | at org.jbpm.bpel.integration.jms.RequestListener.<init>(RequestListener.java:80) | at org.jbpm.bpel.integration.jms.JmsIntegrationService.jmsReceive(JmsIntegrationService.java:80) | at org.jbpm.bpel.integration.jms.JmsIntegrationService.receive(JmsIntegrationService.java:70) | at org.jbpm.bpel.graph.exe.ScopeInstance.enableEvents(ScopeInstance.java:221) | at org.jbpm.bpel.integration.def.ProcessInstanceStarter.visit(ProcessInstanceStarter.java:144) | at org.jbpm.bpel.integration.def.ProcessInstanceStarter.visit(ProcessInstanceStarter.java:61) | at org.jbpm.bpel.integration.def.ReceiveAction.initializeProcessInstance(ReceiveAction.java:87) | 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.hibernate.proxy.pojo.javassist.JavassistLazyInitializer.invoke(JavassistLazyInitializer.java:173) | at org.jbpm.bpel.integration.def.ReceiveAction_$$_javassist_93.initializeProcessInstance(ReceiveAction_$$_javassist_93.java) | at org.jbpm.bpel.integration.jms.StartListener.deliverRequest(StartListener.java:210) | at org.jbpm.bpel.integration.jms.StartListener.onMessage(StartListener.java:168) | at org.jboss.mq.SpyMessageConsumer.run(SpyMessageConsumer.java:682) | at java.lang.Thread.run(Thread.java:595) | createServiceCall.bpel <process | name="createServiceCall" | targetNamespace="http://coresystems.ch/bt/bpel/createServiceCall" | xmlns="http://docs.oasis-open.org/wsbpel/2.0/process/executable" | xmlns:xsd="http://www.w3.org/2001/XMLSchema" | xmlns:tns="http://coresystems.ch/bt/bpel/createServiceCall" | xmlns:nswsdl="http://coresystems.ch/bt/wsdl/createServiceCall" xmlns:sxt="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/Trace" xmlns:sxed="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/Editor" xmlns:ns0="http://www.coresystems.ch/webservices" xmlns:ns1="http://coresystems.ch/bt/xsd/createServiceCall"> | |  | <import namespace="http://coresystems.ch/bt/wsdl/createServiceCall" location="createServiceCall.wsdl" importType="http://schemas.xmlsoap.org/wsdl/"/> | |  | <partnerLinks> | <partnerLink name="ClientPartnerLink" partnerLinkType="nswsdl:ClientPartnerLink" myRole="customer"/> | </partnerLinks> | |  | <variables> | <variable name="businessPartnerID" type="xsd:string"/> | <variable name="serviceCallID" type="xsd:string"/> | <variable name="systemOrEquipIsChosen" type="xsd:boolean"/> | <variable name="openServiceCallInput" messageType="nswsdl:openServiceRequestInMessage"/> | <variable name="openServiceCallOutput" messageType="nswsdl:openServiceRequestOutMessage"/> | </variables> | |  | <correlationSets> | <correlationSet name="serviceCallCreation" properties="nswsdl:requestID"/> | </correlationSets> | <eventHandlers> | <onEvent partnerLink="ClientPartnerLink" operation="getSystems" portType="nswsdl:openServiceRequest" variable="getSystemsIn" messageType="nswsdl:getSystemsOperationRequest"> | <correlations> | <correlation set="serviceCallCreation" initiate="no"/> | </correlations> | <scope name="Scope1"> | <variables> | <variable name="getSystemsOut" messageType="nswsdl:getSystemsOperationResponse"/> | <variable name="getSystemsIn" messageType="nswsdl:getSystemsOperationRequest"/> | </variables> | <sequence name="Sequence1"> | <assign name="Assign1"> | <copy> | <from variable="serviceCallID"/> | <to>$getSystemsOut.getSystemsObject/serviceCallID</to> | </copy> | </assign> | <reply name="replyGetSystems" partnerLink="ClientPartnerLink" operation="getSystems" portType="nswsdl:openServiceRequest" variable="getSystemsOut"> | <correlations> | <correlation set="serviceCallCreation" initiate="no"/> | </correlations> | </reply> | </sequence> | </scope> | </onEvent> | </eventHandlers> | <sequence name="mainSequence"> | <receive name="openServiceCall" createInstance="yes" partnerLink="ClientPartnerLink" operation="openServiceRequest" portType="nswsdl:openServiceRequest" variable="openServiceCallInput"> | <correlations> | <correlation set="serviceCallCreation" initiate="yes"/> | </correlations> | </receive> | <assign name="assignIDs"> | <copy> | <from>$openServiceCallInput.openServiceObject/businessPartnerID</from> | <to variable="businessPartnerID"/> | </copy> | <copy> | <from>$openServiceCallInput.openServiceObject/serviceCallID</from> | <to variable="serviceCallID"/> | </copy> | <copy> | <from>$openServiceCallInput.openServiceObject/serviceCallID</from> | <to>$openServiceCallOutput.openServiceObject/serviceCallID</to> | </copy> | <copy> | <from>true()</from> | <to>$openServiceCallOutput.openServiceObject/serviceCreationSuccessfull</to> | </copy> | </assign> | <reply name="openServiceCallReturn" partnerLink="ClientPartnerLink" operation="openServiceRequest" portType="nswsdl:openServiceRequest" variable="openServiceCallOutput"> | <correlations> | <correlation set="serviceCallCreation" initiate="no"/> | </correlations> | </reply> | </sequence> | </process> | createServiceCall.wsdl <?xml version="1.0" encoding="UTF-8"?> | <definitions name="createServiceCall" targetNamespace="http://coresystems.ch/bt/wsdl/createServiceCall" | xmlns="http://schemas.xmlsoap.org/wsdl/" | xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" | xmlns:xsd="http://www.w3.org/2001/XMLSchema" | xmlns:tns="http://coresystems.ch/bt/wsdl/createServiceCall" | xmlns:plnk="http://docs.oasis-open.org/wsbpel/2.0/plnktype" | xmlns:vprop="http://docs.oasis-open.org/wsbpel/2.0/varprop" xmlns:ns0="http://coresystems.ch/bt/xsd/createServiceCall" xmlns:ns1="http://coresystems.ch/bt/xsd/createServiceCall"> | | |  | <types> | <xsd:schema targetNamespace="http://coresystems.ch/bt/wsdl/createServiceCall" xmlns:tns="http://coresystems.ch/bt/wsdl/createServiceCall" xmlns:ns2="http://www.coresystems.ch/webservices"> | <xsd:import schemaLocation="createServiceCallSchema.xsd" namespace="http://www.coresystems.ch/webservices"/> | <xsd:element name="openServiceRequestInType"> | <xsd:complexType> | <xsd:sequence> | <xsd:element name="businessPartnerID" type="xsd:string"></xsd:element> | <xsd:element name="serviceCallID" type="xsd:string"></xsd:element> | </xsd:sequence> | </xsd:complexType> | </xsd:element> | <xsd:element name="openServiceRequestOutType"> | <xsd:complexType> | <xsd:sequence> | <xsd:element name="serviceCreationSuccessfull" type="xsd:boolean"></xsd:element> | <xsd:element name="serviceCallID" type="xsd:string"></xsd:element> | </xsd:sequence> | </xsd:complexType> | </xsd:element> | <xsd:element name="getSystemsInType"> | <xsd:complexType> | <xsd:sequence> | <xsd:element name="serviceCallID" type="xsd:string"></xsd:element> | </xsd:sequence> | </xsd:complexType> | </xsd:element> | <xsd:element name="getSystemsOutType"> | <xsd:complexType> | <xsd:sequence> | <xsd:element name="serviceCallID" type="xsd:string"></xsd:element> | <xsd:element name="systemArray" type="ns2:ArrayOfBPSystemInfo"></xsd:element> | </xsd:sequence> | </xsd:complexType> | </xsd:element> | </xsd:schema> | </types> | <message name="openServiceRequestInMessage"> | <part name="openServiceObject" element="tns:openServiceRequestInType"/> | </message> | <message name="openServiceRequestOutMessage"> | <part name="openServiceObject" element="tns:openServiceRequestOutType"/> | </message> | | <message name="getSystemsOperationRequest"> | <part name="getSystemsObject" element="tns:getSystemsInType"/> | </message> | <message name="getSystemsOperationResponse"> | <part name="getSystemsObject" element="tns:getSystemsOutType"/> | </message> | <portType name="openServiceRequest"> | <operation name="openServiceRequest"> | <input name="input" message="tns:openServiceRequestInMessage"/> | <output name="output" message="tns:openServiceRequestOutMessage"/> | </operation> | <operation name="getSystems"> | <input name="input1" message="tns:getSystemsOperationRequest"/> | <output name="output1" message="tns:getSystemsOperationResponse"/> | </operation> | </portType> | |  | <plnk:partnerLinkType name="ClientPartnerLink"> | <plnk:role name="customer" portType="tns:openServiceRequest"/> | </plnk:partnerLinkType> | | <vprop:property name="requestID" type="xsd:string"/> | <vprop:propertyAlias propertyName="tns:requestID" messageType="tns:openServiceRequestOutMessage" part="openServiceObject"> | <vprop:query>/tns:openServiceRequestOutType/serviceCallID</vprop:query> | </vprop:propertyAlias> | <vprop:propertyAlias propertyName="tns:requestID" messageType="tns:getSystemsOperationRequest" part="getSystemsObject"> | <vprop:query>/tns:getSystemsInType/serviceCallID</vprop:query> | </vprop:propertyAlias> | <vprop:propertyAlias propertyName="tns:requestID" messageType="tns:getSystemsOperationResponse" part="getSystemsObject"> | <vprop:query>/tns:getSystemsOutType/serviceCallID</vprop:query> | </vprop:propertyAlias> | <vprop:propertyAlias propertyName="tns:requestID" messageType="tns:openServiceRequestInMessage" part="openServiceObject"> | <vprop:query>/tns:openServiceRequestInType/serviceCallID</vprop:query> | </vprop:propertyAlias> | </definitions> View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4165321#4165321 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4165321

17 years, 9 months

1
0
0 / 0

[EJB 3.0] - Re: Using quartz from EJB 3.0

by henk53

Anyone? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4165318#4165318 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4165318

17 years, 9 months

1
0
0 / 0

[JCA/JBoss] - Re: Controlling the quartz scheduler from EJB with the quart

by henk53

Nobody has any more ideas? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4165317#4165317 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4165317

17 years, 9 months

1
0
0 / 0

Delivery Notification <burtobb@mail.auburn.edu>

by Postmaster＠lists.jboss.org

This is a delivery status notification, automatically generated by MTA im2.duc.auburn.edu on Fri, 18 Jul 2008 07:42:08 -0500 Regarding recipient(s) : burtobb(a)mail.auburn.edu Delivery status : Failed. Message could not be delivered to domain <mail.auburn.edu> .Failed while initiating the protocol. <[('burtobb(a)mail.auburn.edu', 550, '5.1.1 <burtobb(a)mail.auburn.edu>... User unknown')]> MTA Response :550 The original message headers are included as attachment.

17 years, 9 months

1
0
0 / 0

[EJB 3.0] - Re: EJB timers ignoring start date

by pdhaigh

cheers: https://jira.jboss.org/jira/browse/JBAS-5779 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4165312#4165312 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4165312

17 years, 9 months

1
0
0 / 0

[EJB 3.0] - Re: Session bean lookup fails JBoss 5, worked in 4.0.5

by jaikiran

"lpmon" wrote : One more thing: The attempted SLSB lookup that is failing is in the @PostContruct method of the Seam class that is an @Startup class. | I don't have any experience on Seam, so i can't say whether this issue is related to Seam. "lpmon" wrote : | But, all indications are the SLSB it is trying to lookup is already loaded and should be found with the jndi name I am using. Logs please :-) Preferably the server.log contents. Also please post the jndi-tree contents (follow the steps mentioned here http://wiki.jboss.org/wiki/DisplayTheJNDITreeWithTheJMXConsole) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4165311#4165311 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4165311

17 years, 9 months

1
0
0 / 0

[JBoss jBPM] - Re: Bug in jpdl 3.2.3 using beanshell expression (not in 3.2

by jbarrez

Alex, I've tested it with jBPM3 trunk: the bug is gone :-) (there is however another bug (task list was null), but I'm sure it was because I'm on trunk). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4165310#4165310 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4165310

17 years, 9 months

1
0
0 / 0

[EJB 3.0] - Re: QuerySyntaxException class is not mapped

by jaikiran

"jaikiran" wrote : Please post the entire logs you see on the console. | | Sorry, i wasn't clear enough in my earlier post. I was actually asking for the console logs that you see from the point you start the server, till this exception is logged (even the server.log would do, but that's actually going to be too long). The logs will actually help us in figuring out whether the entity was actually mapped when you application was being deployed. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4165309#4165309 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4165309

17 years, 9 months

1
0
0 / 0

[Installation, Configuration & DEPLOYMENT] - Re: JBoss: How to create my own configuration folder than de

by jaikiran

anonymous wrote : run.bat -c myapp option I dont not wish to use as I am starting server as a windows service. | How are you starting it as a service? Are you using JBossNative to start it as a service? There are ways, to pass the -c option through the service configuration. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4165308#4165308 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4165308

17 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-user July 2008