November 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-3155) Bug with default properties in KnowledgeStoreServiceImpl

by Pavel Sknar (JIRA)

Bug with default properties in KnowledgeStoreServiceImpl -------------------------------------------------------- Key: JBRULES-3155 URL: https://issues.jboss.org/browse/JBRULES-3155 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 5.2.0.Final Reporter: Pavel Sknar Assignee: Mark Proctor Priority: Critical Method setDefaultImplementations() set default properties in configProps (class KnowledgeStoreServiceImpl). mergeConfig() execute after specific properties loaded to configuration. This overlaps specific properties. [17:08] <pavlz> hi [17:09] <pavlz> I have bug for you [17:09] <Rikkola> :( [17:10] <pavlz> Problem with KnowledgeStoreServiceImpl [17:10] <pavlz> in org.drools.persistence.jpa [17:12] <pavlz> default properties merged first in config (in ChainedProperties: this.props.add( 0, properties )) [17:14] <pavlz> and this overlaps specific properties [17:15] <pavlz> drools.commandService, drools.timerService and else [17:15] <pavlz> I have this bug in 5.2.0.Final [17:23] <conan> pavlz: do you have a fix? [17:25] <pavlz> No, I see this now [17:27] <pavlz> but I think: need to create in ChainedProperties new method "setDefaultProperties" [17:29] <pavlz> and in SessionConfiguration too, to use this method in KnowledgeStoreServiceImpl.mergeConfig() [17:30] <pavlz> then default properties loaded later [17:31] <Rikkola> pavlz: best to make a jira about it [17:31] <Rikkola> https://issues.jboss.org/browse/JBRULES [17:31] <pavlz> ok -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

5
19
0 / 0

[JBoss JIRA] Created: (AS7-1038) Add http to https redirect capability to http-interface

by Darran Lofthouse (JIRA)

Add http to https redirect capability to http-interface ------------------------------------------------------- Key: AS7-1038 URL: https://issues.jboss.org/browse/AS7-1038 Project: Application Server 7 Issue Type: Task Components: Domain Management Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.0.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

4
9
0 / 0

[JBoss JIRA] (AS7-4195) Pass through Digest authentication against LDAP

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-4195: ------------------------------------- Summary: Pass through Digest authentication against LDAP Key: AS7-4195 URL: https://issues.jboss.org/browse/AS7-4195 Project: Application Server 7 Issue Type: Task Components: Domain Management, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.2.0.Alpha1 It is possible for a client to authenticate against an LDAP server using Digest authentication. This task is to make use of this with both our SASL mechanism and HTTP authenticator to provide a pass through check. We need AS7-3691 first and then this needs to be implemented in a way that can consistently be used for both SASL and HTTP Digest. -- 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

12 years, 11 months

2
2
0 / 0

[JBoss JIRA] (AS7-3691) A Negotiated HTTP Authenticator

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-3691: ------------------------------------- Summary: A Negotiated HTTP Authenticator Key: AS7-3691 URL: https://issues.jboss.org/browse/AS7-3691 Project: Application Server 7 Issue Type: Task Components: Domain Management, Security, Web Reporter: Darran Lofthouse Assignee: Darran Lofthouse Historically we have become constrained by an assumption that there should be a single authentication mechanism assigned to a web application. The HTTP specification however allows for multiple mechanisms to be used in parallel - this task is to investigate the feasibility of writing a single authenticator that is compatible with both JBoss Web and the Sun HTTP server used within AS7 to support a negotiated authentication using a single authenticator backed by a CallbackHandler based realm. The most common example is fallback from SPNEGO to a username / password based mechanism but for domain management we have also a case of trying to use CLIENT-CERT authentication first and then fallback if that is not possible. -- 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

12 years, 11 months

1
5
0 / 0

[JBoss JIRA] (AS7-4224) Please add a more intuitive way to configure access logging

by Alex Holmansky (JIRA)

Alex Holmansky created AS7-4224: ----------------------------------- Summary: Please add a more intuitive way to configure access logging Key: AS7-4224 URL: https://issues.jboss.org/browse/AS7-4224 Project: Application Server 7 Issue Type: Enhancement Components: CLI, Console Affects Versions: 7.1.0.Final Environment: Windows 7, CentOS 6 Reporter: Alex Holmansky Assignee: Alexey Loubyansky Priority: Minor There's currently no intuitive way to configure access logging in the web subsystem. In the CLI I can get to what seems like the right area: [standalone@localhost:9999 /] cd /subsystem=web/virtual-server=default-host [standalone@localhost:9999 virtual-server=default-host] ls access-log rewrite sso alias=["localhost","example.com"] default-web-module=ROOT.war enable-welcome-root=true and even [standalone@localhost:9999 virtual-server=default-host] cd access-log [standalone@localhost:9999 access-log] pwd /subsystem=web/virtual-server=default-host/access-log but it's absolutely unclear what to do next. In the web Admin Console this should be under Web->Servlet/HTTP->Virtual Servers, but is missing. -- 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

12 years, 11 months

5
10
0 / 0

[JBoss JIRA] (AS7-5554) Welcome-file ignores servlet mapping

by Brian Leathem (JIRA)

