December 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-6174) Setup TCK job for Enterprise OSGi JPA

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-6174: ----------------------------------- Summary: Setup TCK job for Enterprise OSGi JPA Key: AS7-6174 URL: https://issues.jboss.org/browse/AS7-6174 Project: Application Server 7 Issue Type: Task Components: OSGi Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 7.2.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, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-6175) Setup TCK job for Enterprise OSGi HttpService

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-6175: ----------------------------------- Summary: Setup TCK job for Enterprise OSGi HttpService Key: AS7-6175 URL: https://issues.jboss.org/browse/AS7-6175 Project: Application Server 7 Issue Type: Task Components: OSGi Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 7.2.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, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-6173) Initial FrameworkFactory implementation

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-6173: ----------------------------------- Summary: Initial FrameworkFactory implementation Key: AS7-6173 URL: https://issues.jboss.org/browse/AS7-6173 Project: Application Server 7 Issue Type: Task Components: OSGi Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 7.2.0.CR1 Provide an initial FrameworkFactory implementation that allows to run basic Enterprise OSGi TCK sections (i.e. httpservice) -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-6172) Consolidate embedded server API

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-6172: ----------------------------------- Summary: Consolidate embedded server API Key: AS7-6172 URL: https://issues.jboss.org/browse/AS7-6172 Project: Application Server 7 Issue Type: Task Components: Server Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 7.2.0.Alpha1 There are currently a number of duplicate code paths leading up to the EmbeddedServerFactory. This should be consolidated such that it is sufficient to do this {code} StandaloneServer server = EmbeddedServerFactory.create(jbossHome, modulePath, bundlePath, syspackages...); {code} The ARQ/EJB3 embedded container as well as the future FrameworkFactory integration benefit from this -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-711) LdapExtAdLoginModule proposal for inclusion

by Péter Radics (JIRA)

