January 2008 - jboss-jira - Jboss List Archives

[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

16 years, 5 months

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

16 years, 5 months

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

16 years, 5 months

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

16 years, 5 months

4
5
0 / 0

[JBoss JIRA] Closed: (EJBTHREE-553) PrePersist callback method not called if entity's primery key is null

by Carlo de Wolf (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-553?page=all ] Carlo de Wolf closed EJBTHREE-553. ---------------------------------- > PrePersist callback method not called if entity's primery key is null > --------------------------------------------------------------------- > > Key: EJBTHREE-553 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-553 > Project: EJB 3.0 > Issue Type: Bug > Environment: jboss-4.0.4.CR2 > Reporter: Michal Borowiecki > Assigned To: Emmanuel Bernard > Fix For: AS 5.0.0.Beta3 > > Attachments: EJB3EventListener_v2.patch > > > When an entity is persisted which does not have its primary key set (and it is not annotated with GeneratedValue annotation), the @PrePersist callback method is not invoked. > Instead the exception is thrown: > Caused by: org.hibernate.id.IdentifierGenerationException: ids for this class must be manually assigned before calling save(): com.bluemedia.system.User > at org.hibernate.id.Assigned.generate(Assigned.java:33) > at org.hibernate.event.def.AbstractSaveEventListener.saveWithGeneratedId(AbstractSaveEventListener.java:98) > at org.hibernate.event.def.DefaultPersistEventListener.entityIsTransient(DefaultPersistEventListener.java:131) > at org.hibernate.event.def.DefaultPersistEventListener.onPersist(DefaultPersistEventListener.java:87) > at org.hibernate.event.def.DefaultPersistEventListener.onPersist(DefaultPersistEventListener.java:38) > at org.hibernate.impl.SessionImpl.firePersist(SessionImpl.java:617) > at org.hibernate.impl.SessionImpl.persist(SessionImpl.java:591) > at org.hibernate.impl.SessionImpl.persist(SessionImpl.java:595) > at org.hibernate.ejb.AbstractEntityManagerImpl.persist(AbstractEntityManagerImpl.java:187) > ... 64 more > This is in conflict with ejb 3.0-pfd spec, which states (sec. 3.4.2) : > "The PrePersist and PreRemove callback methods are invoked for a given entity before the respective EntityManager persist and remove operations for that entity are executed." > Since the spec states that EntityManager's persist operation is executed after the PrePersist callback methods, setting the value of the primary key in a PrePersist callback method seems a reasonable use case. -- 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

16 years, 5 months

1
0
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

16 years, 5 months

2
6
0 / 0

[JBoss JIRA] Created: (JBRULES-1376) Mispelling in the automatically generated .project file using the guided editor

by Carlos Bustamante (JIRA)

Mispelling in the automatically generated .project file using the guided editor ------------------------------------------------------------------------------- Key: JBRULES-1376 URL: http://jira.jboss.com/jira/browse/JBRULES-1376 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: Eclipse IDE Affects Versions: 4.0.3 Environment: Eclipse IDE 3.3.1.1 Reporter: Carlos Bustamante Priority: Trivial When using the guided editor for rules in the Drools plugin for Eclipse IDE 3.3, the generated rule.package file has the following comments: //This is a package configuration file //Add imports, globals etc here which will be used by all the rule assets in thise folder. There is a mispelling, the word "thise" should be "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

16 years, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1687) Maven modules migration

by Julien Viet (JIRA)

Maven modules migration ----------------------- Key: JBPORTAL-1687 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1687 Project: JBoss Portal Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Julien Viet Assigned To: Wesley Hales Fix For: 2.8 Final -- 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

16 years, 5 months

3
9
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1864) Improve logging in JBossUnit

by Boleslaw Dawidowicz (JIRA)

Improve logging in JBossUnit ---------------------------- Key: JBPORTAL-1864 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1864 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Boleslaw Dawidowicz Assigned To: Boleslaw Dawidowicz There is no real logging in JBossUnit and build plugins. -- 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

16 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1863) Make JPDa support in JBossUnit configurable

by Boleslaw Dawidowicz (JIRA)

Make JPDa support in JBossUnit configurable ------------------------------------------- Key: JBPORTAL-1863 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1863 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Boleslaw Dawidowicz Make JPDa support in JBossUnit configurable in both ant and maven plugins. At least port number and suspend should be configurable. -- 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

16 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2008