March 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBPORTAL-860) Update DTDs to reflect changes in descriptors.

by Julien Viet (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-860?page=all ] Julien Viet updated JBPORTAL-860: --------------------------------- Fix Version/s: 2.6.CR1 (was: 2.6.Beta1) > Update DTDs to reflect changes in descriptors. > ---------------------------------------------- > > Key: JBPORTAL-860 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-860 > Project: JBoss Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Portal Core > Affects Versions: 2.4 Final > Reporter: Chris Laprun > Fix For: 2.6.CR1 > > Original Estimate: 1 week > Remaining Estimate: 1 week > > Update and document changes. Should we move to XSD since some of the DTD elements don't seem to reflect the internal structure of descriptors. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-841) add a business key

by Tom Baeyens (JIRA)

add a business key ------------------ Key: JBPM-841 URL: http://jira.jboss.com/jira/browse/JBPM-841 Project: JBoss jBPM Issue Type: Feature Request Components: Core Engine Reporter: Tom Baeyens Assigned To: Tom Baeyens Fix For: jBPM jPDL 3.2 add a string based business key property on the process instance. combination of business key + process defintion must be unique if a business key is supplied. -- 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, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-710) Improve perf by optimizing/caching class field inspectors

by Edson Tirelli (JIRA)

Improve perf by optimizing/caching class field inspectors --------------------------------------------------------- Key: JBRULES-710 URL: http://jira.jboss.com/jira/browse/JBRULES-710 Project: JBoss Rules Issue Type: Task Security Level: Public (Everyone can see) Components: Reteoo Reporter: Edson Tirelli Assigned To: Edson Tirelli Fix For: 3.1-m2 ClassFieldInspector instances are created all the time in core and not reused. Optimize code reusing 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, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-3414) Port EJBDeployer

by Scott M Stark (JIRA)

Port EJBDeployer ---------------- Key: JBAS-3414 URL: http://jira.jboss.com/jira/browse/JBAS-3414 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Deployment services, EJB2 Reporter: Scott M Stark Assigned To: Dimitris Andreadis Fix For: JBossAS-5.0.0.Beta The EJBDeployer needs to be ported to the new VDF and interaction with the EJB3 deployer defined -- 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, 1 month

3
5
0 / 0

And the winner is ... Ud. por supuesto!!

by Hostex

17 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (EJBTHREE-891) Interceptors aren't called for MDBs

by Peter Muir (JIRA)

Interceptors aren't called for MDBs ----------------------------------- Key: EJBTHREE-891 URL: http://jira.jboss.com/jira/browse/EJBTHREE-891 Project: EJB 3.0 Issue Type: Bug Environment: JBoss 4.0.5.GA Reporter: Peter Muir Using @MessageDriven(activationConfig={ ... }) @ResourceAdapter("mail-ra.rar") @Interceptors(MySpecialInterceptor.class) public class MailListenerMDB implements MailListener { public void onMessage(Message message) { } } the @AroundInvoke method on MySpecialInterceptor is not called when a message is delivered using onMessage. -- 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, 1 month

5
8
0 / 0

[JBoss JIRA] Assigned: (EJBTHREE-485) Better toString method on the EJB proxy

by Carlo de Wolf (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-485?page=all ] Carlo de Wolf reassigned EJBTHREE-485: -------------------------------------- Assignee: Carlo de Wolf > Better toString method on the EJB proxy > --------------------------------------- > > Key: EJBTHREE-485 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-485 > Project: EJB 3.0 > Issue Type: Feature Request > Environment: n/a > Reporter: Andrew > Assigned To: Carlo de Wolf > Priority: Minor > Fix For: EJB 3.0 RC11 - FD > > Time Spent: 2 hours > > The EJB instance toString method returns "$Proxy###" instead of a class name. It would be nice to know what interface the proxy implements. So if I have a "MySessionBean" with interface "MySession", it would be nice to know when printing the object that the object implements MySession. > This is especially relavent when using JBoss Seam. When there are annotation problems and the EJB interface, it prints out the cryptic proxy name that does not let the developer determine which been has the problem. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (EJBTHREE-485) Better toString method on the EJB proxy

