September 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (EJBTHREE-405) Allow EJB Container's ObjectName to be configurable through annotation or XML

by Bill Burke (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-405?page=all ] Bill Burke updated EJBTHREE-405: -------------------------------- Fix Version/s: (was: EJB 3.0 RC9 - FD) EJB 3.0 RC10 - FD > Allow EJB Container's ObjectName to be configurable through annotation or XML > ----------------------------------------------------------------------------- > > Key: EJBTHREE-405 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-405 > Project: EJB 3.0 > Issue Type: Feature Request > Reporter: Bill Burke > Assigned To: Bill Burke > Fix For: EJB 3.0 RC10 - FD > > -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (EJBTHREE-420) redeploy of TreeCached entities fails

by Bill Burke (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-420?page=all ] Bill Burke updated EJBTHREE-420: -------------------------------- Fix Version/s: (was: EJB 3.0 RC9 - FD) EJB 3.0 RC10 - FD > redeploy of TreeCached entities fails > ------------------------------------- > > Key: EJBTHREE-420 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-420 > Project: EJB 3.0 > Issue Type: Bug > Affects Versions: EJB 3.0 RC3 > Reporter: Bill Burke > Assigned To: Bill Burke > Fix For: EJB 3.0 RC10 - FD > > > 2006-01-20 15:14:19,843 INFO [STDOUT] org.hibernate.PropertyAccessException: exception getting property value with CGLIB (set hibernate.cglib.use_reflection_optimizer=false for more info) getter of com.airit.fidsdb.entity.ArrPrevPortPK.? > at org.hibernate.tuple.PojoComponentTuplizer.getPropertyValues(PojoComponentTuplizer.java:79) > at org.hibernate.type.ComponentType.getPropertyValues(ComponentType.java:307) > at org.hibernate.type.ComponentType.isEqual(ComponentType.java:111) > at org.hibernate.cache.CacheKey.equals(CacheKey.java:51) > at org.jboss.cache.Fqn.equals(Fqn.java:134) > at java.util.HashMap.eq(HashMap.java:277) > at java.util.HashMap.containsKey(HashMap.java:346) > at org.jboss.cache.eviction.LRUAlgorithm.add(LRUAlgorithm.java:126) > at org.jboss.cache.eviction.LRUAlgorithm.processAddedNodes(LRUAlgorithm.java:99) > at org.jboss.cache.eviction.LRUAlgorithm.processQueues(LRUAlgorithm.java:77) > at org.jboss.cache.eviction.LRUAlgorithm.process(LRUAlgorithm.java:52) > at org.jboss.cache.eviction.EvictionTimerTask.run(EvictionTimerTask.java:37) > at java.util.TimerThread.mainLoop(Timer.java:512) > at java.util.TimerThread.run(Timer.java:462) > Caused by: java.lang.ClassCastException: com.airit.fidsdb.entity.ArrPrevPortPK > at com.airit.fidsdb.entity.ArrPrevPortPK$$BulkBeanByCGLIB$$8b6b36b9.getPropertyValues(<generated>) > at net.sf.cglib.beans.BulkBean.getPropertyValues(BulkBean.java:48) > at org.hibernate.tuple.PojoComponentTuplizer.getPropertyValues(PojoComponentTuplizer.java:76) > ... 13 more -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (EJBTHREE-402) Remoting proxies are not declaring serialVersionUIDs

by Bill Burke (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-402?page=all ] Bill Burke updated EJBTHREE-402: -------------------------------- Fix Version/s: (was: EJB 3.0 RC9 - FD) EJB 3.0 RC10 - FD > Remoting proxies are not declaring serialVersionUIDs > ---------------------------------------------------- > > Key: EJBTHREE-402 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-402 > Project: EJB 3.0 > Issue Type: Bug > Affects Versions: EJB 3.0 RC3 > Reporter: Scott M Stark > Priority: Critical > Fix For: EJB 3.0 RC10 - FD > > > Same old lack of explicit serialVersionUIDs causing major incompatibilities across releases: > java: org.jnp.interfaces.NamingContext@bd0108 > Looking up RemoteCalculator > javax.naming.CommunicationException [Root exception is java.io.InvalidClassException: org.jboss.ejb3.stateless.StatelessRemoteProxy; local class incompatible: stream classdesc serialVersionUID = 2583299153931800023, local class serialVersionUID = 8144530673853515126] > at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:707) > at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:572) > at javax.naming.InitialContext.lookup(InitialContext.java:351) > at trail.client.RemoteCalculatorClient.main(RemoteCalculatorClient.java:38) > Caused by: java.io.InvalidClassException: org.jboss.ejb3.stateless.StatelessRemoteProxy; local class incompatible: stream classdesc serialVersionUID = 2583299153931800023, local class serialVersionUID = 8144530673853515126 > at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:519) > at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1546) > at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1460) > at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1693) > at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1299) > at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1912) > at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1836) > at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1713) > at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1299) > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:339) > at java.rmi.MarshalledObject.get(MarshalledObject.java:135) > at org.jnp.interfaces.MarshalledValuePair.get(MarshalledValuePair.java:57) > at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:637) -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (EJBTHREE-344) Deployment should fail for resource injection to both field and method

by Bill Burke (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-344?page=all ] Bill Burke updated EJBTHREE-344: -------------------------------- Fix Version/s: EJB 3.0 RC10 - FD (was: EJB 3.0 RC9 - FD) > Deployment should fail for resource injection to both field and method > ---------------------------------------------------------------------- > > Key: EJBTHREE-344 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-344 > Project: EJB 3.0 > Issue Type: Bug > Environment: org.jboss.ejb3.test.naming.unit.BadInjectionsUnitTestCase > Reporter: Scott M Stark > Assigned To: William DeCoste > Fix For: EJB 3.0 RC10 - FD > > > I belive the indicated BadInjectionsUnitTestCase should be failing to deploy due to the attempt to inject an env-entry via both a field and method annotation. The ejb-jar.xml key env-entry value is not being injected via either mechanism it appears. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (EJBTHREE-466) support persistence properties for XML and injection annotations

