August 2008 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Work started: (JBPM-1446) display non GMT+0 time zones

by Alejandro Guizar (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1446?page=com.atlassian.jira.plug... ] Work on JBPM-1446 started by Alejandro Guizar. > display non GMT+0 time zones > ---------------------------- > > Key: JBPM-1446 > URL: https://jira.jboss.org/jira/browse/JBPM-1446 > Project: JBoss jBPM > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core Engine > Reporter: Jiri Pechanec > Assignee: Alejandro Guizar > Fix For: SOA 4.2 CP03, SOA 4.3 > > Attachments: Screenshot.jpg > > > I spotted it today so I am creating the link to project JIRA. It is really inconvenient for user to have UTC time displayed in browser. See JBPM-987 -- 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

15 years, 9 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-1448) jBPM does not initialise thread context classloader

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1448?page=com.atlassian.jira.plug... ] Thomas Diesler updated JBPM-1448: --------------------------------- Assignee: Trevor Kirby (was: Thomas Diesler) Hi Trevor, what is the SOA branch I should use for testing? > jBPM does not initialise thread context classloader > --------------------------------------------------- > > Key: JBPM-1448 > URL: https://jira.jboss.org/jira/browse/JBPM-1448 > Project: JBoss jBPM > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core Engine > Reporter: Kevin Conner > Assignee: Trevor Kirby > Priority: Critical > Fix For: SOA 4.2 CP03, SOA 4.3 > > > jBPM does not initialise the thread context classloader when executing actions within the process. > The outcome of this decision is that code executed within the context of this action will not have access to classes/resources in the par unless the action classloader is an explicit parameter. > One example of this is the RMI marshalling layer, which has an implication on JNDI lookups. -- 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

15 years, 9 months

1
0
0 / 0

[JBoss JIRA] Work stopped: (JBPM-1448) jBPM does not initialise thread context classloader

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1448?page=com.atlassian.jira.plug... ] Work on JBPM-1448 stopped by Thomas Diesler. > jBPM does not initialise thread context classloader > --------------------------------------------------- > > Key: JBPM-1448 > URL: https://jira.jboss.org/jira/browse/JBPM-1448 > Project: JBoss jBPM > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core Engine > Reporter: Kevin Conner > Assignee: Thomas Diesler > Priority: Critical > Fix For: SOA 4.2 CP03, SOA 4.3 > > > jBPM does not initialise the thread context classloader when executing actions within the process. > The outcome of this decision is that code executed within the context of this action will not have access to classes/resources in the par unless the action classloader is an explicit parameter. > One example of this is the RMI marshalling layer, which has an implication on JNDI lookups. -- 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

15 years, 9 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-1443) Follup to SOA-344 - should the namespace reference be removed?

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1443?page=com.atlassian.jira.plug... ] Thomas Diesler updated JBPM-1443: --------------------------------- Assignee: Tom Baeyens Tom, could you please take care of this. > Follup to SOA-344 - should the namespace reference be removed? > -------------------------------------------------------------- > > Key: JBPM-1443 > URL: https://jira.jboss.org/jira/browse/JBPM-1443 > Project: JBoss jBPM > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core Engine > Environment: standalone-soa-4.2.0.CR1.zip > soa-4.2.0.CR1.zip > Reporter: Len DiMaggio > Assignee: Tom Baeyens > Fix For: SOA 4.2 CP03, SOA 4.3 > > > Followup to SOA-344 > The fix in SOA-344 was to remove the namespace reference. Don't we need this? -- 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

15 years, 9 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-1449) com.sun.facelets.compiler.TagLibraryConfig loadImplicit errors reported when jBPM console is accessed

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1449?page=com.atlassian.jira.plug... ] Thomas Diesler updated JBPM-1449: --------------------------------- Assignee: Tom Baeyens Tom, could you please take care of this. > com.sun.facelets.compiler.TagLibraryConfig loadImplicit errors reported when jBPM console is accessed > ----------------------------------------------------------------------------------------------------- > > Key: JBPM-1449 > URL: https://jira.jboss.org/jira/browse/JBPM-1449 > Project: JBoss jBPM > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core Engine > Reporter: Len DiMaggio > Assignee: Tom Baeyens > Priority: Minor > Fix For: SOA 4.2 CP03, SOA 4.3 > > > Platform JIRA for project JIRA: JBPM-1065 -- 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

