[JBoss Seam] - Re: Seam + jBPM + JNDI
by viniciuscarvalho
"gavin.king(a)jboss.com" wrote : You can deploy your jPDL anyhoo you like. Seam doesn't need to know anything about it (jBPM reads it from the process definitions from the database).
Thanks Gavin. Just another one (this might be more a jbpm question, but since you seem to be a kind of oracle (matrix way, not the evil company) I wonder if you might help me out).
Ok, so let's suppose I have a jar with my process and 2 seam ears application. The applications interact with the process where each one is responsible for certain tasks.
Considering that seam uses the jbpm context reading the process from the database, does it means that all 3 applications must be pointing to the same DB?
Another thing that I did not understand (sorry for the stupid mode=on) is
anonymous wrote : The most important thing to notice here is that jBPM transaction control is disabled. Seam or EJB3 should control the JTA transactions.
So I'll have 3 independent jbpm contexts on my JBoss at a same time?
All this mess is because I wanna show in a presentation the SOA stack with JBoss, and having a process defined where many applications can interact plus the jbpm console showing the exact place of the execution will cause a really, really nice impression of JBoss SOA stack within our customers
Regards
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032334#4032334
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032334
19Â years
[JBoss jBPM] - getting taskList with process variables non lazy
by holly77
I got about 1500 taskInstances in my DB applied to a single user.
I'm extracting all these TaskInstances via
jbpmCtx.getTaskList("actorId");
|
Then I'm accessing the contextVariables of the according contextInstance by
Token tk = taskInstance.getToken();
| ProcessInstance pi = tk.getProcessInstance();
| ContextInstance ci = pi.getContextInstance();
| ci.getVariable("nameOfVariable");
|
Problem is, that the ProcessInstance, ContextInstance and Variables are fetched non lazy by Hibernate. Thus for each access to a Set of variables a new query is executed. It takes ca. 50 sec to retrieve all the results i need, wich is much too long!
Currently I'm trying a workaround based upon HQL like this:
List<Object> list =
| s.createQuery("select ti, tk, pi, vi " +
| "from TaskInstance ti " +
| "join ti.token tk " +
| "join tk.processInstance pi, " +
| "VariableInstance vi " +
| "where vi.token=tk").
| list();
This is rather ugly...
Does anyone know, or can anyone think of another, better way to initialize the Variables of the according ContextInstance of a TaskInstance.?
By the way...
Shouldn't the global variables of a Token be passed through to the local variables of a TaskInstance? Currently they are not... Is this a bug?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032330#4032330
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032330
19Â years
[JBossWS] - VerifyError in jbossws1.2.0.SP1
by qiliu
Hello,
I am trying to consume a EJB3 web service in JBoss 4.0.5 and jbossws-1.2.0SP1, and got the error in symbols I couldn't recognize. I have no problem deploying this web service and have tested another Echo web service in the same setting. Please help. Thank you very much. Here is the error trace:
javax.xml.ws.WebServiceException: java.lang.VerifyError: (class: org/jboss/ws/tools/wsdl/WSDL11Reader, method: processBindingOutput signature: (Ljavax/wsdl/Definition;Lorg/jboss/ws/metadata/wsdl/WSDLBindingOperation;Lorg/jboss/ws/metadata/wsdl/WSDLInterfaceOperation;Ljavax/wsdl/BindingOperation;Ljavax/wsdl/BindiK®vm0Jø"XÃ
at javax.xml.ws.Service.create(Service.java:731)
at org.calgb.ecog.client.ECOGWS2ClientTest.testWebService(ECOGWS2ClientTest.java:52)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at junit.framework.TestCase.runTest(TestCase.java:164)
at junit.framework.TestCase.runBare(TestCase.java:130)
at junit.framework.TestResult$1.protect(TestResult.java:110)
at junit.framework.TestResult.runProtected(TestResult.java:128)
at junit.framework.TestResult.run(TestResult.java:113)
at junit.framework.TestCase.run(TestCase.java:120)
at junit.framework.TestSuite.runTest(TestSuite.java:228)
at junit.framework.TestSuite.run(TestSuite.java:223)
at org.junit.internal.runners.OldTestClassRunner.run(OldTestClassRunner.java:35)
at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:38)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196)
Caused by: java.lang.VerifyError: (class: org/jboss/ws/tools/wsdl/WSDL11Reader, method: processBindingOutput signature: (Ljavax/wsdl/Definition;Lorg/jboss/ws/metadata/wsdl/WSDLBindingOperation;Lorg/jboss/ws/metadata/wsdl/WSDLInterfaceOperation;Ljavax/wsdl/BindingOperation;Ljavax/wsdl/BindiK®vm0Jø"XÃ
at org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory.parse(WSDLDefinitionsFactory.java:131)
at org.jboss.ws.metadata.umdm.ServiceMetaData.getWsdlDefinitions(ServiceMetaData.java:313)
at org.jboss.ws.metadata.builder.jaxws.JAXWSClientMetaDataBuilder.buildMetaData(JAXWSClientMetaDataBuilder.java:78)
at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.(ServiceDelegateImpl.java:109)
at org.jboss.ws.core.jaxws.spi.ProviderImpl.createServiceDelegate(ProviderImpl.java:61)
at javax.xml.ws.Service.(Service.java:83)
at org.jboss.ws.core.jaxws.client.ServiceExt.(ServiceExt.java:60)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
at java.lang.reflect.Constructor.newInstance(Unknown Source)
at javax.xml.ws.Service.create(Service.java:726)
... 20 more
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032328#4032328
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032328
19Â years
[JBoss Seam] - Re: Seam 1.2.1 Released
by bsmithjj
"fers" wrote : Hello,
|
| I want to let you know that I have created Maven packages for Seam 1.2.1.GA.
|
| As usually you can find it on http://software.softeu.cz/seam/ .
|
| Petr Ferschmann
I've deployed this release in our Maven 2 repository as well, but that's on our intranet ;-).
Here's a sample pom.xml that anyone can use for ftp deployment of the seam artifacts to a network-accessible repository:
| <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
| xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
| <modelVersion>4.0.0</modelVersion>
|
| <groupId>org.jboss</groupId>
| <artifactId>jboss-seam</artifactId>
| <version>1.2.1</version>
|
| <packaging>jar</packaging>
|
| <build>
|
| <extensions>
| <extension>
| <groupId>org.apache.maven.wagon</groupId>
| <artifactId>wagon-ftp</artifactId>
| <version>1.0-alpha-6</version>
| </extension>
| </extensions>
|
| </build>
|
| </project>
|
put this pom in same directory as the seam jars then execute the following commands and your own repository will be updated with the jars.
| mvn deploy:deploy-file -DrepositoryId=ftp-repository -DgeneratePom=true \
| -Durl=ftp://YOUR.REPO.COM -Dpackaging=jar \
| -DgroupId=org.jboss -Dversion=1.2.1 -DartifactId=jboss-seam -Dfile=jboss-seam.jar
|
| mvn deploy:deploy-file -DrepositoryId=ftp-repository -DgeneratePom=true \
| -Durl=ftp://YOUR.REPO.COM -Dpackaging=jar \
| -DgroupId=org.jboss -Dversion=1.2.1 -DartifactId=jboss-seam-debug -Dfile=jboss-seam-debug.jar
|
| mvn deploy:deploy-file -DrepositoryId=ftp-repository -DgeneratePom=true \
| -Durl=ftp://YOUR.REPO.COM -Dpackaging=jar \
| -DgroupId=org.jboss -Dversion=1.2.1 -DartifactId=jboss-seam-pdf -Dfile=jboss-seam-pdf.jar
|
| mvn deploy:deploy-file -DrepositoryId=ftp-repository -DgeneratePom=true \
| -Durl=ftp://YOUR.REPO.COM -Dpackaging=jar \
| -DgroupId=org.jboss -Dversion=1.2.1 -DartifactId=jboss-seam-ui -Dfile=jboss-seam-ui.jar
|
| mvn deploy:deploy-file -DrepositoryId=ftp-repository -DgeneratePom=true \
| -Durl=ftp://YOUR.REPO.COM -Dpackaging=jar \
| -DgroupId=org.jboss -Dversion=1.2.1 -DartifactId=jboss-seam-mail -Dfile=jboss-seam-mail.jar
|
| mvn deploy:deploy-file -DrepositoryId=ftp-repository -DgeneratePom=true \
| -Durl=ftp://YOUR.REPO.COM -Dpackaging=jar \
| -DgroupId=org.jboss -Dversion=1.2.1 -DartifactId=jboss-seam-gen -Dfile=jboss-seam-gen.jar
|
| mvn deploy:deploy-file -DrepositoryId=ftp-repository -DgeneratePom=true \
| -Durl=ftp://YOUR.REPO.COM -Dpackaging=jar \
| -DgroupId=org.jboss -Dversion=1.2.1 -DartifactId=jboss-seam-ioc -Dfile=jboss-seam-ioc.jar
|
| mvn deploy:deploy-file -DrepositoryId=ftp-repository -DgeneratePom=true \
| -Durl=ftp://YOUR.REPO.COM -Dpackaging=jar \
| -DgroupId=org.jboss -Dversion=1.2.1 -DartifactId=jboss-seam-remoting -Dfile=jboss-seam-remoting.jar
|
Happy Maven 2'ing!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032326#4032326
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032326
19Â years