March 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBPM-846) HibernateLongIdMatcher (and HibernateStringIdMatcher) is not processed correctly CGLib Enchanced classes

by Alexey Kakunin (JIRA)

HibernateLongIdMatcher (and HibernateStringIdMatcher) is not processed correctly CGLib Enchanced classes -------------------------------------------------------------------------------------------------------- Key: JBPM-846 URL: http://jira.jboss.com/jira/browse/JBPM-846 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM 3.1.3 Reporter: Alexey Kakunin Assigned To: Tom Baeyens Initially I though it is Hibernate Issue and reported it there: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2437 But seems from answer it is bug in jBPM. So, if we storing some object as variable in jBPM, and this object got from Hibernate - and enhanced by CGLib - it is not processed correctly. It is because HibernateLongIdMatcher (and HibernateStringIdMatcher) tried to get meta-data by using object.getClass() - but in this case Class-returned - is not a real class, but class enhanced by CGLib, as result, Hibernate did not returned us MetaData (because cannot find it) and as result - this object stored not as reference - but as BLOB. Some possible solutions provided in Hibernate Issue -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBPM-843) Custom TaskController variable setting should use getter/setter rather than fields

by Peter Muir (JIRA)

Custom TaskController variable setting should use getter/setter rather than fields ---------------------------------------------------------------------------------- Key: JBPM-843 URL: http://jira.jboss.com/jira/browse/JBPM-843 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM 3.1.4 Reporter: Peter Muir Assigned To: Tom Baeyens Priority: Minor If you do <controller class="MyTaskControllerHandler"> <foo>bar</foo> </controller> JBPM attempts to set the value of a field called foo on MyTaskControllerHandler. IMO it should call setFoo(bar) (encapsulation). See Seam's org.jboss.seam.util.Reflections for helper methods to do this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 months

2
1
0 / 0

[JBoss JIRA] Assigned: (JBPM-569) improve EL expression examples in the user guide

by Tom Baeyens (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-569?page=all ] Tom Baeyens reassigned JBPM-569: -------------------------------- Assignee: Koen Aers (was: Tom Baeyens) koen, could you have a look at this ? > improve EL expression examples in the user guide > ------------------------------------------------ > > Key: JBPM-569 > URL: http://jira.jboss.com/jira/browse/JBPM-569 > Project: JBoss jBPM > Issue Type: Task > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Koen Aers > Fix For: jBPM jPDL 3.2.1 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-904) task notify attribute and reminder element not right in schema

by Tom Baeyens (JIRA)

task notify attribute and reminder element not right in schema -------------------------------------------------------------- Key: JBPM-904 URL: http://jira.jboss.com/jira/browse/JBPM-904 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Reporter: Tom Baeyens Assigned To: Tom Baeyens Fix For: jBPM jPDL 3.2.1 these new schema elements were not properly modelled in the xsd schema file. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-4226) alternative deployment descriptor resolution fails on unix

by Dimitris Andreadis (JIRA)

alternative deployment descriptor resolution fails on unix ---------------------------------------------------------- Key: JBAS-4226 URL: http://jira.jboss.com/jira/browse/JBAS-4226 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB2 Affects Versions: JBossAS-4.2.0.CR1 Reporter: Dimitris Andreadis Assigned To: Dimitris Andreadis Fix For: JBossAS-5.0.0.Beta2, JBossAS-4.2.0.GA The url that is constructed contains an extra '/' on unix. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-4205) Nested DataSource fails to deploy before ejbs

by Scott M Stark (JIRA)

Nested DataSource fails to deploy before ejbs --------------------------------------------- Key: JBAS-4205 URL: http://jira.jboss.com/jira/browse/JBAS-4205 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployment services, EJB2 Reporter: Scott M Stark Assigned To: Scott M Stark Fix For: JBossAS-5.0.0.Beta2 The org.jboss.test.deadlock.test.BeanStressTestCase is failing because the included deadlock-ds.xml is not being deployed before the ejbs, even when the ejbs declare a dependency on "jboss.jca:service=LocalTxCM,name=DeadlockDS". -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBBUILD-344) Add ability to deploy aggregage projects (ejb3 api) to the jboss repository.

