October 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBCACHE-788) Optimistic locking should not REQUIRE transactions!

by Manik Surtani (JIRA)

Optimistic locking should not REQUIRE transactions! --------------------------------------------------- Key: JBCACHE-788 URL: http://jira.jboss.com/jira/browse/JBCACHE-788 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 1.4.0, 1.3.0, 2.0.0 Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.1.0 Makes things simpler. TXs are only used so transaction workspaces can be stored in a transaction entry. This workspace can just as easily be stored in ThreadLocal for non-tx calls (that just have the lifespan of a single invocation). This will: 1) Make things a LOT quicker since we don't need 2PC for all calls. 2) Make the TxInterceptor a lot simpler 3) Allow the use of Opt Locking without a TM -- 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

17 years

2
3
0 / 0

[JBoss JIRA] Created: (JBBUILD-324) Build.xml in testsuite directory doesn't support multiple JVM argument

by Sunny Chan (JIRA)

Build.xml in testsuite directory doesn't support multiple JVM argument ---------------------------------------------------------------------- Key: JBBUILD-324 URL: http://jira.jboss.com/jira/browse/JBBUILD-324 Project: JBoss Build System Issue Type: Feature Request Components: Targets and Tasks Affects Versions: Repository Build head, Repsository Build Branch_4_0 Environment: Any Reporter: Sunny Chan Priority: Minor We are using the JBoss unit test as part of our JVM verification testsuite. We wanted to be able to invoke tests with multiple JVM options, but it didn't work. If you set parameters via build.sh -Djunit.vm.options with multiple paramters (e.g. -Djunit.vm.options="-d64 -verbose:gc"), it will fail with unrecongized option error. The problem is that in testsuite/build.xml, the junit.vm.options is passed onto junit ant task via <jvmarg value> tag rather then <jvmarg line> tag. The jvmarg line allows multiple JVM options exist in one line. Once I replace all instance of <jvmarg value="${junit.jvm.options}"/> with <jvmarg line="${junit.jvm.options}"/> then the problem goes away. I can provide a patch for this if you want - but I don't know the rules on patches (whether I need to be cleared for contribution) so let me know if you want that. -- 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

17 years

4
8
0 / 0

[JBoss JIRA] Created: (EJBTHREE-749) org.jboss.ejb3.remoting.IsLocalInterceptor does not has a SerialVersionUID and causes problems when using jboss-ejb3-client.jar to access remote session bean

by Peter Salomonsen (JIRA)

org.jboss.ejb3.remoting.IsLocalInterceptor does not has a SerialVersionUID and causes problems when using jboss-ejb3-client.jar to access remote session bean ------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: EJBTHREE-749 URL: http://jira.jboss.com/jira/browse/EJBTHREE-749 Project: EJB 3.0 Issue Type: Bug Components: EJB3 Extensions Affects Versions: EJB 3.0 RC9 - FD Environment: Sun JDK 1.5.0.06 / Ubuntu 6.0.6 Reporter: Peter Salomonsen When using jboss-ejb3-client.jar to lookup a remote interface of an ejb3 stateless session bean I get this exception: Exception: javax.naming.CommunicationException [Root exception is java.io.InvalidClassException: org.jboss.ejb3.remoting.IsLocalInterceptor; local class incompatible: stream classdesc serialVersionUID = -3758782076801249473, local class serialVersionUID = 595045557897063404] When removing jboss-ejb3-client.jar and instead using the same jar as the server, it works fine. I guess the resolution may be to add a SerialVersionUID for org.jboss.ejb3.remoting.IsLocalInterceptor -- 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

17 years

4
5
0 / 0

[JBoss JIRA] Created: (EJBTHREE-751) @Local and @Remote on one interface must not be allowed

by Carlo de Wolf (JIRA)

@Local and @Remote on one interface must not be allowed ------------------------------------------------------- Key: EJBTHREE-751 URL: http://jira.jboss.com/jira/browse/EJBTHREE-751 Project: EJB 3.0 Issue Type: Bug Reporter: Carlo de Wolf EJB3 4.6.7 bullet 5.4 'The same business interface cannot be both a local and a remote business interface of the bean.' -- 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

17 years

4
13
0 / 0

[JBoss JIRA] Created: (EJBTHREE-725) Problem with OneToOne annotation

by Ilya (JIRA)

