November 2007 - jboss-jira - Jboss List Archives

[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

[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

17 years

3
9
0 / 0

[JBoss JIRA] Created: (JBCACHE-931) Move to JBossAOP rather than hand-wiring interceptor chain for JBoss Cache

by Manik Surtani (JIRA)

Move to JBossAOP rather than hand-wiring interceptor chain for JBoss Cache -------------------------------------------------------------------------- Key: JBCACHE-931 URL: http://jira.jboss.com/jira/browse/JBCACHE-931 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.0.0.GA Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.1.0.GA This should be a seamless change for end-users, and backward compat should be maintained. -- 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: (JBCACHE-1219) Refactor logic implementation of interceptors

by Manik Surtani (JIRA)

Refactor logic implementation of interceptors --------------------------------------------- Key: JBCACHE-1219 URL: http://jira.jboss.com/jira/browse/JBCACHE-1219 Project: JBoss Cache Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Manik Surtani Assigned To: Mircea Markus Fix For: 2.2.0.GA The current interceptor implementations are pretty messy, unreadable and hard to maintain, with lots of switches and casts from an args array. The goal of this task is to create a SwitchedInterceptor, an abstract class that extends Interceptor, which would perform a switch() and call no-op handlers which can be overridden by subclasses such as the PessimisticLockInterceptor, etc. The benefit is that the implementation interceptors are easier to follow through, read and refactor. Another benefit is that the switched interceptor can take care of extracting method call parameters and pass them to the handlers - making them typed. -- 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
2
0 / 0

[JBoss JIRA] Created: (JBRULES-1339) Debugging: Breakpoints are only considered for code with variables

by Michael Zimmermann (JIRA)

Debugging: Breakpoints are only considered for code with variables ------------------------------------------------------------------ Key: JBRULES-1339 URL: http://jira.jboss.com/jira/browse/JBRULES-1339 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: Eclipse IDE Affects Versions: 4.0.3 Environment: Linux (Kubunut 7.10), Current Eclipse 3.2.x, Drools 4.0.3 Reporter: Michael Zimmermann In my installation breakpoints in drl files are only recognized if there is any variable involved. Here is a small example 1) Works ok, while debugging the application stops at the breakpoint in System.out.println() rule "TestRule" when eval (1==1) then int i = 1; System.out.println("Breakpoint ok" +i); end 2) The breakpoint in System.out.println() is ignored. The rule fires nevertheless.... rule "TestRule" when eval (1==1) then int i = 1; System.out.println("Breakpoint ignored"); end Tested via the Debug > As > Drools -- 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
2
0 / 0

[JBoss JIRA] Created: (JBREM-752) SSLSocket runs into BindException

by Claudia Richter (JIRA)

SSLSocket runs into BindException --------------------------------- Key: JBREM-752 URL: http://jira.jboss.com/jira/browse/JBREM-752 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Components: transport Affects Versions: 2.2.0.SP4, 2.2.0.SP3, 2.2.0.SP2, 2.2.0.SP1, 2.2.0.GA (Bluto), 2.2.0.Beta1 (Bluto) Reporter: Claudia Richter during a Socket refresh in the SocketServerInvoker Class (Method refreshServerSocket() ) sometimes a BindException occures. The reason is that reuseAddress is set after the ServerSocket is bound. It is necessary to first create an unbound ServerSocket, then set reuseAddress and then bind the ServerSocket. -- 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
5
0 / 0

[JBoss JIRA] Created: (JBREM-846) Fix race in JNIDDetector

by Ron Sigal (JIRA)

Fix race in JNIDDetector ------------------------ Key: JBREM-846 URL: http://jira.jboss.com/jira/browse/JBREM-846 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.2.2.SP2, 2.2.2.GA_CP01, 2.4.0.Beta1 (Pinto) Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 2.4.0.Beta1 (Pinto) When the org.jboss.remoting.detection.jndi.JNDIDetector heartbeat thread does a clean detect and discovers that a server is unreachable, it calls checkInvokerServer(), which, among other things, tells its org.jboss.remoting.network.NetworkRegistry to inform listeners of the loss of a server. It then calls org.jboss.remoting.detection.AbstractDetector.detect(), passing the org.jboss.remoting.detection.Detection representing the server that is no longer available. However, detect() treats the Detection as a *new* server, and it tells its org.jboss.remoting.network.NetworkRegistry to inform listeners of a new server. This problem was turned up by the occasional failure of org.jboss.test.remoting.detection.jndi.RestartTestCase. The test fails inconsistently because NetworkRegistry sends its notifications in separate threads, and RestartTestCase is expecting to hear that (1) the old server has died, and (2) a new server has replaced it. If the notifications are received in order, than the test passes, and if they are received out of order it fails. The solution is simply to not call AbstractInvoker.detect() when a server has died. -- 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
2
0 / 0

[JBoss JIRA] Created: (JBREM-745) client unable to send if server recycles

by John Mazzitelli (JIRA)

client unable to send if server recycles ---------------------------------------- Key: JBREM-745 URL: http://jira.jboss.com/jira/browse/JBREM-745 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.2.0.SP4 Reporter: John Mazzitelli Assigned To: Ron Sigal I have TestNG unit test that fails about 75% of the time. See attached. The issue here is that if a server shuts down and then restarts, the client will fail to be able to send a message to it. Replication works like this: 1. create and start a connector 2. create and connect a client 3. send a message to the server and see that it works (which creates a ServerThread worker thread on server side) 4. stop connector and the re-start it 5. send a message to the server and see that it FAILS due to: org.jboss.remoting.ServerInvoker$InvalidStateException: Can not process invocation request since is not in started state. at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:745) at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:560) at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:383) at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:165) at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:163) at org.jboss.remoting.Client.invoke(Client.java:1550) at org.jboss.remoting.Client.invoke(Client.java:530) at org.jboss.remoting.Client.invoke(Client.java:518) -- 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
5
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2007