April 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBRULES-3127) PackageBuilder should support an ordered iteration of added/merged packages

by Davide Sottara (JIRA)

[ https://issues.jboss.org/browse/JBRULES-3127?page=com.atlassian.jira.plug... ] Davide Sottara resolved JBRULES-3127. ------------------------------------- Fix Version/s: 5.5.0.Final Resolution: Done > PackageBuilder should support an ordered iteration of added/merged packages > ---------------------------------------------------------------------------- > > Key: JBRULES-3127 > URL: https://issues.jboss.org/browse/JBRULES-3127 > Project: JBRULES > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: drools-compiler > Reporter: Davide Sottara > Assignee: Mark Proctor > Priority: Minor > Fix For: 5.5.0.Final > > > The getPackages() method returns an array of packages which is based on the internal map's iteration order. > Instead, the order should depend on the package addition/merge sequence. > E.g. if a KnowledgeBuilder adds the following resources: > r1 -> package p1 > r2 -> package p2 > r3 -> package p2 > r4 -> package p3 > r5 -> package p1 > the sequence in the array should be p1, p3, p2 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-730) Special Characters in User Names

by Guillaume Grossetie (JIRA)

[ https://issues.jboss.org/browse/WFLY-730?page=com.atlassian.jira.plugin.s... ] Guillaume Grossetie commented on WFLY-730: ------------------------------------------ Is this issue related to the ./add-user.sh script which do not supports "-" in user names ? If this is the case, I can make a quick fix in [1] to add "-" to the valid punctuation list. [1] https://github.com/wildfly/wildfly/blob/master/domain-management/src/main... > Special Characters in User Names > -------------------------------- > > Key: WFLY-730 > URL: https://issues.jboss.org/browse/WFLY-730 > Project: WildFly > Issue Type: Feature Request > Components: Scripts > Reporter: Fernando Ribeiro > Fix For: Awaiting Volunteers > > > When working with domains, I've noticed that having special characters that are valid in host names (like "-") in user names should be supported to prevent having "fake" host names configured in host.xml files and displayed in the management interfaces. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-732) Ability to declare a dependency on a service name

by Dimitris Andreadis (JIRA)

[ https://issues.jboss.org/browse/WFLY-732?page=com.atlassian.jira.plugin.s... ] Dimitris Andreadis commented on WFLY-732: ----------------------------------------- Is this still worked on, or have you left it Stuart? > Ability to declare a dependency on a service name > ------------------------------------------------- > > Key: WFLY-732 > URL: https://issues.jboss.org/browse/WFLY-732 > Project: WildFly > Issue Type: Feature Request > Reporter: Brad Maxwell > Assignee: Stuart Douglas > Fix For: Awaiting Volunteers > > > We have several use cases where we need dependencies between different deployments. > Such as > Singleton in ear1 which injects an ejb from ear2 using @EJB. At shutdown we need the Singleton to call a method to clean up on the ejb, however the ejb is sometimes shutdown before the Singleton. Using @DependsOn would allow the Singleton to depend on the EJB if the EJB is in the same ear as the Singleton, however it is not. > There are other use cases where resources are injected and we need the resources to still be deployed at shutdown so we can clean up the resources before they are undeployed. > Having a service name to depend on would be useful and if the name was configurable such that it does not based on the exact name of the deployment, it would be useful as using maven changes the deployment names when we rebuild and we do not want to have to change the code each time we rebuild. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1086) Provide deployment manifest information via the CLI

by Dimitris Andreadis (JIRA)

[ https://issues.jboss.org/browse/WFLY-1086?page=com.atlassian.jira.plugin.... ] Dimitris Andreadis updated WFLY-1086: ------------------------------------- Priority: Critical (was: Major) > Provide deployment manifest information via the CLI > --------------------------------------------------- > > Key: WFLY-1086 > URL: https://issues.jboss.org/browse/WFLY-1086 > Project: WildFly > Issue Type: Feature Request > Components: CLI, Domain Management > Reporter: Brian Stansberry > Priority: Critical > > We've gotten a user request for providing the contents of a deployment's MANIFEST.MF via the CLI. > The request is to include an option to get the manifest info for a single deployment, and also the info for all deployments. > This task needs to be evaluated in relationship to the larger request to provide read (and possibly in some cases write) access to all files within a deployment. The manifest is essentially just one file with a standard location. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1291) Invalid package capabilities for registered modules

by Thomas Diesler (JIRA)

Thomas Diesler created WFLY-1291: ------------------------------------ Summary: Invalid package capabilities for registered modules Key: WFLY-1291 URL: https://issues.jboss.org/browse/WFLY-1291 Project: WildFly Issue Type: Bug Components: OSGi Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 8.0.0.Alpha1 A jar registered with the OSGi layer exports the full transitive graph of reachable packages. It should however only expose its own package capabilities. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1290) VFSResourceLoader does not allow to iterate resources

by Thomas Diesler (JIRA)

Thomas Diesler created WFLY-1290: ------------------------------------ Summary: VFSResourceLoader does not allow to iterate resources Key: WFLY-1290 URL: https://issues.jboss.org/browse/WFLY-1290 Project: WildFly Issue Type: Bug Components: OSGi, Server Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 8.0.0.Alpha1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-967) ClassLoader memory leak with JSF

by Vlad Arkhipov (JIRA)

[ https://issues.jboss.org/browse/WFLY-967?page=com.atlassian.jira.plugin.s... ] Vlad Arkhipov commented on WFLY-967: ------------------------------------ 7.2.0.Final (6.1.0 EAP). > ClassLoader memory leak with JSF > -------------------------------- > > Key: WFLY-967 > URL: https://issues.jboss.org/browse/WFLY-967 > Project: WildFly > Issue Type: Bug > Components: JSF > Reporter: Vlad Arkhipov > Assignee: Stan Silvert > Priority: Critical > Attachments: war-leak.tar.gz > > > JSF application's classes are not unloaded properly when undeployed. The test case is in the attachment. Steps to reproduce: > # mvn package > # deploy war-leak.war > # open http://localhost:8080/war-leak > # undeploy war-leak.war > # analyze a heap dump to find unloaded ModuleClassLoader of war-leak.war > References to the WAR classes are hold by java.beans.Introspector caches. It seems to be a known bug (feature?). For example Tomcat automatically invokes java.beans.Introspector.flushCaches() when WAR undeploys. There is also IntrospectorCleanupListener in Spring for the same purpose. > http://wiki.apache.org/commons/Logging/UndeployMemoryLeak > http://static.springsource.org/spring/docs/2.5.x/api/org/springframework/... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-967) ClassLoader memory leak with JSF

by Stan Silvert (JIRA)

[ https://issues.jboss.org/browse/WFLY-967?page=com.atlassian.jira.plugin.s... ] Stan Silvert commented on WFLY-967: ----------------------------------- Vlad, which version of AS are you using? > ClassLoader memory leak with JSF > -------------------------------- > > Key: WFLY-967 > URL: https://issues.jboss.org/browse/WFLY-967 > Project: WildFly > Issue Type: Bug > Components: JSF > Reporter: Vlad Arkhipov > Assignee: Stan Silvert > Priority: Critical > Attachments: war-leak.tar.gz > > > JSF application's classes are not unloaded properly when undeployed. The test case is in the attachment. Steps to reproduce: > # mvn package > # deploy war-leak.war > # open http://localhost:8080/war-leak > # undeploy war-leak.war > # analyze a heap dump to find unloaded ModuleClassLoader of war-leak.war > References to the WAR classes are hold by java.beans.Introspector caches. It seems to be a known bug (feature?). For example Tomcat automatically invokes java.beans.Introspector.flushCaches() when WAR undeploys. There is also IntrospectorCleanupListener in Spring for the same purpose. > http://wiki.apache.org/commons/Logging/UndeployMemoryLeak > http://static.springsource.org/spring/docs/2.5.x/api/org/springframework/... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1289) Spurious warnings about invalid META-INF/services class name

by Harald Wellmann (JIRA)

Harald Wellmann created WFLY-1289: ------------------------------------- Summary: Spurious warnings about invalid META-INF/services class name Key: WFLY-1289 URL: https://issues.jboss.org/browse/WFLY-1289 Project: WildFly Issue Type: Bug Components: Class Loading Environment: 7.2.0.Final java version "1.7.0_21" Ubuntu 12.04 LTS Reporter: Harald Wellmann Assignee: David Lloyd When an application contains a {{META-INF/services}} resource referencing an inner class, JBoss prints a spurious warning {noformat} JBAS015893: Encountered invalid class name 'com.acme.Foo$Bar' for service type 'com.acme.Service' {noformat} {{META-INF/services}} lists classes with their binary name, so dollar characters are likely to occur. {{org.jboss.as.server.deployment.ServiceLoaderProcessor}} scans all {{META-INF/services}} resources but does not accept dollar characters in its validation pattern. (Note: I can't select any 7.x release for "Affects Version".) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBFORUMS-299) JBoss 5.2 eap file protocol issue

by Wang Yu (JIRA)

Wang Yu created JBFORUMS-299: -------------------------------- Summary: JBoss 5.2 eap file protocol issue Key: JBFORUMS-299 URL: https://issues.jboss.org/browse/JBFORUMS-299 Project: JBoss Forums Issue Type: Feature Request Environment: Window X64, JBoss 5.2 Reporter: Wang Yu Assignee: Luca Stancapiano there is an issue of JBoss 5.2.0 which hasn’t been solved. This issue is a similiar issue as the issue for JBoss 5.1.2. Red Hat has released a patch on https://access.redhat.com/jbossnetwork/restricted/softwareDetail.html?sof... to fix this problem on JBoss 5..1.2. But I haven’t found any patch for this issue on 5.2.0. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
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 April 2013