May 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (EJBTHREE-950) Incorrect signatures for EJB3 APIs

by Shelly McGowan (JIRA)

Incorrect signatures for EJB3 APIs ----------------------------------- Key: EJBTHREE-950 URL: http://jira.jboss.com/jira/browse/EJBTHREE-950 Project: EJB 3.0 Issue Type: Bug Affects Versions: AS 4.2.0 CR2 Reporter: Shelly McGowan The following differences were detected in the JBoss EJB3 API signatures in Branch_4_2 and trunk (5.0.0) according to the EJB3 API Javadoc located at: http://java.sun.com/javaee/5/docs/api/ javax.ejb.ActivationConfigProperty: No Target or Retention Policy defined Defined as: class abstract public interface !annotation javax.ejb.ActivationConfigProperty Should be defined: javax.ejb.ActivationConfigProperty: class abstract public interface !annotation javax.ejb.ActivationConfigProperty anno 0 java.lang.annotation.Retention(java.lang.annotation.RetentionPolicy value=RUNTIME) anno 0 java.lang.annotation.Target(java.lang.annotation.ElementType[] value=[]) ---------------------- javax.ejb.EJB: Target value includes PARAMETER anno 0 java.lang.annotation.Target(java.lang.annotation.ElementType[] value=[METHOD, TYPE, FIELD, PARAMETER]) should only be: anno 0 java.lang.annotation.Target(java.lang.annotation.ElementType[] value=[TYPE, METHOD, FIELD]) ---------------------- javax.ejb.Init: Defined as: method abstract public !hasdefault java.lang.String[] value() Should be: method abstract public !hasdefault java.lang.String value() -------------------------- javax.ejb.AccessMode This is obsolete and should be removed. ------------------------------------------ javax.ejb.SessionContext: Defined as: public Object getBusinessObject(Class businessInterface) throws IllegalStateException; Should be defined: <T> T getBusinessObject(Class<T> businessInterface) throws IllegalStateException; ------------------------------------------ javax.ejb.EJBAccessException: Constructors for EJBAccessException should be: public EJBAccessException() public EJBAccessException(String message) JBoss implementation has an additional constructor: public javax.ejb.EJBAccessException(String message, Exception ex) ------------------------------------------ javax.ejb.EJBTransactionRolledbackException: Constructors for EJBTransactionRolledbackException should be: public EJBTransactionRolledbackException() public EJBTransactionRolledbackException(String message) public EJBTransactionRolledbackException(String message, Exception ex) The JBoss implementation has an additional constructor: public EJBTransactionRolledbackException(Exception ex) ---------------------------------------------------- -- 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, 7 months

3
4
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-520) Messages received from Receiver.receive() using an XA are never deleted from the database if not withing a transactional boundary.

by Joel Lindheimer (JIRA)

Messages received from Receiver.receive() using an XA are never deleted from the database if not withing a transactional boundary. ---------------------------------------------------------------------------------------------------------------------------------- Key: JBMESSAGING-520 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-520 Project: JBoss Messaging Issue Type: Feature Request Components: Messaging Core Affects Versions: 1.0.1.CR4 Environment: Windows XP, JBossServer4.0.4GA, Oracle10G Reporter: Joel Lindheimer Assigned To: Ovidiu Feodorov Create a simple receiver, but do not place it within a Transaction boundary; shut down the server; look up the tables and you will see all the messages are still in the Messages and MessageRef tables. ========================================= Observations using a debbuger reveal the following: ========================================= Looking over the org.jboss.resource.adapter.jms.JmsManagedConnection the setup method will always call createXAQueueSession() and create an XAQueconnection as transacted and Session.SESSION_TRANSACTED. That being the case, non-XA Queues have no message-deletion problems with the current version (RC4) because the API removes all messages that are "not transacted and (!ack==1). I am guessing that using XA is problematic because the persistence layer is expecting manipulation of the transacted XASession--which for some reason is not working in this version of Messaging. More specifically, I suspect that when MDBs are tested you are not seeing this problem because the container is doing needed magic to manage the XASession transacted state, and therefore everything works fine therein. And consequently, when operating as a non-MDB client, AKA a simple Receiver, there is something missing in the equation ergo the problems that I have been reporting regarding the ClickCommerce applications which use Receivers and not MDBs. Work-around: None; the strategy for my team is to NOT use an XAQueueConnection while waiting for a fix. -- 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, 7 months

5
11
0 / 0

[JBoss JIRA] Updated: (JBCACHE-60) Partitioned Cache

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-60?page=all ] Manik Surtani updated JBCACHE-60: --------------------------------- Fix Version/s: 2.2.0.GA (was: 2.3.0.GA) > Partitioned Cache > ----------------- > > Key: JBCACHE-60 > URL: http://jira.jboss.com/jira/browse/JBCACHE-60 > Project: JBoss Cache > Issue Type: Feature Request > Reporter: Bela Ban > Assigned To: Manik Surtani > Fix For: 2.2.0.GA > > Original Estimate: 10 weeks > Remaining Estimate: 10 weeks > > - Distributed load across multiple nodes in a cluster > - No replication/redundancy -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCACHE-11) Memory based eviction policy

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-11?page=all ] Manik Surtani updated JBCACHE-11: --------------------------------- Fix Version/s: 2.1.0.GA (was: 2.2.0.GA) > Memory based eviction policy > ---------------------------- > > Key: JBCACHE-11 > URL: http://jira.jboss.com/jira/browse/JBCACHE-11 > Project: JBoss Cache > Issue Type: Feature Request > Components: Eviction > Reporter: Bela Ban > Assigned To: Mircea Markus > Fix For: 2.1.0.GA > > Original Estimate: 2 weeks > Remaining Estimate: 2 weeks > > (maybe only in JDK 1.5, which has > triggers for low memory) -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1363) java.lang.NullPointerException for Users Role after deleting demo Test page