15 years, 9 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-1441) JBPM.3 failures with sybase 12.5

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1441?page=com.atlassian.jira.plug... ] Thomas Diesler updated JBPM-1441: --------------------------------- Assignee: Tom Baeyens Tom, could you please take care of this. > JBPM.3 failures with sybase 12.5 > -------------------------------- > > Key: JBPM-1441 > URL: https://jira.jboss.org/jira/browse/JBPM-1441 > Project: JBoss jBPM > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core Engine > Reporter: Aleksandar Kostadinov > Assignee: Tom Baeyens > Fix For: SOA 4.2 CP03, SOA 4.3 > > > Tests failing with sybase 12.5 > JBPM-1177 -- 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

15 years, 9 months

1
0
0 / 0

[JBoss JIRA] Deleted: (JBPM-1405) jBPM does not initialise thread context classloader

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1405?page=com.atlassian.jira.plug... ] Thomas Diesler deleted JBPM-1405: --------------------------------- > jBPM does not initialise thread context classloader > ---------------------------------------------------- > > Key: JBPM-1405 > URL: https://jira.jboss.org/jira/browse/JBPM-1405 > Project: JBoss jBPM > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Mark Little > Assignee: Thomas Diesler > Priority: Critical > > jBPM does not initialise the thread context classloader when executing actions within the process. > The outcome of this decision is that code executed within the context of this action will not have access to classes/resources in the par unless the action classloader is an explicit parameter. > One example of this is the RMI marshalling layer, which has an implication on JNDI lookups. -- 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

15 years, 9 months

1
0
0 / 0

[JBoss JIRA] Work started: (JBPM-1448) jBPM does not initialise thread context classloader

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1448?page=com.atlassian.jira.plug... ] Work on JBPM-1448 started by Thomas Diesler. > jBPM does not initialise thread context classloader > --------------------------------------------------- > > Key: JBPM-1448 > URL: https://jira.jboss.org/jira/browse/JBPM-1448 > Project: JBoss jBPM > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core Engine > Reporter: Kevin Conner > Assignee: Thomas Diesler > Priority: Critical > Fix For: SOA 4.2 CP03, SOA 4.3 > > > jBPM does not initialise the thread context classloader when executing actions within the process. > The outcome of this decision is that code executed within the context of this action will not have access to classes/resources in the par unless the action classloader is an explicit parameter. > One example of this is the RMI marshalling layer, which has an implication on JNDI lookups. -- 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

15 years, 9 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBPM-1451) Check that jBPM can be run against all of the Tier 1 databases for SOA-P.

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1451?page=com.atlassian.jira.plug... ] Thomas Diesler reassigned JBPM-1451: ------------------------------------ Assignee: Trevor Kirby (was: Thomas Diesler) Hi Trevor, what are the Tier-1 DBs? > Check that jBPM can be run against all of the Tier 1 databases for SOA-P. > ------------------------------------------------------------------------- > > Key: JBPM-1451 > URL: https://jira.jboss.org/jira/browse/JBPM-1451 > Project: JBoss jBPM > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Core Engine > Reporter: Mark Little > Assignee: Trevor Kirby > Fix For: SOA 4.3 > > > Do we need special initialisation scripts as well? -- 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

15 years, 9 months

1
0
0 / 0

[JBoss JIRA] Deleted: (JBPM-1447) jBPM classloader does not define package information

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1447?page=com.atlassian.jira.plug... ] Thomas Diesler deleted JBPM-1447: --------------------------------- > jBPM classloader does not define package information > ---------------------------------------------------- > > Key: JBPM-1447 > URL: https://jira.jboss.org/jira/browse/JBPM-1447 > Project: JBoss jBPM > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Kevin Conner > Assignee: Thomas Diesler > Priority: Critical > > The jBPM ProcessClassLoader defines classes from within the par file but it does not define the associated package information. > As a consequence the result of <class>.getPackage() is null and code which relies on this (such as JAXB for package annotations) will not work. > A simple fix would be to add the following to the findClass method although it should be noted that this ignores the manifest/sealing information. > if (fileDefinition!=null) { > // Add the package information > final int packageIndex = name.lastIndexOf('.') ; > if (packageIndex != -1) { > final String packageName = name.substring(0, packageIndex) ; > final Package classPackage = getPackage(packageName) ; > if (classPackage == null) { > definePackage(packageName, null, null, null, null, null, null, null) ; > } > } > With this fix in place the JAXB marshalling works as expected. -- 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

15 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues August 2008