[jBPM Users] - Re: Deploying JBPM project created by Eclipse in Tomcat serv
by Nanaki
Ok, a couple days ago, I studied the door example.
So I have understand this simple sample (how to get a token, how to move it to differents state ...).
So now, I'd like to see this test directly on the worflow image.
For example, I have a JUnit test testing some movement of the token.
anonymous wrote : ou can also use the jbpm api and retrieve the jpdl file from e.g. your war and use a startup servlet to deploy it and have some checks around that to see if it is not already deployed.
I understand how to deploy a process via this part of code:
JbpmContext jbpmContext = jbpmConfiguration.createJbpmContext();
| ProcessDefinition processDefinition = ProcessDefinition.parseXmlResource(
| "org/xxx/definitions/yyy/processdefinition.xml");
| jbpmContext.deployProcessDefinition(processDefinition);
| jbpmContext.close();
I also understand how to run a process via:
jbpmContext = jbpmConfiguration.createJbpmContext();
| processInstance = jbpmContext.newProcessInstance("processname");
|
| contextInstance = processInstance.getContextInstance();
| contextInstance.setVariable("var", myVar);
|
| processInstance.getRootToken().signal();
|
So i know how to move the token by using different "signal".
But i still don't understand (I didn't find a true example on internet) how to "use the jbpm api and retrieve the jpdl file from" like you said.
Because now, as i understand, i can do all the movements i desire with the token on the workflow, but can't display it on the workflow image.
Can you show me a part of java code that retrieve this image from the "processdefinition.xml" and how to display it (and update it at each time that we move the token with the method token.signal("xxx")
I'd like to have for example the same interface like when we deploy with Jboss server (the image with a red square around the node).
=======================
In a second time, is there any other method via JBPM 4.1 ?
My collegue asks if there's a simple method by using the processdefinition.xml file, and the template folder deployed in the Webapps folder when installing JBPM 4.1 ?
Have you ever tested this version since its release ?
Thank you ^^ (again :p)
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4253151#4253151
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4253151
16 years, 7 months
[Installation, Configuration & Deployment] - twiddle does not work in web configuration if I change HTTP
by vbez
1. Choose default configuration.
Change port "The listening socket for the Naming service" in jboss-5.1.0.GA\server\default\conf\bindingservice.beans\META-INF\bindings-jboss-beans.xml from 1099 to 17235.
Run JBoss.
Execute next command:
twiddle.sh -s localhost:17235 serverinfo -d
Output - "jboss".
All is ok.
Change "A HTTP/1.1 Connector on port 8080" in jboss-5.1.0.GA/server/default/deploy/jbossweb.sar/server.xml from 8080 to 17230.
Run JBoss.
Execute next command:
Twiddle.sh -s localhost:17235 serverinfo -d
Output - "jboss".
All is ok.
2. Choose webconfiguration.
Change port "The listening socket for the Naming service" in jboss-5.1.0.GA\server\default\conf\bindingservice.beans\META-INF\bindings-jboss-beans.xml from 1099 to 17235.
Run JBoss.
Execute next command:
twiddle.sh -s localhost:17235 serverinfo -d
Output - "jboss".
All is ok.
Change "A HTTP/1.1 Connector on port 8080" in jboss-5.1.0.GA/server/default/deploy/jbossweb.sar/server.xml from 8080 to 17230.
Run JBoss.
Execute next command:
twiddle.sh -s localhost:17235 serverinfo -d
Output:
anonymous wrote : 19:10:41,347 DEBUG [Twiddle] args[0]=-s
| 19:10:41,352 DEBUG [Twiddle] args[1]=localhost:17235
| 19:10:41,352 DEBUG [Twiddle] args[2]=serverinfo
| 19:10:41,352 DEBUG [Twiddle] args[3]=-d
| 19:10:41,382 DEBUG [Twiddle] Command name: serverinfo
| 19:10:41,390 DEBUG [Twiddle] Command arguments: -d
| 19:10:41,391 DEBUG [Twiddle] command proto type properties: jar:file:/local/jboss/bin/twiddle.jar!/org/jboss/console/twiddle/commands.properties
| 19:10:41,407 DEBUG [Twiddle] Adding command 'jsr77'; proto: org.jboss.console.twiddle.command.JSR77Command@13421342
| 19:10:41,411 DEBUG [Twiddle] Adding command 'xmbean'; proto: org.jboss.console.twiddle.command.XMBeanCommand@23892389
| 19:10:41,414 DEBUG [Twiddle] Adding command 'info'; proto: org.jboss.console.twiddle.command.InfoCommand@2bfc2bfc
| 19:10:41,416 DEBUG [Twiddle] Adding command 'get'; proto: org.jboss.console.twiddle.command.GetCommand@350e350e
| 19:10:41,421 DEBUG [Twiddle] Adding command 'invoke'; proto: org.jboss.console.twiddle.command.InvokeCommand@40af40af
| 19:10:41,430 DEBUG [Twiddle] Adding command 'create'; proto: org.jboss.console.twiddle.command.CreateCommand@48c548c5
| 19:10:41,433 DEBUG [Twiddle] Adding command 'setattrs'; proto: org.jboss.console.twiddle.command.SetAttrsCommand@53355335
| 19:10:41,436 DEBUG [Twiddle] Adding command 'unregister'; proto: org.jboss.console.twiddle.command.UnregisterCommand@5a9c5a9c
| 19:10:41,439 DEBUG [Twiddle] Adding command 'queryMethod'; proto: org.jboss.console.twiddle.command.QueryMethodCommand@64a864a8
| 19:10:41,442 DEBUG [Twiddle] Adding command 'listDomains'; proto: org.jboss.console.twiddle.command.ListDomainsCommand@6bb06bb0
| 19:10:41,445 DEBUG [Twiddle] Adding command 'query'; proto: org.jboss.console.twiddle.command.QueryCommand@73567356
| 19:10:41,449 DEBUG [Twiddle] Adding command 'set'; proto: org.jboss.console.twiddle.command.SetCommand@79f179f1
| 19:10:41,454 DEBUG [Twiddle] Adding command 'serverinfo'; proto: org.jboss.console.twiddle.command.ServerInfoCommand@5ce05ce
| 19:10:41,460 DEBUG [ServerInfoCommand] processing arguments: -d
| 19:10:41,658 DEBUG [TimedSocketFactory] createSocket, hostAddr: localhost/127.0.0.1, port: 17235, localAddr: null, localPort: 0, timeout: 0
| 19:10:43,128 ERROR [Twiddle] Exec failed
| java.rmi.ServerException: IOE; nested exception is:
| java.net.ConnectException: Connection refused
| at org.jboss.invocation.http.interfaces.HttpInvokerProxy.invoke(HttpInvokerProxy.java:133)
| at org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
| at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
| at org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
| at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:68)
| at org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
| at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101)
| at $Proxy0.getDefaultDomain(Unknown Source)
| at org.jboss.console.twiddle.command.ServerInfoCommand.execute(ServerInfoCommand.java:137)
| at org.jboss.console.twiddle.Twiddle.main(Twiddle.java:306)
| Caused by:
| java.net.ConnectException: Connection refused
| at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:389)
| at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:250)
| at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:237)
| at java.net.Socket.connect(Socket.java:540)
| at java.net.Socket.connect(Socket.java:490)
| at sun.net.NetworkClient.doConnect(NetworkClient.java:180)
| at sun.net.www.http.HttpClient.openServer(HttpClient.java:403)
| at sun.net.www.http.HttpClient.openServer(HttpClient.java:521)
| at sun.net.www.http.HttpClient.(HttpClient.java:246)
| at sun.net.www.http.HttpClient.New(HttpClient.java:320)
| at sun.net.www.http.HttpClient.New(HttpClient.java:337)
| at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:822)
| at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:774)
| at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:699)
| at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:866)
| at org.jboss.invocation.http.interfaces.Util.invoke(Util.java:163)
| at org.jboss.invocation.http.interfaces.HttpInvokerProxy.invoke(HttpInvokerProxy.java:118)
Why twiddle does not work in case if we change HTTP port?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4253136#4253136
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4253136
16 years, 7 months
[JBoss Web Services Users] - disable client chunking in jbossws-3.0.1-native-2.0.4.GA
by kagey
Hey all,
I have an external webservice endpoint that i have wsconsumed the wsdl for and generated the necessary classes for a client to call the web services. I am dynamically setting the port endpoint at runtime to avoid consuming the wsdl at runtime. the code looks like:
| PrincipalManagement princMgmt = new PrincipalManagement(null,
| new QName("http://www.microsoft.com/iptv/bss",
| "PrincipalManagement"));
|
| PrincipalManagementSoap pms = princMgmt.getPrincipalManagementSoap();
|
| ((BindingProvider) pms).getRequestContext().put(
| BindingProvider.ENDPOINT_ADDRESS_PROPERTY,
| "http://" + wsServer
| + "/bss/PrincipalManagement.asmx");
|
The server also has NTLM authentication required. NTLM authentication is the thing that is breaking when using the newer version. It works fine in jboss 4.2.1, but not in 4.2.3. I believe the reason is because the request made with the older jbossws version does not use chunking (Transfer-Encoding: chunked), but rather specifes the content-length. here are the http header sniffs:
OLD version:
| POST /bss/PrincipalManagement.asmx?datatype=JBossWSMessage= HTTP/1.1
|
| SOAPAction: "http://www.microsoft.com/iptv/bss/ReadAccount"
| Content-Type: text/xml; charset=UTF-8
| JBoss-Remoting-Version: 22
| User-Agent: JBossRemoting - 2.2.1.GA (Bluto)
| Host: #.#.#.#
| Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
| Connection: keep-alive
| Content-Length: 185
| ...
|
NEW version:
| POST /bss/PrincipalManagement.asmx HTTP/1.1
| SOAPAction: "http://www.microsoft.com/iptv/bss/ReadAccount"
| Content-Type: text/xml; charset=UTF-8
| JBoss-Remoting-Version: 22
| User-Agent: JBossRemoting - 2.2.2.SP11
| Host: #.#.#.#
| Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
| Connection: keep-alive
| Transfer-Encoding: chunked
|
I see a newer version of jbossws (3.2...) has a chunking feature (http://www.jboss.org/community/wiki/JBossWS-NativeUserGuide#Chunked_encod...). Is it possible to disable client chunking on jbossws-3.0.1-native-2.0.4.GA?
Thanks
Kagey
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4253125#4253125
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4253125
16 years, 7 months