March 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-7799) DeploymentManager fails to specify a context when unable to determine the module type

by Carlo de Wolf (JIRA)

DeploymentManager fails to specify a context when unable to determine the module type ------------------------------------------------------------------------------------- Key: JBAS-7799 URL: https://jira.jboss.org/jira/browse/JBAS-7799 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Carlo de Wolf Assignee: Carlo de Wolf Priority: Minor Fix For: JBossAS-6.0.0.M3 java.lang.RuntimeException: cannot obtain module type at org.jboss.deployment.spi.DeploymentManagerImpl.createDeployment(DeploymentManagerImpl.java:533) -- 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

16 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-7794) Integrate Remoting into AS

by David Lloyd (JIRA)

Integrate Remoting into AS -------------------------- Key: JBAS-7794 URL: https://jira.jboss.org/jira/browse/JBAS-7794 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: David Lloyd Assignee: David Lloyd Fix For: JBossAS-6.0.0.M3 Name it jboss-remoting-3.jar so that it doesn't conflict with R2 during the migration -- 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

16 years, 4 months

1
3
0 / 0

[JBoss JIRA] Created: (JBAS-7795) Integrate Remoting Metadata

by David Lloyd (JIRA)

Integrate Remoting Metadata --------------------------- Key: JBAS-7795 URL: https://jira.jboss.org/jira/browse/JBAS-7795 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: David Lloyd Assignee: David Lloyd Fix For: JBossAS-6.0.0.M3 jboss-remoting.xml descriptor tags and deployer. -- 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

16 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-7796) Integrate jboss-marshalling

by David Lloyd (JIRA)

Integrate jboss-marshalling --------------------------- Key: JBAS-7796 URL: https://jira.jboss.org/jira/browse/JBAS-7796 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: David Lloyd Assignee: David Lloyd Fix For: JBossAS-6.0.0.M3 Include API and River JARs into common/lib for now -- 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

16 years, 4 months

1
1
0 / 0

[JBoss JIRA] Updated: (JBAS-3131) Extension-List MANIFEST attribute not honored during deployment of an EAR

by Jason T. Greene (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-3131?page=com.atlassian.jira.plug... ] Jason T. Greene updated JBAS-3131: ---------------------------------- Fix Version/s: JBossAS-6.0.0.M4 (was: JBossAS-6.0.0.M3) > Extension-List MANIFEST attribute not honored during deployment of an EAR > ------------------------------------------------------------------------- > > Key: JBAS-3131 > URL: https://jira.jboss.org/jira/browse/JBAS-3131 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Deployers > Affects Versions: JBossAS-4.0.3 SP1 > Environment: Windows XP SP2, JDK 1.5.0_06 > Reporter: Alexander Sack > Priority: Minor > Fix For: JBossAS-6.0.0.M4 > > > If a JAR within an EAR specifies an Extension-List MANIFEST attribute, the EAR deployer does not honor it. I have a library, my.jar, that gets deployed that specifies an Extension-Name and Implementation-Version. If any of my jars within an EAR references this library, JBoss ignores the Extension-List attribute. The use of the Extension-List MANIFEST attribute is part of the core J2EE 1.4 spec and the EAR deployment should fail if the Extension-List library is not found (or if it is found and the <name>-Implementatino-Version does not meet the minimal requirements. -- 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

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-3131) Extension-List MANIFEST attribute not honored during deployment of an EAR

