February 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (EJBTHREE-843) @ManyToOne(cascade=CascadeType.REMOVE) produces delete of the reference of the relation, that is a nonsense

by Christophe Gildas (JIRA)

@ManyToOne(cascade=CascadeType.REMOVE) produces delete of the reference of the relation, that is a nonsense ----------------------------------------------------------------------------------------------------------- Key: EJBTHREE-843 URL: http://jira.jboss.com/jira/browse/EJBTHREE-843 Project: EJB 3.0 Issue Type: Feature Request Affects Versions: EJB 3.0 RC9 - Patch 1, EJB 3.0 RC9 - FD, EJB 3.0 RC8 - FD, EJB 3.0 RC10 - FD, EJB 3.0 RC11 - FD Environment: Windows XP Reporter: Christophe Gildas If I define a relation @ManyToOne(cascade=CascadeType.REMOVE), when an instance of the POJO where is defined this relation is deleted, that produces a attempt to delete the target of the relation, which is the "parent" of the current POJO, that is a nonsense. In this case, like that the "on delete cascade" of Oracle, the expected behaviour would rather be that deleting the target of the relation produces the destruction of all the instances of entities which have a foreign key of this target. If I want to have this behaviour, I must define as much relations @OneToMany(cascade=CascadeType.REMOVE) in a POJO as this POJO has foireign keys That can be very heavy, and a lot less flexible that to define this rule on each foreign key (as Oracle does). -- 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, 2 months

3
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-778) @Remote/@Local interface can be inherited from superclass

by Bill Burke (JIRA)

@Remote/@Local interface can be inherited from superclass --------------------------------------------------------- Key: EJBTHREE-778 URL: http://jira.jboss.com/jira/browse/EJBTHREE-778 Project: EJB 3.0 Issue Type: Feature Request Reporter: Bill Burke class TheSuper implements MyRemote {} @Remote interface MyRemote {} @Stateless class Subclass extends TheSuper {} SubClass stateless bean should be able to inherit remote interface from a superclass that implements @Remote. *NOTE* we need to check the spec to see if this is ok. -- 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, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-731) Allow Clustered BEans to be Tested in the Embedded Container

by John Gilbert (JIRA)

Allow Clustered BEans to be Tested in the Embedded Container ------------------------------------------------------------ Key: EJBTHREE-731 URL: http://jira.jboss.com/jira/browse/EJBTHREE-731 Project: EJB 3.0 Issue Type: Feature Request Components: Clustering Affects Versions: EJB 3.0 RC10 - FD Reporter: John Gilbert -- 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, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-721) persistence unit in embeddable ejb3 doesn't deploy when datasource has leading JNDI path

by Levi Purvis (JIRA)

persistence unit in embeddable ejb3 doesn't deploy when datasource has leading JNDI path ---------------------------------------------------------------------------------------- Key: EJBTHREE-721 URL: http://jira.jboss.com/jira/browse/EJBTHREE-721 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC9 - FD, EJB 3.0 RC10 - FD Environment: jboss-EJB-3.0_Embeddable_ALPHA_9, Eclipse 3.2, Sun JVM 1.5.0_08 Reporter: Levi Purvis Priority: Minor This problem only appears to happen with the embeddable release. A JNDI path such as the following will cause the persistence unit deployment to silently fail with no exception: <jta-data-source>java:/foo/bar/mydatasource</jta-data-source> Whereas this will succeed: <jta-data-source>java:/mydatasource</jta-data-source> -- 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, 2 months

2
1
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-348) Automate test run against all supported databases

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-348?page=all ] Ovidiu Feodorov updated JBMESSAGING-348: ---------------------------------------- Fix Version/s: 1.2.1 (was: 1.2.0.GA) > Automate test run against all supported databases > ------------------------------------------------- > > Key: JBMESSAGING-348 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-348 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Fix For: 1.2.1 > > > The test suite should be run continuously against all databases we supply a configuration for. > Initially this should be: > Oracle, MSSQL, MySQL, PostgreSQL, DB2, Sybase and Derby. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-866) Revert log4j configuration that masks Remoting's [BisocketServerInvoker] got listener: null

by Ovidiu Feodorov (JIRA)