by William Byrne (JIRA)

java.lang.NullPointerException for Users Role after deleting demo Test page --------------------------------------------------------------------------- Key: JBPORTAL-1363 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1363 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal CMS Affects Versions: 2.6.CR1 Environment: Win XP SP2, PostgreSQL 8.2, postgresql-8.2-505.jdbc3.jar, jboss-portal-2.6-CR1-bundled.zip Reporter: William Byrne Assigned To: Sohil Shah Both PGSQL and JBossPortal are clean installations. Problem exhibited with both PGSQL 8.1 and 8.2. Problem does NOT show up with HSQLDB script.. 1) Clean install of PGSQL DB 2) Clean install of JBossPortal bundle configured for PGSQL using "portal-postgresql-ds.xml" 3) Run portal 4) Login as admin 5) Delete Test page under default portal 6) Logout 7) Login as user java.lang.NullPointerException shown in center portal region. Will attach complete log file. Refer to: 2007-04-28 04:02:49,339 ERROR [STDERR] java.lang.NullPointerException -- 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, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-950) Unacked messages on recovery with JCA adaptor

by Tim Fox (JIRA)

Unacked messages on recovery with JCA adaptor --------------------------------------------- Key: JBMESSAGING-950 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-950 Project: JBoss Messaging Issue Type: Bug Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.0.SP2, 1.0.1.SP5 -- 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, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-4387) testRetryWithJnpAndAustoDiscovery accessing localhost

by Richard Achmatowicz (JIRA)

testRetryWithJnpAndAustoDiscovery accessing localhost ----------------------------------------------------- Key: JBAS-4387 URL: http://jira.jboss.com/jira/browse/JBAS-4387 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.2.0.GA Environment: all Windows 2003 platforms Reporter: Richard Achmatowicz The test cases org.jboss.test.testbeancluster.test.RetryInterceptorUnitTestCase (Default-TCP) org.jboss.test.testbeancluster.test.RetryInterceptorUnitTestCase (Default-UDP) org.jboss.test.testbeancluster.test.SingleRetryInterceptorUnitTestCase (Default-TCP) org.jboss.test.testbeancluster.test.SingleRetryInterceptorUnitTestCase (Default-UDP) are failing on the test testRetryWithJnpAndAustoDiscovery with a common error: See the linked issue for details and comments. -- 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, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-4375) Upgrade Javassist to v3.5.0.GA

by Dimitris Andreadis (JIRA)

Upgrade Javassist to v3.5.0.GA ------------------------------ Key: JBAS-4375 URL: http://jira.jboss.com/jira/browse/JBAS-4375 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Other Affects Versions: JBossAS-4.2.0.CR2 Reporter: Dimitris Andreadis Fix For: JBossAS-4.2.0.GA -- 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, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (SECURITY-44) Security Client SPI

by Anil Saldhana (JIRA)

Security Client SPI ------------------- Key: SECURITY-44 URL: http://jira.jboss.com/jira/browse/SECURITY-44 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: Security SPI Affects Versions: 2.0.0.BETA Reporter: Anil Saldhana Assigned To: Anil Saldhana Priority: Critical Fix For: 2.0.GA There is a need for a Security Client SPI that is going to move the client applications away from the dependence on JAAS and/or SecurityAssociation. There is a need to come up with a Security Client SPI (that can do JAAS, JGSS and/or SASL). Need to get this SPI in before we do the Security 2.0.0.GA release. -- 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, 7 months

1
2
0 / 0

[JBoss JIRA] Commented: (JBAS-1536) Wrong SQL Type for Boolean Mapping for Derby Database

by Tomas Gustavsson (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1536?page=comments#action_12361151 ] Tomas Gustavsson commented on JBAS-1536: ---------------------------------------- a SMALLINT seems to work for me. I found it by googling. I have tested by adding the following to my jbosscmp-jdbc.xml. ----- <cmp-field> <field-name>markedAsRecoverable</field-name> <jdbc-type>BIT</jdbc-type> <sql-type>SMALLINT</sql-type> </cmp-field> ----- Cheers, Tomas www.ejbca.org > Wrong SQL Type for Boolean Mapping for Derby Database > ----------------------------------------------------- > > Key: JBAS-1536 > URL: http://jira.jboss.com/jira/browse/JBAS-1536 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: CMP service > Affects Versions: JBossAS-4.0.1 Final > Environment: JBoss4.0.1; JDK1.5.0update1;Windows XP SP2;Derby 10.0.2.1 Embedded > Reporter: Ingo Bruell > Fix For: JBossAS-4.2.1.CR1 > > > The SQL datatype 'BOOLEAN' is not a valid datatype for the derby database. -- 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, 7 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 May 2007