May 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-4685) module schemas are missing from documentation

by Philippe Marschall (JIRA)

Philippe Marschall created AS7-4685: --------------------------------------- Summary: module schemas are missing from documentation Key: AS7-4685 URL: https://issues.jboss.org/browse/AS7-4685 Project: Application Server 7 Issue Type: Enhancement Components: Build System, Documentation Affects Versions: 7.1.1.Final Reporter: Philippe Marschall Assignee: Paul Gier Priority: Minor The schemas for the jboss module system are missing from the docs/schemas folder. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
0
0 / 0

[JBoss JIRA] (AS7-4417) permissions for security roles are not redefined by jboss-ejb3.xml

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/AS7-4417?page=com.atlassian.jira.plugin.s... ] Stuart Douglas resolved AS7-4417. --------------------------------- Resolution: Done > permissions for security roles are not redefined by jboss-ejb3.xml > ------------------------------------------------------------------ > > Key: AS7-4417 > URL: https://issues.jboss.org/browse/AS7-4417 > Project: Application Server 7 > Issue Type: Bug > Reporter: Radim Hatlapatka > Assignee: Stuart Douglas > Labels: descriptor, security > Fix For: 7.1.2.Final-redhat1 > > > When I have defined permissions using security roles in ejb-jar.xml (ejb-spec) for certain methods and if I define them differently in jboss-ejb3.xml (jboss-spec) the permissions remain as their are defined in ejb-jar.xml. But I would expect that ejb-spec will redefine the permissions (because merging is not possible). > For details see written tests here: https://github.com/rhatlapa/jboss-as/commit/62adba59b288a53672a6b08c8a710... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
0
0 / 0

[JBoss JIRA] (AS7-4638) Add ability to exclude a subsystems DUP's via jboss-deployment-structure.xml

by Stuart Douglas (JIRA)

Stuart Douglas created AS7-4638: ----------------------------------- Summary: Add ability to exclude a subsystems DUP's via jboss-deployment-structure.xml Key: AS7-4638 URL: https://issues.jboss.org/browse/AS7-4638 Project: Application Server 7 Issue Type: Feature Request Reporter: Stuart Douglas Fix For: 7.1.2.Final-redhat1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
2
0 / 0

[JBoss JIRA] (JBADMCON-170) Jboss Migration from 4.5.3 GA to Jboss Enterprise Edition.

by Surendra Ipperla (JIRA)

Surendra Ipperla created JBADMCON-170: ----------------------------------------- Summary: Jboss Migration from 4.5.3 GA to Jboss Enterprise Edition. Key: JBADMCON-170 URL: https://issues.jboss.org/browse/JBADMCON-170 Project: JBoss Admin Console Issue Type: Enhancement Reporter: Surendra Ipperla We would like to Migrate the Jboss 4.2.3 GA to Jboss Enterprise Edition. Coping the Server folder (<jboss install dir>/server/<server name>) to the Enterprise edition will be enough. If we done in this way is there will be any side effects. Or Do we need to do any configuration changes. Please provide us information and steps to be followed in this Migration Process. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
1
0 / 0

[JBoss JIRA] (AS7-3863) jgroups protocol order not retained

by Heiko Braun (JIRA)

Heiko Braun created AS7-3863: -------------------------------- Summary: jgroups protocol order not retained Key: AS7-3863 URL: https://issues.jboss.org/browse/AS7-3863 Project: Application Server 7 Issue Type: Bug Components: Domain Management Reporter: Heiko Braun Assignee: Brian Stansberry Fix For: 7.1.1.Final the xml config: {noformat} <stack name="tcp"> <transport type="TCP" socket-binding="jgroups-tcp" diagnostics-socket-binding="jgroups-diagnostics"/> <protocol type="MPING" socket-binding="jgroups-mping"/> <protocol type="MERGE2"/> <protocol type="FD_SOCK" socket-binding="jgroups-tcp-fd"/> <protocol type="FD"/> <protocol type="VERIFY_SUSPECT"/> <protocol type="BARRIER"/> <protocol type="pbcast.NAKACK"/> <protocol type="UNICAST2"/> <protocol type="pbcast.STABLE"/> <protocol type="pbcast.GMS"/> <protocol type="UFC"/> <protocol type="MFC"/> <protocol type="FRAG2"/> </stack> {noformat} the DMR response: {noformat} "protocol" => { "FD_SOCK" => undefined, "FD" => undefined, "VERIFY_SUSPECT" => undefined, "BARRIER" => undefined, "FRAG2" => undefined, "MERGE2" => undefined, "pbcast.GMS" => undefined, "UNICAST2" => undefined, "UFC" => undefined, "MFC" => undefined, "pbcast.NAKACK" => undefined, "pbcast.STABLE" => undefined, "MPING" => undefined }, {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

5
10
0 / 0

[JBoss JIRA] (JBRULES-3441) Declared Beans with interface-typed fields cause exceptions when evaluating hashCode()

by Davide Sottara (JIRA)

Davide Sottara created JBRULES-3441: --------------------------------------- Summary: Declared Beans with interface-typed fields cause exceptions when evaluating hashCode() Key: JBRULES-3441 URL: https://issues.jboss.org/browse/JBRULES-3441 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler, drools-core Reporter: Davide Sottara Assignee: Davide Sottara Given an interface: interface SomeInterface { int getId(); void setId(int id); } and a declared bean: declare SomeFact ( x : SomeInterface @key ) the system throws an exception "a class is expected but an interface is found" when evaluating the hashCode method -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
2
0 / 0

[JBoss JIRA] (JBRULES-3449) null dsdfeesd

by dnktty chen (JIRA)

dnktty chen created JBRULES-3449: ------------------------------------ Summary: null dsdfeesd Key: JBRULES-3449 URL: https://issues.jboss.org/browse/JBRULES-3449 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-ant Affects Versions: 5.4.0.Beta2 Environment: sd Reporter: dnktty chen Assignee: Mark Proctor Fix For: Out of scope s -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
3
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 May 2012