by Paul Gier (JIRA)

Add ability to deploy aggregage projects (ejb3 api) to the jboss repository. ---------------------------------------------------------------------------- Key: JBBUILD-344 URL: http://jira.jboss.com/jira/browse/JBBUILD-344 Project: JBoss Build System Issue Type: Feature Request Components: jboss-deploy-maven-plugin Reporter: Paul Gier Fix For: MavenBuild 1.2 Some projects need to deploy a combined jar file that contains classes from multiple sub-projects (modules). These can be deployed to the maven repository using the assembly and deploy plugins. The jboss-deploy-plugin should allow these aggregate jars to be deployed to the jboss repository. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 months

1
3
0 / 0

[JBoss JIRA] Updated: (JBCLUSTER-101) Make session clustering's "useJK" handling a pluggable policy so we can integrate with other load balancers

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBCLUSTER-101?page=all ] Brian Stansberry updated JBCLUSTER-101: --------------------------------------- Component/s: Web Tier > Make session clustering's "useJK" handling a pluggable policy so we can integrate with other load balancers > ----------------------------------------------------------------------------------------------------------- > > Key: JBCLUSTER-101 > URL: http://jira.jboss.com/jira/browse/JBCLUSTER-101 > Project: JBoss Clustering > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Web Tier > Reporter: Brian Stansberry > Assigned To: Brian Stansberry > Fix For: Q3Y7 > > > Session replication uses the JvmRouteValve to detect session failover and modify the session id so mod_jk knows to thereafter pin the the session to the new node. > JBossCacheManager also has logic that understands how to strip out the jvmRoute from the session id. > Need to make this logic a pluggable policy, so we can deal with other load balancers that may have a different mechanism for tracking to which node a session is pinned. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCLUSTER-86) Web container lacks cluster replication of application scope

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBCLUSTER-86?page=all ] Brian Stansberry updated JBCLUSTER-86: -------------------------------------- Component/s: Web Tier > Web container lacks cluster replication of application scope > ------------------------------------------------------------ > > Key: JBCLUSTER-86 > URL: http://jira.jboss.com/jira/browse/JBCLUSTER-86 > Project: JBoss Clustering > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Web Tier > Affects Versions: Q2Y5 > Reporter: treespace > Assigned To: Brian Stansberry > Fix For: Q3Y7 > > > Replication of servlet contexts (a.k.a. appliction scope) are not supported by the servlet specification. That is an important fact that needs to be emphased in cluster related documentation. Applications need to be cluster-aware at some level so this is just another design issue that needs to be accomodated. > An extra-specification feature to cluster the servlet context would be peachy. Generalizing a shared object that hides the underlying cache implementation could provide a more portable alternative: > getServletContext().getAttribute(MAGIC_BEAN).setAttribute("myBroadcastMessage", "All your servlet contexts are belong to us!"); > To port the application you would need a port of the MAGIC_BEAN class to use whatever clustering facilities are available on the target platform. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCLUSTER-14) http session failover using single shared DB with cache loader

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBCLUSTER-14?page=all ] Brian Stansberry updated JBCLUSTER-14: -------------------------------------- Component/s: Web Tier Fix Version/s: Q3Y7 (was: Q2Y7) > http session failover using single shared DB with cache loader > -------------------------------------------------------------- > > Key: JBCLUSTER-14 > URL: http://jira.jboss.com/jira/browse/JBCLUSTER-14 > Project: JBoss Clustering > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Web Tier > Reporter: Ben Wang > Assigned To: Brian Stansberry > Priority: Minor > Fix For: Q3Y7 > > Original Estimate: 8 weeks > Remaining Estimate: 8 weeks > > To achieve http session failover, alternatively we can use a single shared DB with CacheLoader for multiple cache instances. All the session states will be persisted to the shared DB. When failing over, it will simply retrieve from the DB if it is not there yet. > This approach can scale very well. But it will be slower since every session setAttribute operation involves trip to DB. JBossCache already supports this semantics now. All we need is someone to verify it and benchmark it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2007