Revert log4j configuration that masks Remoting's [BisocketServerInvoker] got listener: null ------------------------------------------------------------------------------------------- Key: JBMESSAGING-866 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-866 Project: JBoss Messaging Issue Type: Task Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.2.0.GA By this time, Remoting should've gotten rid of that logging statement -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-569) Update clustering design documentation wiki

by Tim Fox (JIRA)

Update clustering design documentation wiki ------------------------------------------- Key: JBMESSAGING-569 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-569 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.0.Beta1 The design doc wiki should be updated to reflect the state of the clustering implementation. Some parts, especially the intelligent balancer are out of date. -- 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, 2 months

3
3
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-26) Standalone Messaging configuration.

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-26?page=all ] Ovidiu Feodorov updated JBMESSAGING-26: --------------------------------------- Fix Version/s: 1.2.1 (was: 1.2.0.GA) Needs to be further discussed. Do we really want to support a standalone configuration? > Standalone Messaging configuration. > ----------------------------------- > > Key: JBMESSAGING-26 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-26 > Project: JBoss Messaging > Issue Type: Task > Components: AS Integration > Reporter: Ovidiu Feodorov > Assigned To: Alex Pinkin > Fix For: 1.2.1 > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Prepare a stripped-down JBoss configuration that will be the "stand-alone" JBoss Messaging server. > Must have at least the JNDI server, Logging, Remoting and AOP support. > We should provide a pre-packaged downloadable "standalone" config - users don't want to have to download and install the AS just so they can create a standalone installation. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-743) Run the whole functional test suite and the stress tests in both clustered and non-clustered configurations

by Ovidiu Feodorov (JIRA)

Run the whole functional test suite and the stress tests in both clustered and non-clustered configurations ----------------------------------------------------------------------------------------------------------- Key: JBMESSAGING-743 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-743 Project: JBoss Messaging Issue Type: Task Components: Tests and Performance Reporter: Ovidiu Feodorov Fix For: 1.2.0.CR1 -- 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, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-4124) Using getDefaultSession istead of getSession in org/jboss/resource/adapter/mail/inflow/MailFolder.java

by Ilya (JIRA)

Using getDefaultSession istead of getSession in org/jboss/resource/adapter/mail/inflow/MailFolder.java ------------------------------------------------------------------------------------------------------ Key: JBAS-4124 URL: http://jira.jboss.com/jira/browse/JBAS-4124 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JCA service Affects Versions: JBossAS-4.0.5.GA Environment: Linux Reporter: Ilya Assigned To: Weston Price Priority: Critical I'm using MDB of type org.jboss.resource.adapter.mail.inflow.MailListener it was working incorrectly. Sometimes, out of blue, it stopped fetching mail with exception (which I could see after fix from JBAS-3769): 2007-02-02 11:51:52,220 ERROR [MailActivation] Failed to execute folder check, spec=MailActivationSpec(mailServer=10.0.0.1, storeProtocol=imap, mailFolder=INBOX, pollingInterval=60000, messageSelector=null, userName=***, maxMessages=1) javax.mail.NoSuchProviderException: Invalid protocol: null at javax.mail.Session.getProvider(Session.java:412) at javax.mail.Session.getStore(Session.java:511) at javax.mail.Session.getStore(Session.java:491) at javax.mail.Session.getStore(Session.java:477) at org.jboss.resource.adapter.mail.inflow.MailFolder.open(MailFolder.java:69) at org.jboss.resource.adapter.mail.inflow.MailActivation.run(MailActivation.java:121) at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:204) at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:275) at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:743) at java.lang.Thread.run(Thread.java:595) problem was fixed, when I applyed this patch: Index: src/main/org/jboss/resource/adapter/mail/inflow/MailFolder.java =================================================================== --- src/main/org/jboss/resource/adapter/mail/inflow/MailFolder.java (revision 60713) +++ src/main/org/jboss/resource/adapter/mail/inflow/MailFolder.java (working copy) @@ -64,7 +64,8 @@ throws Exception { // Get a session object - session = Session.getDefaultInstance(sessionProps); + session = Session.getInstance(sessionProps); + // Get a store object store = session.getStore(); store.connect(mailServer, userName, password); I believe that using getDefaultSession() was incorrect, because we don't need _defaul_ we need _our_ session =) Please plan this to be fixed. -- 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, 2 months

3
4
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 February 2007