April 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-96) Unification Iterator is broken

by Mark Proctor (JIRA)

Mark Proctor created DROOLS-96: ---------------------------------- Summary: Unification Iterator is broken Key: DROOLS-96 URL: https://issues.jboss.org/browse/DROOLS-96 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Mark Proctor Assignee: Mark Proctor -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (AS7-514) Per-deployment logging configuration

by Rohan Emmanuel (JIRA)

[ https://issues.jboss.org/browse/AS7-514?page=com.atlassian.jira.plugin.sy... ] Rohan Emmanuel commented on AS7-514: ------------------------------------ i created a logging.properties and put it in META-INF folder for the .jar file and deployed, the specific log file is being created ,but app is not logging anything into it.. > Per-deployment logging configuration > ------------------------------------ > > Key: AS7-514 > URL: https://issues.jboss.org/browse/AS7-514 > Project: Application Server 7 > Issue Type: Enhancement > Components: Logging > Reporter: David Lloyd > Assignee: James Perkins > Fix For: 7.1.2.Final (EAP) > > > Add a deployment descriptor for per-deployment logging. Should also support user-defined handler (JUL) and appender (log4j) configurations. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (AS7-514) Per-deployment logging configuration

by Will Tatam (JIRA)

[ https://issues.jboss.org/browse/AS7-514?page=com.atlassian.jira.plugin.sy... ] Will Tatam commented on AS7-514: -------------------------------- Yes, just create logging.properties, jboss-logging.properties, log4j.properties, log4j.xml or jboss-log4j.xml following normal log4j style config rules inside your META-INF or WEB-INF directories > Per-deployment logging configuration > ------------------------------------ > > Key: AS7-514 > URL: https://issues.jboss.org/browse/AS7-514 > Project: Application Server 7 > Issue Type: Enhancement > Components: Logging > Reporter: David Lloyd > Assignee: James Perkins > Fix For: 7.1.2.Final (EAP) > > > Add a deployment descriptor for per-deployment logging. Should also support user-defined handler (JUL) and appender (log4j) configurations. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (AS7-514) Per-deployment logging configuration

by Rohan Emmanuel (JIRA)

[ https://issues.jboss.org/browse/AS7-514?page=com.atlassian.jira.plugin.sy... ] Rohan Emmanuel commented on AS7-514: ------------------------------------ is there is any example demonstrating how to configure per-deployment logging? > Per-deployment logging configuration > ------------------------------------ > > Key: AS7-514 > URL: https://issues.jboss.org/browse/AS7-514 > Project: Application Server 7 > Issue Type: Enhancement > Components: Logging > Reporter: David Lloyd > Assignee: James Perkins > Fix For: 7.1.2.Final (EAP) > > > Add a deployment descriptor for per-deployment logging. Should also support user-defined handler (JUL) and appender (log4j) configurations. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (AS7-6725) <security><application/></security> for a RA should give PoolByCRI

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6725?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-6725: ---------------------------------------------- Vladimir Rastseluev <vrastsel(a)redhat.com> made a comment on [bug 921121|https://bugzilla.redhat.com/show_bug.cgi?id=921121] Verified on EAP 6.1 ER4 > <security><application/></security> for a RA should give PoolByCRI > ------------------------------------------------------------------- > > Key: AS7-6725 > URL: https://issues.jboss.org/browse/AS7-6725 > Project: Application Server 7 > Issue Type: Bug > Components: JCA > Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final) > Reporter: Stefano Maestri > Assignee: Stefano Maestri > Priority: Critical > 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (AS7-6725) <security><application/></security> for a RA should give PoolByCRI

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6725?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-6725: ---------------------------------------------- Vladimir Rastseluev <vrastsel(a)redhat.com> changed the Status of [bug 921121|https://bugzilla.redhat.com/show_bug.cgi?id=921121] from ON_QA to VERIFIED > <security><application/></security> for a RA should give PoolByCRI > ------------------------------------------------------------------- > > Key: AS7-6725 > URL: https://issues.jboss.org/browse/AS7-6725 > Project: Application Server 7 > Issue Type: Bug > Components: JCA > Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final) > Reporter: Stefano Maestri > Assignee: Stefano Maestri > Priority: Critical > 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (AS7-370) Add Notification support to the domain management API

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/AS7-370?page=com.atlassian.jira.plugin.sy... ] Jeff Mesnil updated AS7-370: ---------------------------- Comment: was deleted (was: development branch: https://github.com/jmesnil/jboss-as/compare/AS7-370_notification) > Add Notification support to the domain management API > ----------------------------------------------------- > > Key: AS7-370 > URL: https://issues.jboss.org/browse/AS7-370 > Project: Application Server 7 > Issue Type: Feature Request > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Jeff Mesnil > Fix For: 8.0.0.Alpha1 > > > Management resource should be able to emit notifications; clients can register listeners. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (AS7-6428) Using Session Scope CDI bean does not work in a HttpSessionListener

by Jozef Hartinger (JIRA)

[ https://issues.jboss.org/browse/AS7-6428?page=com.atlassian.jira.plugin.s... ] Jozef Hartinger commented on AS7-6428: -------------------------------------- The test passes using Undertow ;-) > Using Session Scope CDI bean does not work in a HttpSessionListener > ------------------------------------------------------------------- > > Key: AS7-6428 > URL: https://issues.jboss.org/browse/AS7-6428 > Project: Application Server 7 > Issue Type: Bug > Components: CDI / Weld > Affects Versions: 7.1.1.Final > Environment: linux 64bits, win7 64 bits > Reporter: nicolas marchais > Assignee: Remy Maucherat > Fix For: No Release > > > JBoss AS 7.1.x has a bug with using session bean scope in a HttpSessionListener. > When i inject a session scope bean in a HttpSessionListener and i try to populate attribute in sessionCreated() method many HttpSession are created by JBoss AS. Is it normal the a web server create many Http session for the same request ? > Normally, this behaviour should work. See : http://docs.jboss.org/cdi/api/1.1-PRD/javax/enterprise/context/SessionSco... > I did a light Web Project to explain the problem with 1 JSP, 1 SessionScope bean and 1 HttpSessionListener. > Here is the code. > JSP page : > <%@ page language="java" contentType="text/html; charset=UTF-8" > pageEncoding="UTF-8"%> > <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> > <html> > <head> > <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> > <title>Insert title here</title> > </head> > <body> > </body> > </html> > SessionScope bean : > @Named > @SessionScoped > public class UserState implements Serializable { > private int state; > public int getState() { > return state; > } > public void setState(int state) { > this.state = state; > } > } > HttpSessionListener : > @WebListener > public class SessionListener implements HttpSessionListener { > @Inject private UserState userState; > > @Override > public void sessionCreated(HttpSessionEvent event) { > System.out.println("New HTTP Session created : " + event.getSession().getId()); > userState.setState(2); > } > @Override > public void sessionDestroyed(HttpSessionEvent event) {} > } > After execution, you can read in the console at least 2 http session creation like this : > New HTTP Session created : zvlF6vGLP1AaXM-rzFU02wAJ.undefined > New HTTP Session created : TlrmmA8Eu4v32SHDT0QBBZza.undefined > The first session seams to be the one which is used by the client. There is one more problem : The polutated attributes of the session scope bean are ignored after HttpSessionListener execution. At the end all session scope attributes are null. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBMETA-349) EJB 2.0 ejb-jar.xml parser fails on message-driven/acknowledge-mode element

by SBS JIRA Integration (JIRA)

[ https://issues.jboss.org/browse/JBMETA-349?page=com.atlassian.jira.plugin... ] SBS JIRA Integration updated JBMETA-349: ---------------------------------------- Forum Reference: https://community.jboss.org/message/642113#642113, https://community.jboss.org/message/806460#806460, https://community.jboss.org/thread/176290?tstart=0 (was: https://community.jboss.org/message/642113#642113, https://community.jboss.org/thread/176290?tstart=0) > EJB 2.0 ejb-jar.xml parser fails on message-driven/acknowledge-mode element > --------------------------------------------------------------------------- > > Key: JBMETA-349 > URL: https://issues.jboss.org/browse/JBMETA-349 > Project: JBoss Metadata > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: ejb > Affects Versions: 7.0.0.Final > Reporter: Stephen Coy > Assignee: Carlo de Wolf > > The acknowledge-mode element was removed from the schema between -EJB 2.1 and EJB 3.0- EJB 2.0 and EJB 2.1 as it was replaced by an activation-config property. > > org.jboss.metadata.ejb.parser.spec.AbstractMessageDrivenBeanParser.processElement(MD, XMLStreamReader) does not look for it at all. > [edit: the description referenced the wrong spec versions] -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (AS7-5859) welcome content contains redhat properitary branding elements

by Bernd Eckenfels (JIRA)

[ https://issues.jboss.org/browse/AS7-5859?page=com.atlassian.jira.plugin.s... ] Bernd Eckenfels commented on AS7-5859: -------------------------------------- Any news on this? I noticed that the EAP Alpha does ship a different welcome (and error) content and delets that image, so there is even less reason to keep the RedHat logo in the community source (of AS8). > welcome content contains redhat properitary branding elements > ------------------------------------------------------------- > > Key: AS7-5859 > URL: https://issues.jboss.org/browse/AS7-5859 > Project: Application Server 7 > Issue Type: Bug > Reporter: Bernd Eckenfels > Labels: branding, community, design, license, logo, trademark > > The welcome content in the community repository does contain a RedHat logo. It actually even contains the text "by redhat" which is according to the license guidelines reserved for the EAP version. I think the branding should be removed since otherwise it makes even forking/repackaing for the JBoss AS hard: > https://github.com/jbossas/jboss-as/blob/master/build/src/main/resources/... > (also note that the file name is pretty missleading to, as it is not the community logo (alone)). -- 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, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2013