Problem with OneToOne annotation -------------------------------- Key: EJBTHREE-725 URL: http://jira.jboss.com/jira/browse/EJBTHREE-725 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC9 - FD Reporter: Ilya Priority: Minor Given to classes as in hibernate doc: @Entity public class Body { @Id public Long getId() { return id; } @OneToOne @PrimaryKeyJoinColumn public Heart getHeart() { return heart; } ... } @Entity public class Heart { @Id public Long getId() { ...} @OneToOne(mappedBy = "heart") public Heart getHeart() { return heart; } } everything works, but when I moved mappedBy to body deployment failed with NPE in class OneToOneSecondPass on line 135, because otherSideProperty was null. Testcase (deploymnt fails with NPE): ------------------ @Entity public class Body { @Id public Long getId() { return id; } @OneToOne(mappedBy = "body") public Heart getHeart() { return heart; } ... } @Entity public class Heart { @Id public Long getId() { ...} @OneToOne @PrimaryKeyJoinColumn public Heart getHeart() { return heart; } } ------------------ -- 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

17 years

3
6
0 / 0

[JBoss JIRA] Created: (EJBTHREE-718) Application client deployer

by Carlo de Wolf (JIRA)

Application client deployer --------------------------- Key: EJBTHREE-718 URL: http://jira.jboss.com/jira/browse/EJBTHREE-718 Project: EJB 3.0 Issue Type: Task Affects Versions: EJB 3.0 RC10 - FD Reporter: Carlo de Wolf Assigned To: Carlo de Wolf Build support for JavaEE 5 application clients (see EE.9 Application Clients) - create a JBossXB parser for application_client_5.xsd - create a client deployer - create a client launcher -- 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

17 years

2
6
0 / 0

[JBoss JIRA] Created: (EJBTHREE-714) Session objects returned by injection should implement SessionImplementor in addition to o.h.classic.Session

by Emmanuel Bernard (JIRA)

Session objects returned by injection should implement SessionImplementor in addition to o.h.classic.Session ------------------------------------------------------------------------------------------------------------ Key: EJBTHREE-714 URL: http://jira.jboss.com/jira/browse/EJBTHREE-714 Project: EJB 3.0 Issue Type: Bug Components: EJB3 Extensions Affects Versions: EJB 3.0 RC9 - FD Reporter: Emmanuel Bernard Priority: Minor Hibernate internally can cast a session object to org.hibernate.classic.Session (subinterface of org.hibernate.Session) org.hibernate.engine.SessionImplementor This is especially useful when using the DetachedCriteria API So at least org.jboss.ejb3.entity.TransactionScopedHibernateSession should implement 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

17 years

4
8
0 / 0

[JBoss JIRA] Created: (EJBTHREE-712) Support EJBContext injection through ejb-jar.xml

by Bill Burke (JIRA)

Support EJBContext injection through ejb-jar.xml ------------------------------------------------ Key: EJBTHREE-712 URL: http://jira.jboss.com/jira/browse/EJBTHREE-712 Project: EJB 3.0 Issue Type: Task Affects Versions: EJB 3.0 RC10 - FD Reporter: Bill Burke Assigned To: Carlo de Wolf Spec says you use <resource-env-ref> to do injection of EJBContext into a bean. -- 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

17 years

4
13
0 / 0

[JBoss JIRA] Created: (EJBTHREE-687) EntityManager.getDelegate()

by Emmanuel Bernard (JIRA)

EntityManager.getDelegate() --------------------------- Key: EJBTHREE-687 URL: http://jira.jboss.com/jira/browse/EJBTHREE-687 Project: EJB 3.0 Issue Type: Feature Request Reporter: Emmanuel Bernard Fix For: EJB 3.0 RC9 - FD EntityManager.getdelegate() currently returns the underlying entityManager (let's say HibernateEntityManager) It is more convinient and coherence between SE and EE to return hibernateEntityManager.getDelegate() rather than hibernate EntityManager -- 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

17 years

4
5
0 / 0

[JBoss JIRA] Created: (EJBTHREE-651) javax.ejb.SessionContext.getBusinessObject has wrong signature

by Carlo de Wolf (JIRA)

javax.ejb.SessionContext.getBusinessObject has wrong signature -------------------------------------------------------------- Key: EJBTHREE-651 URL: http://jira.jboss.com/jira/browse/EJBTHREE-651 Project: EJB 3.0 Issue Type: Bug Reporter: Carlo de Wolf javax.ejb.SessionContext.getBusinessObject must have the following signature: <T> T getBusinessObject(Class<T> businessInterface) throws IllegalStateException; See http://java.sun.com/javaee/5/docs/api/javax/ejb/SessionContext.html#getBu... -- 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

17 years

2
6
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2006