January 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBAS-8798) mail-ra: getMessages() on imap folder doesn't work as expected

by Mark Zeller (JIRA)

[ https://issues.jboss.org/browse/JBAS-8798?page=com.atlassian.jira.plugin.... ] Mark Zeller updated JBAS-8798: ------------------------------ Attachment: mail-ra.patch Patch attached to fix the issue. > mail-ra: getMessages() on imap folder doesn't work as expected > -------------------------------------------------------------- > > Key: JBAS-8798 > URL: https://issues.jboss.org/browse/JBAS-8798 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: JBossAS-5.1.0.GA, 6.0.0.Final > Reporter: Mark Zeller > Priority: Minor > Labels: mail-ra > Attachments: mail-ra.patch > > > The getMessages()-method should return only new (not Flag.SEEN) messages. This does not work if the not unseen messages are not the first messages in the folder. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-8633) Flatten the deployment unit processor chain

by David Lloyd (JIRA)

Flatten the deployment unit processor chain ------------------------------------------- Key: JBAS-8633 URL: https://jira.jboss.org/browse/JBAS-8633 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Deployers Reporter: David Lloyd Priority: Blocker Fix For: 7.0.0.Alpha2 Right now we are using a separate processor chain for each deployment unit "type". However many processors apply to multiple or all types of deployments. We should move to a single deployment chain where each processor makes its own decision as to whether it should apply to the current deployment. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-8615) There needs to be a way to cleanup after deployment processors in case a deployment failed

by Alexey Loubyansky (JIRA)

There needs to be a way to cleanup after deployment processors in case a deployment failed ------------------------------------------------------------------------------------------ Key: JBAS-8615 URL: https://jira.jboss.org/browse/JBAS-8615 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: 7.0.0.Alpha2 An example is module unloading. Normally it happens when the deployment unit is undeployed by notifying the listeners. But in case the deployment unit failed to start and the listeners can't be invoked there needs to be a way to clean-up such things. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-8617) Unload module for failed deployment

by Alexey Loubyansky (JIRA)

Unload module for failed deployment ----------------------------------- Key: JBAS-8617 URL: https://jira.jboss.org/browse/JBAS-8617 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 7.0.0.Alpha1 Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: 7.0.0.Alpha2 In ModuleDeploymentProcessor the module spec is added to the loader and the module is loaded. But if later the deployment fails before the clean-up listeners are installed the module will not be unloaded which will prevent subsequent re-deploy. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBJPA-35) Hibernate logs warning for PersistenceUnitInfo.newTempClassLoader() == null, which it always is in EJB3

by Brad Maxwell (JIRA)

Hibernate logs warning for PersistenceUnitInfo.newTempClassLoader() == null, which it always is in EJB3 ------------------------------------------------------------------------------------------------------- Key: JBJPA-35 URL: https://issues.jboss.org/browse/JBJPA-35 Project: JBoss JPA Issue Type: Bug Components: mcint Affects Versions: 1.0.0 Environment: JBoss Enterprise Application Platform 5.0.1 Reporter: Brad Maxwell Assignee: Brad Maxwell Fix For: 1.0.1 Looks like https://jira.jboss.org/browse/EJBTHREE-982 did not make it into JBoss 5 WARN [Ejb3Configuration] Persistence provider caller does not implements the EJB3 spec correctly. PersistenceUnitInfo.getN ewTempClassLoader() is null. Coming from org.hibernate.ejb.Ejb3Configuration private void addXMLEntities(List<String> xmlFiles, PersistenceUnitInfo info, List<String> entities) { //TODO handle inputstream related hbm files ClassLoader newTempClassLoader = info.getNewTempClassLoader(); if (newTempClassLoader == null) { log.warn( "Persistence provider caller does not implements the EJB3 spec correctly. PersistenceUnitInfo.getNewTempClassLoader() is null." ); return; } However, implementation of org.jboss.ejb3.entity.PersistenceUnitInfoImpl has: public ClassLoader getNewTempClassLoader() { return null; } -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (LOGMGR-27) AsyncHandler spawns many threads instead of just one

by David Lloyd (JIRA)

AsyncHandler spawns many threads instead of just one ---------------------------------------------------- Key: LOGMGR-27 URL: https://issues.jboss.org/browse/LOGMGR-27 Project: JBoss Log Manager Issue Type: Bug Security Level: Public (Everyone can see) Reporter: David Lloyd Assignee: David Lloyd -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (LOGMGR-27) AsyncHandler spawns many threads instead of just one

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-27?page=com.atlassian.jira.plugin.... ] David Lloyd updated LOGMGR-27: ------------------------------ Fix Version/s: 1.2.0.CR10 > AsyncHandler spawns many threads instead of just one > ---------------------------------------------------- > > Key: LOGMGR-27 > URL: https://issues.jboss.org/browse/LOGMGR-27 > Project: JBoss Log Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: 1.2.0.CR10 > > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] Resolved: (LOGMGR-27) AsyncHandler spawns many threads instead of just one

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-27?page=com.atlassian.jira.plugin.... ] David Lloyd resolved LOGMGR-27. ------------------------------- Resolution: Done > AsyncHandler spawns many threads instead of just one > ---------------------------------------------------- > > Key: LOGMGR-27 > URL: https://issues.jboss.org/browse/LOGMGR-27 > Project: JBoss Log Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: David Lloyd > Assignee: David Lloyd > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2488) Please coordinate OpenSSO artifacts with SOA team.

by Rick Wagner (JIRA)

Please coordinate OpenSSO artifacts with SOA team. -------------------------------------------------- Key: JBPORTAL-2488 URL: https://issues.jboss.org/browse/JBPORTAL-2488 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal Identity Affects Versions: 2.7.2 Final Environment: All Portal Reporter: Rick Wagner Priority: Minor Customers attempting to integrate SOA-P, Portal and OpenSSO have encountered difficulty in using our packaged examples. Currently, Portal has a newer version of OpenSSO (8.0 Update 1). Please do not change this without coordinating with the SOA-P team. See related JIRA SOA-2760. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBBUILD-512) Create a maven plugin that can pull a pom from the repository and compare versions

by Paul Gier (JIRA)

Create a maven plugin that can pull a pom from the repository and compare versions ---------------------------------------------------------------------------------- Key: JBBUILD-512 URL: https://jira.jboss.org/jira/browse/JBBUILD-512 Project: JBoss Build System Issue Type: Feature Request Components: Maven Reporter: Paul Gier Fix For: Maven Build - Maint 2009 Dimitris suggested that it would be useful to have a maven plugin that can read a pom from a given URL (or maybe from the maven repo). The plugin would then compare the dependencies listed in this pom to the dependency versions of the current project. It would then report on the results showing where the versions conflict. Note: Possibly this could be added as a feature to the maven dependency plugin. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2011