by Bill Burke (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-466?page=all ] Bill Burke updated EJBTHREE-466: -------------------------------- Fix Version/s: EJB 3.0 RC10 - FD (was: EJB 3.0 RC9 - FD) > support persistence properties for XML and injection annotations > ---------------------------------------------------------------- > > Key: EJBTHREE-466 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-466 > Project: EJB 3.0 > Issue Type: Task > Affects Versions: EJB 3.0 RC5 - PFD > Reporter: Bill Burke > Assigned To: Bill Burke > Fix For: EJB 3.0 RC10 - FD > > -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (EJBTHREE-477) Implement @WebServiceRef and <service-ref>

by Bill Burke (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-477?page=all ] Bill Burke updated EJBTHREE-477: -------------------------------- Fix Version/s: (was: EJB 3.0 RC9 - FD) EJB 3.0 RC10 - FD > Implement @WebServiceRef and <service-ref> > ------------------------------------------ > > Key: EJBTHREE-477 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-477 > Project: EJB 3.0 > Issue Type: Task > Reporter: Bill Burke > Assigned To: William DeCoste > Priority: Critical > Fix For: EJB 3.0 RC10 - FD > > > This will be fun!!!! > Take a look at code in EJB 2.1 container. DO NOT USE THAT CODE DIRECTLY. I want to start removing dependencies on that code. You can also work with WS team on this too. This should be a HIG PRIORITY task. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (EJBTHREE-582) Refactoring/implementation of ejb3 sfsb clustering

by Bill Burke (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-582?page=all ] Bill Burke updated EJBTHREE-582: -------------------------------- Fix Version/s: EJB 3.0 RC10 - FD (was: EJB 3.0 RC9 - FD) > Refactoring/implementation of ejb3 sfsb clustering > -------------------------------------------------- > > Key: EJBTHREE-582 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-582 > Project: EJB 3.0 > Issue Type: Task > Components: Clustering > Reporter: Ben Wang > Assigned To: Ben Wang > Fix For: EJB 3.0 RC10 - FD > > > This is top level task to track all the tasks related to refactoring and implemntation of current ejb3 sfsb clustering support. Current items include: > 1. Use JBC to handle passivation > 2. Make sure straight JBC works with more test cases > 3. implement fine-grained option -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (EJBTHREE-217) The container should Instruments Hibernate classes

by Bill Burke (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-217?page=all ] Bill Burke updated EJBTHREE-217: -------------------------------- Fix Version/s: (was: EJB 3.0 RC9 - FD) EJB 3.0 RC10 - FD > The container should Instruments Hibernate classes > -------------------------------------------------- > > Key: EJBTHREE-217 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-217 > Project: EJB 3.0 > Issue Type: Feature Request > Components: EJB3 Extensions > Affects Versions: EJB 3.0 Beta 1 > Reporter: Emmanuel Bernard > Assigned To: Bill Burke > Priority: Minor > Fix For: EJB 3.0 RC10 - FD > > > Right now, the user has to instrument Hibernate classes itself through a InstrumentAnt task to enable some features such as property level lazy loading > It'd be cool if the container execute the same job at class load time in an automatic manner. > http://www.hibernate.org/hib_docs/v3/reference/en/html_single/#performanc... -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (EJBTHREE-197) Deploy Hibernate MBean statistics in the EJB 3 Deployer

by Bill Burke (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-197?page=all ] Bill Burke updated EJBTHREE-197: -------------------------------- Fix Version/s: EJB 3.0 RC10 - FD (was: EJB 3.0 RC9 - FD) > Deploy Hibernate MBean statistics in the EJB 3 Deployer > ------------------------------------------------------- > > Key: EJBTHREE-197 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-197 > Project: EJB 3.0 > Issue Type: Feature Request > Reporter: Michael Yuan > Fix For: EJB 3.0 RC10 - FD > > > I discussed this with Emmanuel and Steve over email. They both thought it should be fairly easy to add. The JBoss Network team needs this feature to develop profiling and monitoring tools for EJB 3 (see the linked issue). > Can we have this feature in the JavaOne release of the product? I can demo it in the trail blazer. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Closed: (EJBTHREE-588) Refactor EJB3 MetaModel and create web.xml/jboss-web.xml metamodel

by Bill Burke (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-588?page=all ] Bill Burke closed EJBTHREE-588. ------------------------------- Resolution: Done > Refactor EJB3 MetaModel and create web.xml/jboss-web.xml metamodel > ------------------------------------------------------------------ > > Key: EJBTHREE-588 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-588 > Project: EJB 3.0 > Issue Type: Task > Reporter: Bill Burke > Assigned To: William DeCoste > Priority: Critical > Fix For: EJB 3.0 RC9 - FD > > > * refactor all the shared DD elements between ejb-jar.xml and web.xml into their own reusable metamodel. > * for now, unless Scott changes, put this new metamodel in jboss-head/j2ee under: > org.jboss.metamodel > * Create a metamodel and XML parsing (the jbossxb shit) for web.xml and jboss-web.xml. Put this under the jboss-head/tomcat module under > org.jboss.web.metamodel > If you can think of a better name for these packages, then do that. > *DO NOT USE THE OLD WEB.XML SCHEMA!* > Download the Java EE 5 Servlet specification to obtain the new XML schema for Java EE 5. -- 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, 8 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 September 2006