August 2009 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-2454) Principal not correctly resolved

by Heiko Braun (JIRA)

Principal not correctly resolved -------------------------------- Key: JBPM-2454 URL: https://jira.jboss.org/jira/browse/JBPM-2454 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: GWT Console 1.0.x In some cases the authenticated user is logged with operations on the engine. The REST fails to resolve the principal. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-2469) Update to console 1.1

by Heiko Braun (JIRA)

Update to console 1.1 --------------------- Key: JBPM-2469 URL: https://jira.jboss.org/jira/browse/JBPM-2469 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: jBPM 4.1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
2
0 / 0

[JBoss JIRA] Created: (JBPM-2470) Reference console war by classifier 'jbpm'

by Heiko Braun (JIRA)

Reference console war by classifier 'jbpm' ------------------------------------------ Key: JBPM-2470 URL: https://jira.jboss.org/jira/browse/JBPM-2470 Project: JBoss jBPM Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: jBPM 4.1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
2
0 / 0

[JBoss JIRA] Created: (JBPM-2324) Running console on 127.0.0.1 does not work (localhost does)

by Ronald van Kuijk (JIRA)

Running console on 127.0.0.1 does not work (localhost does) ----------------------------------------------------------- Key: JBPM-2324 URL: https://jira.jboss.org/jira/browse/JBPM-2324 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Console Affects Versions: GWT Console 1.0.0 CR1 Environment: Fedora 10, kernel 2.6.27, openjdk 6, JBoss AS 5.0.0, Firefox 3.0.10 Reporter: Ronald van Kuijk Priority: Minor If I open the console on 127.0.0.1 it does not work. The login page is shown, but nothing happens when entering data. If I open it on localhost it does work. Should maybe intially just be added to the releasenotes -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (JBPM-2326) Logging out does not work correctly

by Ronald van Kuijk (JIRA)

Logging out does not work correctly ----------------------------------- Key: JBPM-2326 URL: https://jira.jboss.org/jira/browse/JBPM-2326 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: GWT Console 1.0.0 CR1 Reporter: Ronald van Kuijk After logging out, I can login with the same user but using a wrong password. So effectively, a user is not fully logged out -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-1956) Integration API impl. breaks reporting

by Heiko Braun (JIRA)

Integration API impl. breaks reporting -------------------------------------- Key: JBPM-1956 URL: https://jira.jboss.org/jira/browse/JBPM-1956 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Heiko Braun The instance start dates are not set. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (JBPM-2140) the "version" of the processDefinition in db is a Long type not a Sting type

by fang changjiang (JIRA)

the "version" of the processDefinition in db is a Long type not a Sting type -------------------------------------------------------------------------------- Key: JBPM-2140 URL: https://jira.jboss.org/jira/browse/JBPM-2140 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: PVM Affects Versions: jBPM 4.0.0.Beta1 Environment: WINDOWS XP Eclipse JBOSS AS 4.2.2GA jbpm 4.0.0 Trunk Reporter: fang changjiang when I call ExecutionService.startProcessInstanceById() , I meet a Exception " exception while executing command org.jbpm.pvm.internal.cmd.StartProcessInstanceCmd@f9d4f7 java.lang.ClassCastException: java.lang.Long at org.jbpm.jpdl.internal.repository.JpdlDeployer.deploy(JpdlDeployer.java:72) " so I debug this call process, I find the root cause of the exception is in this segment " String version = (String) deployment.getObjectProperty(processDefinitionName, KEY_VERSION); " I find in the "jbpm.repository.hbm.xml" have " <property name="longValue" column="LONGVAL_" /> " map. I find in DeploymentProperty class the longValue is long type . so the Long type can't cast to String -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (JBPM-2276) net.sf.xframe.xsddoc.ProcessorException in jBPM4 with maven 2.1.0

by Jeff Yu (JIRA)

