February 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBEE-110) Add relocations from org.jboss.spec.* to non org.jboss.spec artifacts

by Paul Gier (JIRA)

[ https://issues.jboss.org/browse/JBEE-110?page=com.atlassian.jira.plugin.s... ] Paul Gier commented on JBEE-110: -------------------------------- This page on the Maven site contains some information about how to do relocation: http://maven.apache.org/guides/mini/guide-relocation.html > Add relocations from org.jboss.spec.* to non org.jboss.spec artifacts > --------------------------------------------------------------------- > > Key: JBEE-110 > URL: https://issues.jboss.org/browse/JBEE-110 > Project: JBoss JavaEE Spec APIs > Issue Type: Feature Request > Affects Versions: JavaEE 6 Spec APIs 3.0.0.Final > Reporter: Pete Muir > Assignee: Paul Gier > Priority: Critical > > For example, we use org.hibernate and javax.enterprise group ids for JPA and CDI. It would be nice if we created stubs with relocations for these under org.jboss.spec so that the new developer can just follow the naming conventions with no exceptions. -- 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] (JBEE-110) Add relocations from org.jboss.spec.* to non org.jboss.spec artifacts

by Ondrej Zizka (JIRA)

[ https://issues.jboss.org/browse/JBEE-110?page=com.atlassian.jira.plugin.s... ] Ondrej Zizka commented on JBEE-110: ----------------------------------- Pete, is there a list of candidates for this? > Add relocations from org.jboss.spec.* to non org.jboss.spec artifacts > --------------------------------------------------------------------- > > Key: JBEE-110 > URL: https://issues.jboss.org/browse/JBEE-110 > Project: JBoss JavaEE Spec APIs > Issue Type: Feature Request > Affects Versions: JavaEE 6 Spec APIs 3.0.0.Final > Reporter: Pete Muir > Assignee: Paul Gier > Priority: Critical > > For example, we use org.hibernate and javax.enterprise group ids for JPA and CDI. It would be nice if we created stubs with relocations for these under org.jboss.spec so that the new developer can just follow the naming conventions with no exceptions. -- 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] (AS7-6581) Security manager subsystem

by Anil Saldhana (JIRA)

[ https://issues.jboss.org/browse/AS7-6581?page=com.atlassian.jira.plugin.s... ] Anil Saldhana reassigned AS7-6581: ---------------------------------- Assignee: Stefan Guilhen (was: Anil Saldhana) Stefan - can you lead the discussion on the security manager subsystem design? > Security manager subsystem > -------------------------- > > Key: AS7-6581 > URL: https://issues.jboss.org/browse/AS7-6581 > Project: Application Server 7 > Issue Type: Sub-task > Components: Security > Reporter: Anil Saldhana > Assignee: Stefan Guilhen > Fix For: 8.0.0.Alpha1 > > > Security manager subsystem is useful to > a) enable/disable Java Security Manager. > b) define the global permissions used by the Module ClassLoaders. -- 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] (JBEE-93) Create document that correlates versions of the jboss-javaee-6.0 and jboss-javaee-web-6.0 to JBAS 6 and AS 7 releases

by Shelly McGowan (JIRA)

[ https://issues.jboss.org/browse/JBEE-93?page=com.atlassian.jira.plugin.sy... ] Shelly McGowan commented on JBEE-93: ------------------------------------ JBoss Application Server 6.0.0.Final and JBoss Application Server 6.1.0.Final: https://repository.jboss.org/nexus/content/groups/public/org/jboss/spec/j... Application Server 7.0.0.Final https://repository.jboss.org/nexus/content/groups/public/org/jboss/spec/j... https://repository.jboss.org/nexus/content/groups/public/org/jboss/spec/j... Application Server 7.1.1.Final https://repository.jboss.org/nexus/content/groups/public/org/jboss/spec/j... https://repository.jboss.org/nexus/content/groups/public/org/jboss/spec/j... https://repository.jboss.org/nexus/content/groups/public/org/jboss/spec/j... Application Server 7.2.0.Final https://repository.jboss.org/nexus/content/groups/public/org/jboss/spec/j... https://repository.jboss.org/nexus/content/groups/public/org/jboss/spec/j... https://repository.jboss.org/nexus/content/groups/public/org/jboss/spec/j... I'll add the above info in table format to the Java EE API Specs wiki. > Create document that correlates versions of the jboss-javaee-6.0 and jboss-javaee-web-6.0 to JBAS 6 and AS 7 releases > --------------------------------------------------------------------------------------------------------------------- > > Key: JBEE-93 > URL: https://issues.jboss.org/browse/JBEE-93 > Project: JBoss JavaEE Spec APIs > Issue Type: Enhancement > Components: general > Reporter: Shelly McGowan > Assignee: Shelly McGowan > Fix For: No Release > > -- 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] (AS7-6557) Security Manager integration

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/AS7-6557?page=com.atlassian.jira.plugin.s... ] David Lloyd edited comment on AS7-6557 at 2/21/13 1:23 PM: ----------------------------------------------------------- Just a few notes on that idea so when I wake up tomorrow it isn't all forgotten: * (/) We'll need to implement {{java.security.Policy}} with a simple policy that includes the jboss-modules.jar code source * We have options: ** -Just let all remaining permissions be installed via modules- ** Or, use the policy mechanism to merge in some global config * Notes: ** -Look into keying off of something besides code source - maybe modules should maintain/cache protection domains in addition to/instead of permission sets?- was (Author: dmlloyd): Just a few notes on that idea so when I wake up tomorrow it isn't all forgotten: * We'll need to implement {{java.security.Policy}} with a simple policy that includes the jboss-modules.jar code source * We have options: ** Just let all remaining permissions be installed via modules ** Or, use the policy mechanism to merge in some global config * Notes: ** Look into keying off of something besides code source - maybe modules should maintain/cache protection domains in addition to/instead of permission sets? > Security Manager integration > ---------------------------- > > Key: AS7-6557 > URL: https://issues.jboss.org/browse/AS7-6557 > Project: Application Server 7 > Issue Type: Sub-task > Components: Security > Reporter: David Lloyd > Assignee: Anil Saldhana > Fix For: 8.0.0.Alpha1 > > > As per the Java EE 7 spec, all Java EE products must be capable of running within a Java security manager. Test each Java EE configuration including application client for security manager operability. Implement configuration and management as appropriate. See AS7-6572 for detailed task list. > Discuss with [~dmlloyd] options around modules integration. -- 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] (AS7-6524) In non-interactive mode the add-user utility should replace duplicate users instead of reporting an error.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/AS7-6524?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated AS7-6524: ---------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) > In non-interactive mode the add-user utility should replace duplicate users instead of reporting an error. > ---------------------------------------------------------------------------------------------------------- > > Key: AS7-6524 > URL: https://issues.jboss.org/browse/AS7-6524 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management > Affects Versions: 7.2.0.Alpha1 > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 8.0.0.Alpha1 > > > In non-interactive mode the ass-user utility should replace duplicate users instead of reporting an error. -- 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] (AS7-6382) Local auth doesn't work on Windows when client uses link-local address without zone-id

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/AS7-6382?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated AS7-6382: ---------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) > Local auth doesn't work on Windows when client uses link-local address without zone-id > -------------------------------------------------------------------------------------- > > Key: AS7-6382 > URL: https://issues.jboss.org/browse/AS7-6382 > Project: Application Server 7 > Issue Type: Bug > Components: CLI, Domain Management, Security > Affects Versions: 7.1.3.Final (EAP) > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 8.0.0.Alpha1 > > > This is most likely caused by an optimisation during initialisation that checks that the server being connected to is really local - if that server is not detected as being local from the address then the local authentication mechanism is omitted from the list of supported mechanisms. -- 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] (AS7-6551) Add Version 2.0 of the jboss-as-config schema

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/AS7-6551?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated AS7-6551: ---------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) > Add Version 2.0 of the jboss-as-config schema > --------------------------------------------- > > Key: AS7-6551 > URL: https://issues.jboss.org/browse/AS7-6551 > Project: Application Server 7 > Issue Type: Task > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 8.0.0.Alpha1 > > > Add version 2.0 of the domain management schema. > A few issues currently being worked on require this so we are splitting out the new version so they can all build on it. -- 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] (AS7-6557) Security Manager integration

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/AS7-6557?page=com.atlassian.jira.plugin.s... ] David Lloyd updated AS7-6557: ----------------------------- Summary: Security Manager integration (was: Verify operation within a security manager ) Description: As per the Java EE 7 spec, all Java EE products must be capable of running within a Java security manager. Test each Java EE configuration including application client for security manager operability. Implement configuration and management as appropriate. See AS7-6572 for detailed task list. Discuss with [~dmlloyd] options around modules integration. was: As per the Java EE 7 spec, all Java EE products must be capable of running within a Java security manager. Test each Java EE configuration including application client for security manager operability. Discuss with [~dmlloyd] options around modules integration. > Security Manager integration > ---------------------------- > > Key: AS7-6557 > URL: https://issues.jboss.org/browse/AS7-6557 > Project: Application Server 7 > Issue Type: Sub-task > Components: Security > Reporter: David Lloyd > Assignee: Anil Saldhana > Fix For: 8.0.0.Alpha1 > > > As per the Java EE 7 spec, all Java EE products must be capable of running within a Java security manager. Test each Java EE configuration including application client for security manager operability. Implement configuration and management as appropriate. See AS7-6572 for detailed task list. > Discuss with [~dmlloyd] options around modules integration. -- 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] (AS7-6588) Implement new java:comp names for EE 7

by David Lloyd (JIRA)

David Lloyd created AS7-6588: -------------------------------- Summary: Implement new java:comp names for EE 7 Key: AS7-6588 URL: https://issues.jboss.org/browse/AS7-6588 Project: Application Server 7 Issue Type: Sub-task Components: EE, Naming Reporter: David Lloyd Fix For: 8.0.0.Alpha1 New sections EE.5.16 and EE.5.17 cover JNDI names that have to be bound. * {{java:comp/InstanceName}} - contains the node name * {{java:comp/InAppClientContainer}} - contains Boolean.TRUE if running in app client mode Add more here if found. -- 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 February 2013