by Jason T. Greene (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-3131?page=com.atlassian.jira.plug... ] Jason T. Greene updated JBAS-3131: ---------------------------------- Priority: Major (was: Minor) Increasing priority > Extension-List MANIFEST attribute not honored during deployment of an EAR > ------------------------------------------------------------------------- > > Key: JBAS-3131 > URL: https://jira.jboss.org/jira/browse/JBAS-3131 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Deployers > Affects Versions: JBossAS-4.0.3 SP1 > Environment: Windows XP SP2, JDK 1.5.0_06 > Reporter: Alexander Sack > Fix For: JBossAS-6.0.0.M4 > > > If a JAR within an EAR specifies an Extension-List MANIFEST attribute, the EAR deployer does not honor it. I have a library, my.jar, that gets deployed that specifies an Extension-Name and Implementation-Version. If any of my jars within an EAR references this library, JBoss ignores the Extension-List attribute. The use of the Extension-List MANIFEST attribute is part of the core J2EE 1.4 spec and the EAR deployment should fail if the Extension-List library is not found (or if it is found and the <name>-Implementatino-Version does not meet the minimal requirements. -- 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

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBAS-3131) Extension-List MANIFEST attribute not honored during deployment of an EAR

by Jason T. Greene (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-3131?page=com.atlassian.jira.plug... ] Jason T. Greene reassigned JBAS-3131: ------------------------------------- Assignee: Jason T. Greene > Extension-List MANIFEST attribute not honored during deployment of an EAR > ------------------------------------------------------------------------- > > Key: JBAS-3131 > URL: https://jira.jboss.org/jira/browse/JBAS-3131 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Deployers > Affects Versions: JBossAS-4.0.3 SP1 > Environment: Windows XP SP2, JDK 1.5.0_06 > Reporter: Alexander Sack > Assignee: Jason T. Greene > Fix For: JBossAS-6.0.0.M4 > > > If a JAR within an EAR specifies an Extension-List MANIFEST attribute, the EAR deployer does not honor it. I have a library, my.jar, that gets deployed that specifies an Extension-Name and Implementation-Version. If any of my jars within an EAR references this library, JBoss ignores the Extension-List attribute. The use of the Extension-List MANIFEST attribute is part of the core J2EE 1.4 spec and the EAR deployment should fail if the Extension-List library is not found (or if it is found and the <name>-Implementatino-Version does not meet the minimal requirements. -- 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

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMETA-270) EE 6 module name concept in war metadata

by Brian Stansberry (JIRA)

EE 6 module name concept in war metadata ---------------------------------------- Key: JBMETA-270 URL: https://jira.jboss.org/jira/browse/JBMETA-270 Project: JBoss Metadata Issue Type: Sub-task Security Level: Public (Everyone can see) Components: rar Reporter: Brian Stansberry Assignee: Jesper Pedersen Jesper, per our IRC discussion today... this is the JIRA to ensure the metadata coming out of rar.xml can have it's module-name manipulated by the deployer I added for JBAS-7644. -- 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

16 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMETA-268) EE 6 module name concept in war metadata

by Brian Stansberry (JIRA)

EE 6 module name concept in war metadata ---------------------------------------- Key: JBMETA-268 URL: https://jira.jboss.org/jira/browse/JBMETA-268 Project: JBoss Metadata Issue Type: Sub-task Security Level: Public (Everyone can see) Components: web Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: jboss-metadata-web-2.0.0-alpha-14 Web metadata portion of parent task. -- 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

16 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-7797) EARContentsDeployer creates the wrong name for modules

by Brian Stansberry (JIRA)

EARContentsDeployer creates the wrong name for modules ------------------------------------------------------ Key: JBAS-7797 URL: https://jira.jboss.org/jira/browse/JBAS-7797 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployers Affects Versions: JBossAS-6.0.0.M2 Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Minor Fix For: JBossAS-6.0.0.M3 It passes the result of this calculation to ModuleMetaData.setFileName(): private String earRelativePath(String earPath, String pathName) { StringBuilder tmp = new StringBuilder(pathName); tmp.delete(0, earPath.length()); return tmp.toString(); } That will include a leading /, e.g. foo.ear/bar.war will have a ModuleMetaData with name "/bar.war". It should be "bar.war". This impacts the processing done as part of JBAS-7644. EARStructure has the same flaw, but the "earRelativePath" is passed to VirtualFile.getChild(earRelativePath) which ignores the leading /. -- 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

16 years, 4 months

1
1
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 March 2010