by Carlo de Wolf (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-485?page=all ] Carlo de Wolf updated EJBTHREE-485: ----------------------------------- Fix Version/s: EJB 3.0 RC11 - FD > Better toString method on the EJB proxy > --------------------------------------- > > Key: EJBTHREE-485 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-485 > Project: EJB 3.0 > Issue Type: Feature Request > Environment: n/a > Reporter: Andrew > Priority: Minor > Fix For: EJB 3.0 RC11 - FD > > Time Spent: 2 hours > > The EJB instance toString method returns "$Proxy###" instead of a class name. It would be nice to know what interface the proxy implements. So if I have a "MySessionBean" with interface "MySession", it would be nice to know when printing the object that the object implements MySession. > This is especially relavent when using JBoss Seam. When there are annotation problems and the EJB interface, it prints out the cryptic proxy name that does not let the developer determine which been has the problem. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (EJBTHREE-864) Patch for EJBTHREE-719, but not all required extensions, only, jar, zip, jar:file, zip:file

by Norbert Kenderesi (JIRA)

Patch for EJBTHREE-719, but not all required extensions, only, jar, zip, jar:file, zip:file ------------------------------------------------------------------------------------------- Key: EJBTHREE-864 URL: http://jira.jboss.com/jira/browse/EJBTHREE-864 Project: EJB 3.0 Issue Type: Patch Affects Versions: EJB 3.0 RC9 - Patch 1 Reporter: Norbert Kenderesi With this patch the following exception won't come in case of protocols: jar, zip, jar:file, zip:file and file of course. This is tested on weblogic 9.2 where the workaround doesn't work Caused by: java.lang.RuntimeException: NOT IMPLEMENTED at org.jboss.util.file.ArchiveBrowser.getBrowser(ArchiveBrowser.java:42) at org.hibernate.ejb.Ejb3Configuration.scanForClasses(Ejb3Configuration.java:541) ... 148 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

17 years, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-710) Cleanup E-EJB3 package/code/logging

by Christian Bauer (JIRA)

Cleanup E-EJB3 package/code/logging ----------------------------------- Key: EJBTHREE-710 URL: http://jira.jboss.com/jira/browse/EJBTHREE-710 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC9 - FD Reporter: Christian Bauer Priority: Blocker This is E-EJB3 RC9. The following issues are not minor, they would make me feel uneasy if I was a user: 1. The bundled embedded-jboss-beans.xml uses xmlns="urn:jboss:bean-deployer" and everybody gets a nice WARN on startup that xmlns="urn:jboss:bean-deployer:2.0" should be used. Change that in the distributed configuration file. 2. [java] 13:40:10,676 WARN Ejb3Configuration:104 - Persistence provider caller does not implements the EJB3 spec correctly. PersistenceUnitInfo.getNewTempClassLoader() is null. It's OK to warn users that something is not right, but if something is not right in our distribution there should be a note in the README or something that tells me as a user that this is OK for the moment. Like a link to a JIRA issue. 3. [java] 13:44:59,381 WARN JBossTimerServiceFactory:112 - TIMER SERVICE IS NOT INSTALLED -- Uh, yes, because I don't want it. Find a way for users to disable this warning. I don't see any way to disable the timer service in embedded-jboss-beans.xml and I don't want the .rar and .jar in my libs. 4. In RC9 there is code that prints debugging stuff on STDOUT: [java] lookup [java] UserTransaction: org.jboss.ejb3.embedded.UserTransactionImpl [java] MessageHandlerBean: org.jnp.interfaces.NamingContext This is triggered by EJB3StandaloneBootstrap.scanClasspath("helloworld-ejb3/build"), please remove from code... -- 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, 1 month

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2007