Build failed in Hudson: jbpm4-jboss » postgresql,5.0.0.GA,java16_default,dev45 #80
by jboss-qa-internal＠redhat.com
See http://hudson.qa.jboss.com/hudson/job/jbpm4-jboss/./DATABASE=postgresql,J...
------------------------------------------
started
Building remotely on dev45
Updating https://svn.jboss.org/repos/jbpm/jbpm4/trunk
ERROR: Failed to update https://svn.jboss.org/repos/jbpm/jbpm4/trunk
org.tmatesoft.svn.core.SVNException: svn: No route to host
svn: OPTIONS request failed on '/repos/jbpm/jbpm4/trunk'
at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:103)
at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:87)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:601)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:257)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:245)
at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:454)
at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:97)
at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:664)
at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getRepositoryUUID(DAVRepository.java:143)
at org.tmatesoft.svn.core.wc.SVNBasicClient.createRepository(SVNBasicClient.java:339)
at org.tmatesoft.svn.core.wc.SVNBasicClient.createRepository(SVNBasicClient.java:327)
at org.tmatesoft.svn.core.wc.SVNUpdateClient.update(SVNUpdateClient.java:426)
at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:394)
at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:210)
at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:464)
at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:435)
at hudson.FilePath$FileCallableWrapper.call(FilePath.java:1252)
at hudson.remoting.UserRequest.perform(UserRequest.java:92)
at hudson.remoting.UserRequest.perform(UserRequest.java:46)
at hudson.remoting.Request$2.run(Request.java:236)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.net.NoRouteToHostException: No route to host
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:519)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:550)
at org.tmatesoft.svn.core.internal.util.SVNSocketFactory.createSSLSocket(SVNSocketFactory.java:65)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.connect(HTTPConnection.java:167)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:307)
... 23 more
Recording test results
16 years, 3 months
[Design of JBoss jBPM] - Re: Implementation of XPDL in jBPM
by camunda
Hi Sebastion.
anonymous wrote :
| Since they took the PVM to implement XPDL why didn't they contribute this to the jBPM project but started an own project instead?
|
The Bonita engine is out already quite a while, they just decided to do some joint effort with jbpm and use the PVM in their new version. Bonita 3 was completly independant.
On the other hand it would be really cool to see other engines and products building their own stuff on the PVM. JBoss itself will not develop these themself. And: Embrace choice :-)
anonymous wrote :
| I got confused a bit with the two standarized languages of the WfMC. I'm still new to the topic and to me it looked like there was a strong relation with BPMN on one side for the notation of processes and with XPDL on the other side for the execution of processes.
|
BPMN is from the OMG (like UML), only XPDL is from the WfMC. And my personal view is, they tried to at least participate in the BPMN hype somehow, that's why they tried to make a connection.
anonymous wrote :
| To me it's just crucial to have a standarized format which is vendor-independent and commonly accepted. So in your opinion XPDL is not that important although it's standardised and it would make more sense to wait for BPMN 2.0 which will add semantics and process execution to the BPMN standard?
|
Depends. Is the standard a pure political issue and you have to start today? Then maybe XPDL is a good option. Maybe then it is already sufficient that jbpm 4 uses BPDs (the diagrams standardized in BPMN). Problem is, current BPMN 1.2 doesn't define a XML-File-Format.
Or do you really need vendor independance (why?)? Then BPMN 2.0 would definitley get interesting, but this will still need some time.
But what a coicidence, currently I am writing on a BPMN book (http://www.hanser.de/buch.asp?isbn=978-3-446-41768-7) and I am working on a Proof of concept: a very simple BPMN 2.0 Engine based on the PVM :-)
Cheers
Bernd
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4243115#4243115
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4243115
16 years, 3 months