[ https://issues.jboss.org/browse/SECURITY-711?page=com.atlassian.jira.plug... ] Péter Radics updated SECURITY-711: ---------------------------------- Attachment: picketbox-r363-LdapExtAdLoginModule-with-history.patch This patch shows the difference between the original LdapExtLoginModule and LdapExtAdLoginModule > LdapExtAdLoginModule proposal for inclusion > ------------------------------------------- > > Key: SECURITY-711 > URL: https://issues.jboss.org/browse/SECURITY-711 > Project: PicketBox > Issue Type: Patch > Security Level: Public(Everyone can see) > Components: PicketBox, Security SPI > Affects Versions: PicketBox_4_0_14.Final > Environment: jboss7, active directory authentication > Reporter: Péter Radics > Assignee: Anil Saldhana > Priority: Minor > Labels: LdapExtLoginModule, active-directory, security > Attachments: picketbox-r362-LdapExtAdLoginModule.patch, picketbox-r363-LdapExtAdLoginModule-with-history.patch > > Original Estimate: 1 week > Remaining Estimate: 1 week > > Please consider including the attached LdapExtAdLoginModule into the official release. This login module is based on r362 of LdapExtLoginModule, but it's better suited for deeply nested Active Directory domains: it only uses one search for the userDN then it's resolving the roles recursively by querying attributes on DNs only. (as a side-effect, it doesn't trigger AS7-5737) -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBLOGGING-30) TCLFilter fails to get correct URLs from classloader in AS-5

by Arun Kumar (JIRA)

[ https://issues.jboss.org/browse/JBLOGGING-30?page=com.atlassian.jira.plug... ] Arun Kumar commented on JBLOGGING-30: ------------------------------------- i tried to implement the TCLfilter by following the robert as per below link https://community.jboss.org/message/6616 but i got failed. is there any updated jar available for this.. Please help.. > TCLFilter fails to get correct URLs from classloader in AS-5 > -------------------------------------------------------------- > > Key: JBLOGGING-30 > URL: https://issues.jboss.org/browse/JBLOGGING-30 > Project: JBoss Logging > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jboss-logging-log4j > Affects Versions: 2.1.0.GA-jboss-logging > Reporter: jaikiran pai > Assignee: jaikiran pai > Fix For: 2.1.1.GA-jboss-logging, 2.2.0.CR2-jboss-logging > > > As explained in JBAS-6532, the TCLFilter doesn't work in AS-5 because it never attempts to use the URLClassLoader while retrieving the Classloader URLs. A patch is attached to that JIRA (details of the patch are in the forum thread) which needs to be applied in jboss-logging-log4j component to get this working. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1) Rules getting executed even when the condition specifed is not satisfied

by Gladson Soans (JIRA)

Gladson Soans created DROOLS-1: ---------------------------------- Summary: Rules getting executed even when the condition specifed is not satisfied Key: DROOLS-1 URL: https://issues.jboss.org/browse/DROOLS-1 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Environment: SOLARIS Reporter: Gladson Soans Assignee: Mark Proctor Hi, Below is the rules: rule "RelStatusUpdateCalcCheck" salience 55 no-loop true when $evt : UpdateRateStatusReq(statusID == RateStatusEnum.READY.getValue() || == RateStatusEnum.HOLIDAY_ROLL_FORWARD.getValue() || == RateStatusEnum.ROLL_FORWARD.getValue()) from entry-point RequestStream $rr : ReliableRate(rateId == $evt.getRateID()) $dr : DerivedRate(holidayFlag == false, grfLock == false, $lr : listInputRateId, $lr.contains($evt.getRateID())) then cepService.relStatusUpdateCalcCheck($evt, $rr, $dr); end The last condition states that if 'holidayflag' is false and other conditions are satisfied as well then only execute the the java method. But the method gets executed even when the holidayflag is true. Only when I restart my app server the method doesnt get executed when holidayflag is true. Why is this so? -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-6171) Confusing error message when an invalid element is added to host.xml

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-6171?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-6171: ---------------------------------- Fix Version/s: 7.2.0.Alpha1 (was: 7.2.0.CR1) > Confusing error message when an invalid element is added to host.xml > -------------------------------------------------------------------- > > Key: AS7-6171 > URL: https://issues.jboss.org/browse/AS7-6171 > Project: Application Server 7 > Issue Type: Enhancement > Components: Domain Management > Affects Versions: 7.1.3.Final (EAP) > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Minor > Fix For: 7.2.0.Alpha1 > > > I deliberately added an element <bogus/> to host.xml as part of testing something. I got this not very useful error message: > [Host Controller] 20:25:50,435 ERROR [org.jboss.as.host.controller] (Controller Boot Thread) JBAS010932: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration > [Host Controller] at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:141) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] > [Host Controller] at org.jboss.as.host.controller.HostControllerConfigurationPersister.load(HostControllerConfigurationPersister.java:163) [jboss-as-host-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] > [Host Controller] at org.jboss.as.host.controller.DomainModelControllerService.boot(DomainModelControllerService.java:399) [jboss-as-host-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] > [Host Controller] at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:185) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] > [Host Controller] at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_37] > [Host Controller] Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[4,5] > [Host Controller] Message: JBAS014725: Missing required element(s): MANAGEMENT > [Host Controller] at org.jboss.as.controller.parsing.ParseUtils.missingRequiredElement(ParseUtils.java:154) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] > [Host Controller] at org.jboss.as.host.controller.parsing.HostXml.readHostElement_1_1(HostXml.java:392) [jboss-as-host-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] > [Host Controller] at org.jboss.as.host.controller.parsing.HostXml.readElement(HostXml.java:129) [jboss-as-host-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] > [Host Controller] at org.jboss.as.host.controller.parsing.HostXml.readElement(HostXml.java:104) [jboss-as-host-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] > [Host Controller] at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) [staxmapper-1.1.0.Final.jar:1.1.0.Final] > [Host Controller] at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) [staxmapper-1.1.0.Final.jar:1.1.0.Final] > [Host Controller] at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:133) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] > [Host Controller] ... 4 more > The parser should detect the invalid element and fail with the unexpected element message. > Look for the same problem elsewhere as well. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-6171) Confusing error message when an invalid element is added to host.xml

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-6171: ------------------------------------- Summary: Confusing error message when an invalid element is added to host.xml Key: AS7-6171 URL: https://issues.jboss.org/browse/AS7-6171 Project: Application Server 7 Issue Type: Enhancement Components: Domain Management Affects Versions: 7.1.3.Final (EAP) Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Minor Fix For: 7.2.0.CR1 I deliberately added an element <bogus/> to host.xml as part of testing something. I got this not very useful error message: [Host Controller] 20:25:50,435 ERROR [org.jboss.as.host.controller] (Controller Boot Thread) JBAS010932: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration [Host Controller] at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:141) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] [Host Controller] at org.jboss.as.host.controller.HostControllerConfigurationPersister.load(HostControllerConfigurationPersister.java:163) [jboss-as-host-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] [Host Controller] at org.jboss.as.host.controller.DomainModelControllerService.boot(DomainModelControllerService.java:399) [jboss-as-host-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] [Host Controller] at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:185) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] [Host Controller] at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_37] [Host Controller] Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[4,5] [Host Controller] Message: JBAS014725: Missing required element(s): MANAGEMENT [Host Controller] at org.jboss.as.controller.parsing.ParseUtils.missingRequiredElement(ParseUtils.java:154) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] [Host Controller] at org.jboss.as.host.controller.parsing.HostXml.readHostElement_1_1(HostXml.java:392) [jboss-as-host-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] [Host Controller] at org.jboss.as.host.controller.parsing.HostXml.readElement(HostXml.java:129) [jboss-as-host-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] [Host Controller] at org.jboss.as.host.controller.parsing.HostXml.readElement(HostXml.java:104) [jboss-as-host-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] [Host Controller] at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) [staxmapper-1.1.0.Final.jar:1.1.0.Final] [Host Controller] at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) [staxmapper-1.1.0.Final.jar:1.1.0.Final] [Host Controller] at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:133) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] [Host Controller] ... 4 more The parser should detect the invalid element and fail with the unexpected element message. Look for the same problem elsewhere as well. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-1581) tomcatAuthentication attribute on the AJP connector

by Usman Saleem (JIRA)

[ https://issues.jboss.org/browse/AS7-1581?page=com.atlassian.jira.plugin.s... ] Usman Saleem commented on AS7-1581: ----------------------------------- Hi Jean, You modified http://anonsvn.jboss.org/repos/jbossweb/tags/JBOSSWEB_7_0_17_FINAL/java/o... with following change: {noformat} protected boolean tomcatAuthentication = Boolean.valueOf(System.getProperty("org.apache.coyote.ajp.AprProcessor.TOMCATAUTHENTICATION", "true")).booleanValue(); {noformat} However, AjpAprProtocol.java modified this value as follows: {noformat} /** * Should authentication be done in the native webserver layer, * or in the Servlet container ? */ protected boolean tomcatAuthentication = true; ... // -------------------------------------- AjpConnectionHandler Inner Class protected static class AjpConnectionHandler implements Handler { ... protected AjpAprProcessor createProcessor() { AjpAprProcessor processor = new AjpAprProcessor(proto.packetSize, proto.endpoint); processor.setAdapter(proto.adapter); processor.setTomcatAuthentication(proto.tomcatAuthentication); // <--- This will override the system property settings. processor.setRequiredSecret(proto.requiredSecret); register(processor); return processor; } {noformat} Hence, the change should also be made in AjpAprProtocol.java as: {noformat} protected boolean tomcatAuthentication = Boolean.valueOf(System.getProperty("org.apache.coyote.ajp.AprProcessor.TOMCATAUTHENTICATION", "true")).booleanValue(); {noformat} Thanks, Usman > tomcatAuthentication attribute on the AJP connector > --------------------------------------------------- > > Key: AS7-1581 > URL: https://issues.jboss.org/browse/AS7-1581 > Project: Application Server 7 > Issue Type: Feature Request > Components: Web > Affects Versions: 7.0.0.Final > Environment: Windows Server 2003 32 bit, IIS 6, tomcat connector 1.2.28 used as an extension > Reporter: Brett Prucha > Assignee: Jean-Frederic Clere > Priority: Minor > Fix For: 7.2.0.CR1 > > > In JBoss 5.1.0 I could set the tomcatAuthentication attribute of the AJP connector to false to allow IIS to handle the authentication and pass that along to JBoss. I'm wanting to upgrade to JBoss 7 but unable to set this attribute in version 7.0.0 final to make this work. This attribute is descibed in the tomcat documentation at http://tomcat.apache.org/tomcat-7.0-doc/config/ajp.html -- 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, 7 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 December 2012