net.sf.xframe.xsddoc.ProcessorException in jBPM4 with maven 2.1.0 ----------------------------------------------------------------- Key: JBPM-2276 URL: https://jira.jboss.org/jira/browse/JBPM-2276 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.0.0.Beta2 Reporter: Jeff Yu By installing the maven 2.1.0, and then run: mvn clean install -Pschemadoc, you will have following exceptions: (With maven 2.0.9, I don't see this error) Caused by: java.io.FileNotFoundException: /local/works/jbpm4-idm/modules/api/local/works/jbpm4-idm/modules/api/src/main/resources/jpdl-4.0.xsd (No such file or directory) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.<init>(FileInputStream.java:106) at java.io.FileInputStream.<init>(FileInputStream.java:66) at sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:70) at sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:161) at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity(XMLEntityManager.java:973) at com.sun.org.apache.xerces.internal.impl.XMLVersionDetector.determineDocVersion(XMLVersionDetector.java:184) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:798) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148) at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:250) at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292) at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:146) at net.sf.xframe.xsddoc.Processor.getDocument(Processor.java:1253) at net.sf.xframe.xsddoc.Processor.processImport(Processor.java:990) at net.sf.xframe.xsddoc.Processor.processComponent(Processor.java:779) at net.sf.xframe.xsddoc.Processor.processComponents(Processor.java:747) at net.sf.xframe.xsddoc.Processor.process(Processor.java:719) at net.sf.xframe.xsddoc.Processor.process(Processor.java:691) at net.sf.xframe.xsddoc.Processor.execute(Processor.java:525) ... 25 more Caused by: java.io.FileNotFoundException: /local/works/jbpm4-idm/modules/api/local/works/jbpm4-idm/modules/api/src/main/resources/jpdl-4.0.xsd (No such file or directory) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.<init>(FileInputStream.java:106) at java.io.FileInputStream.<init>(FileInputStream.java:66) at sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:70) at sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:161) at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity(XMLEntityManager.java:973) at com.sun.org.apache.xerces.internal.impl.XMLVersionDetector.determineDocVersion(XMLVersionDetector.java:184) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:798) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148) at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:250) at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292) at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:146) at net.sf.xframe.xsddoc.Processor.getDocument(Processor.java:1253) at net.sf.xframe.xsddoc.Processor.processImport(Processor.java:990) at net.sf.xframe.xsddoc.Processor.processComponent(Processor.java:779) at net.sf.xframe.xsddoc.Processor.processComponents(Processor.java:747) at net.sf.xframe.xsddoc.Processor.process(Processor.java:719) at net.sf.xframe.xsddoc.Processor.process(Processor.java:691) at net.sf.xframe.xsddoc.Processor.execute(Processor.java:525) ... 25 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (JBPM-2431) NullPointerException in CreateDeploymentQueryCmd

by Eduard Dautov (JIRA)

NullPointerException in CreateDeploymentQueryCmd ------------------------------------------------ Key: JBPM-2431 URL: https://jira.jboss.org/jira/browse/JBPM-2431 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.0 Environment: Tomcat 6.0 on Windows XP and Java 1.6. Spring + BlazeDS Reporter: Eduard Dautov I deployed my process and when i try repositoryService.createDeploymentQuery().list(); i have NullPointerException. I debugged programm and found that instanse of org.jbpm.pvm.internal.session.DbSession is missed. can any one tell why its happened? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
5
0 / 0

[JBoss JIRA] Created: (JBPM-2461) made console independent from jboss server

by Hauke Rabe (JIRA)

made console independent from jboss server ------------------------------------------ Key: JBPM-2461 URL: https://jira.jboss.org/jira/browse/JBPM-2461 Project: JBoss jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Console Affects Versions: jBPM 4.0 Reporter: Hauke Rabe I would like to deploy the gwt-console on an embedded jetty (tomcat). Till now I found a dependeny in <GraphViewerPluginImpl> to resolve host and port, which could easily removed. All these dependencies could also be provided over a facade like the integration of jbpm3 / jbpm4. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues August 2009