Brian Leathem created AS7-5554: ---------------------------------- Summary: Welcome-file ignores servlet mapping Key: AS7-5554 URL: https://issues.jboss.org/browse/AS7-5554 Project: Application Server 7 Issue Type: Bug Components: Web Affects Versions: 7.1.1.Final Reporter: Brian Leathem Assignee: Remy Maucherat Welcome files that correspond to a servlet-mapping are ignored. As an example, add a welcome file "index.jsf" and map "*.jsf" to the faces servlet. The welcome file will not be served when navigating to the folder. This is not in accordance with the Servlet 3.0 specification (Section 10.10): {quote} ... the Web server MUST again append each welcome file in the order specified in the deployment descriptor to the partial request and check if a servlet is mapped to that request URI. {quote} As an example of this in practice, refer to one of the many stackoverflow questions on the subject: http://stackoverflow.com/questions/4616493/how-to-set-jsf2-welcome-file-w... -- 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

12 years, 11 months

2
3
0 / 0

[JBoss JIRA] (JBWEB-252) No AccessLogValve documentation in JBoss Web 7

by Jason Shepherd (JIRA)

Jason Shepherd created JBWEB-252: ------------------------------------ Summary: No AccessLogValve documentation in JBoss Web 7 Key: JBWEB-252 URL: https://issues.jboss.org/browse/JBWEB-252 Project: JBoss Web Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Training Affects Versions: JBossWeb-7.0.15.GA, JBossWeb-7.2.0.Alpha1 Reporter: Jason Shepherd Assignee: Remy Maucherat Priority: Minor The documentation here does not contain any information about AccessLogValve. http://docs.jboss.org/jbossweb/7.0.x/ On this page, there is a link to the AccessLogValve documentation, but it's missing. http://docs.jboss.org/jbossweb/7.0.x/config/host.html This is where it lives in 2.1.x: http://docs.jboss.org/jbossweb/2.1.x/config/valve.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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (AS7-5899) CS2 CodeSet Interop Issue

by Brad Maxwell (JIRA)

[ https://issues.jboss.org/browse/AS7-5899?page=com.atlassian.jira.plugin.s... ] Brad Maxwell moved JBPAPP-10370 to AS7-5899: -------------------------------------------- Project: Application Server 7 (was: JBoss Enterprise Application Platform) Key: AS7-5899 (was: JBPAPP-10370) Workflow: GIT Pull Request workflow (was: jira) Affects Version/s: 7.1.2.Final (EAP) (was: EAP 6.0.0) Component/s: IIOP (was: Other) Security: (was: Public) Fix Version/s: Open To Community (was: EAP 6.1.0) Docs QE Status: (was: NEW) > CS2 CodeSet Interop Issue > ------------------------- > > Key: AS7-5899 > URL: https://issues.jboss.org/browse/AS7-5899 > Project: Application Server 7 > Issue Type: Bug > Components: IIOP > Affects Versions: 7.1.2.Final (EAP) > Reporter: Brad Maxwell > Assignee: Brad Maxwell > Labels: jacorb > Fix For: Open To Community > > > Interoperability issue when client in JBoss EAP 6 calls IBM WebSphere. The client in JBoss EAP 6 sends "foo" but the server side IBM WebSphere receives "?foo" -- 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

12 years, 12 months

1
0
0 / 0

[JBoss JIRA] (AS7-5899) CS2 CodeSet Interop Issue

by Brad Maxwell (JIRA)

[ https://issues.jboss.org/browse/AS7-5899?page=com.atlassian.jira.plugin.s... ] Brad Maxwell reassigned AS7-5899: --------------------------------- Assignee: Nick Cross (was: Brad Maxwell) > CS2 CodeSet Interop Issue > ------------------------- > > Key: AS7-5899 > URL: https://issues.jboss.org/browse/AS7-5899 > Project: Application Server 7 > Issue Type: Bug > Components: IIOP > Affects Versions: 7.1.2.Final (EAP) > Reporter: Brad Maxwell > Assignee: Nick Cross > Labels: jacorb > Fix For: Open To Community > > > Interoperability issue when client in JBoss EAP 6 calls IBM WebSphere. The client in JBoss EAP 6 sends "foo" but the server side IBM WebSphere receives "?foo" -- 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

12 years, 12 months

1
0
0 / 0

[JBoss JIRA] (AS7-5886) EJB container-transaction configuration need to include Timer method-intf

by Cheng Fang (JIRA)

Cheng Fang created AS7-5886: ------------------------------- Summary: EJB container-transaction configuration need to include Timer method-intf Key: AS7-5886 URL: https://issues.jboss.org/browse/AS7-5886 Project: Application Server 7 Issue Type: Bug Components: EJB Affects Versions: 7.2.0.CR1 Reporter: Cheng Fang Assignee: Cheng Fang In the following ejb-jar.xml snippet, {code:xml} <container-transaction> <method> <ejb-name>TestBean</ejb-name> <method-name>*</method-name> </method> <trans-attribute>Required</trans-attribute> </container-transaction> <container-transaction> <method> <ejb-name>TestBean</ejb-name> <method-intf>Timer</method-intf> <method-name>*</method-name> </method> <trans-attribute>NotSupported</trans-attribute> </container-transaction> {code} Only timer methods have tx attr not supported, and all other methods have tx attr required. Currently with as-7, the second container-transaction overwrites the first one, resulting in all methods have tx attr not supported. -- 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

12 years, 12 months

1
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2012