January 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-2707) Filter.destroy() not called for undeployment

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-2707?page=com.atlassian.jira.plugin.... ] Stuart Douglas reassigned WFLY-2707: ------------------------------------ Assignee: Stuart Douglas > Filter.destroy() not called for undeployment > -------------------------------------------- > > Key: WFLY-2707 > URL: https://issues.jboss.org/browse/WFLY-2707 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web (Undertow) > Affects Versions: 8.0.0.CR1 > Environment: CentOs/OpenJDK 7 > Reporter: Andre Pankraz > Assignee: Stuart Douglas > > ServletContextListener.contextDestroyed() is called reliably at undeployment time. > But the destroy() methods of javax.servlet.Filters are never called. > The filter is not explicetely in the web.xml, it's automatically detected and initialized via init() at deployment, but destroy() is never called. > JavaMelody cannot shutdown it's timers because of this: > See last remarks in http://code.google.com/p/javamelody/issues/detail?id=360 -- 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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2705) Unicode and Umlaut problems in Wildfly

by Andre Pankraz (JIRA)

[ https://issues.jboss.org/browse/WFLY-2705?page=com.atlassian.jira.plugin.... ] Andre Pankraz commented on WFLY-2705: ------------------------------------- Thanks for the hint, the workaround to explitely use the CharacterEncodingFilter and adding the CDI Filter behind this worked. Strange that it works for JBoss 7.2 and Wildfly with AJAX though. I hope there is a better solution in the future. I found some hints to the new attribute <servlet-container ... default-encoding="UTF-8"> but my version (from git yesterday) didn't know about it yet. Thanks again! > Unicode and Umlaut problems in Wildfly > -------------------------------------- > > Key: WFLY-2705 > URL: https://issues.jboss.org/browse/WFLY-2705 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: CDI / Weld > Affects Versions: 8.0.0.CR1 > Environment: CentOS > java version "1.7.0_45" > OpenJDK Runtime Environment (rhel-2.4.3.2.el6_4-x86_64 u45-b15) > Reporter: Andre Pankraz > Assignee: Jozef Hartinger > > I think I'm doing something wrong if this is really a CR1, but I cannot get UTF working properly on Wildfly. (It works fine in same environment and same settings/code in jboss-as-7.2.0.Final.) > * If i have an JSF inputText in a form (hence POST) > * and I enter "TestÜÖÄ" > * I get "TestÃ?Ã?Ã" as result. > If I provide a <f:ajax render...> on this field, the ajax rendering creates the proper response, but if I submit the data I always get the wrong encoded result. > I created a minimalistic web app without any additional libs with just one JSF test page (see below). It works in jboss as 7.2 final but not in Wildfly CR1. > I have set in the environment: > -Dsun.jnu.encoding=UTF-8 -Dfile.encoding=UTF-8 > An encoding filter didn't help either. > May be I'm doing something wrong here, but I have seen quite some other bugs that don't really speak for a "Release-Candidate" so it might really be an issue? Have you really tried to deploy at least 2 or 3 bigger JSF apps onto this new version? Will add some more reports. > Example page for quick test: > <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> > <f:view encoding="UTF-8" xmlns:f="http://java.sun.com/jsf/core"> > <html lang="de" xmlns="http://www.w3.org/1999/xhtml" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:ui="http://java.sun.com/jsf/facelets"> > <h:head> > <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> > <title>Test</title> > </h:head> > <h:body> > <h1>Test ÜÄÖ</h1> > <h:form id="test"> > <h:inputText label="Test: " value="#{test.test}"> > <f:ajax render=":test" /> > </h:inputText> > AJAX: #{test.test} > <br /> > <h:commandButton action="#{test.print()}" value="Print" /> > </h:form> > </h:body> > </html> > </f:view> > package test; > import javax.enterprise.context.RequestScoped; > import javax.inject.Named; > @Named > @RequestScoped > public class Test { > private String test; > public String getTest() { > return test; > } > public void setTest(String test) { > this.test = test; > } > public String print() { > System.out.println("TEST: " + getTest()); > return "success"; > } > } -- 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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2707) Filter.destroy() not called for undeployment

by Andre Pankraz (JIRA)

Andre Pankraz created WFLY-2707: ----------------------------------- Summary: Filter.destroy() not called for undeployment Key: WFLY-2707 URL: https://issues.jboss.org/browse/WFLY-2707 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 8.0.0.CR1 Environment: CentOs/OpenJDK 7 Reporter: Andre Pankraz ServletContextListener.contextDestroyed() is called reliably at undeployment time. But the destroy() methods of javax.servlet.Filters are never called. The filter is not explicetely in the web.xml, it's automatically detected and initialized via init() at deployment, but destroy() is never called. JavaMelody cannot shutdown it's timers because of this: See last remarks in http://code.google.com/p/javamelody/issues/detail?id=360 -- 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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2707) Filter.destroy() not called for undeployment

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-2707?page=com.atlassian.jira.plugin.... ] Tomaz Cerar updated WFLY-2707: ------------------------------ Component/s: Web (Undertow) > Filter.destroy() not called for undeployment > -------------------------------------------- > > Key: WFLY-2707 > URL: https://issues.jboss.org/browse/WFLY-2707 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web (Undertow) > Affects Versions: 8.0.0.CR1 > Environment: CentOs/OpenJDK 7 > Reporter: Andre Pankraz > > ServletContextListener.contextDestroyed() is called reliably at undeployment time. > But the destroy() methods of javax.servlet.Filters are never called. > The filter is not explicetely in the web.xml, it's automatically detected and initialized via init() at deployment, but destroy() is never called. > JavaMelody cannot shutdown it's timers because of this: > See last remarks in http://code.google.com/p/javamelody/issues/detail?id=360 -- 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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-392) KIE APIs do now allow to configure the Belief System type

by Davide Sottara (JIRA)

Davide Sottara created DROOLS-392: ------------------------------------- Summary: KIE APIs do now allow to configure the Belief System type Key: DROOLS-392 URL: https://issues.jboss.org/browse/DROOLS-392 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 6.0.0.Final Reporter: Davide Sottara Assignee: Mark Proctor BeliefSystemTypeOption is a valid SingleValueKieSessionOption, but the internal class SessionConfiguration ignores 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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-392) KIE APIs do not allow to configure the Belief System type

by Davide Sottara (JIRA)

[ https://issues.jboss.org/browse/DROOLS-392?page=com.atlassian.jira.plugin... ] Davide Sottara updated DROOLS-392: ---------------------------------- Summary: KIE APIs do not allow to configure the Belief System type (was: KIE APIs do now allow to configure the Belief System type) > KIE APIs do not allow to configure the Belief System type > --------------------------------------------------------- > > Key: DROOLS-392 > URL: https://issues.jboss.org/browse/DROOLS-392 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.0.0.Final > Reporter: Davide Sottara > Assignee: Mark Proctor > > BeliefSystemTypeOption is a valid SingleValueKieSessionOption, but the internal class SessionConfiguration ignores 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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-391) Support class literals with complex constraints and custom evaluators

by Davide Sottara (JIRA)

Davide Sottara created DROOLS-391: ------------------------------------- Summary: Support class literals with complex constraints and custom evaluators Key: DROOLS-391 URL: https://issues.jboss.org/browse/DROOLS-391 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 6.0.0.Final, 5.5.1.Final Reporter: Davide Sottara Assignee: Mario Fusco The following is supported, when A is a class name: {code} Pattern( this op A ) {code} But the following fails with a CCE {code} Pattern( this op A || this op B ) {code} when it tries to resolve A as a field of the class Pattern -- 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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2706) ServletContext.getServerInfo: Undertow instead of JBoss or Wildfly

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-2706?page=com.atlassian.jira.plugin.... ] Stuart Douglas updated WFLY-2706: --------------------------------- Assignee: Stuart Douglas > ServletContext.getServerInfo: Undertow instead of JBoss or Wildfly > ------------------------------------------------------------------ > > Key: WFLY-2706 > URL: https://issues.jboss.org/browse/WFLY-2706 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web (Undertow) > Affects Versions: 8.0.0.CR1 > Environment: CentOS, OpenJDK7 > Reporter: Andre Pankraz > Assignee: Stuart Douglas > > javax.servlet.ServletContext.getServerInfo() identifies Wildfly with: > "Undertow" and not with JBoss or Wildfly. Is this intentional? > Some frameworks or extensions (e.g. JavaMelody) use this server info to provide application server specific behaviour. > So Wildfly (or the newer JBoss AS) is quite different to past versions and this must not be the wrong step to tell something different here, but providing the embedded Servlet Container "Undertow" as response might not be intentional? > I would suggest to show something with "JBoss" even though Wildfly is the community version name (BTW great move...who wants to have wild flies in his data center...where is our swatter) > JavaMelody example code, triggered by HttpSessionListener.contextInitialized(ServletContextEvent event) -> initServletContext(event.getServletContext()): > void initServletContext(ServletContext context) { > assert context != null; > this.servletContext = context; > final String serverInfo = servletContext.getServerInfo(); > jboss = serverInfo.contains("JBoss") ; > glassfish = serverInfo.contains("GlassFish") > || serverInfo.contains("Sun Java System Application Server"); > weblogic = serverInfo.contains("WebLogic"); > jonas = System.getProperty("jonas.name") != 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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2705) Unicode and Umlaut problems in Wildfly

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-2705?page=com.atlassian.jira.plugin.... ] Stuart Douglas updated WFLY-2705: --------------------------------- Component/s: CDI / Weld (was: Web (Undertow)) > Unicode and Umlaut problems in Wildfly > -------------------------------------- > > Key: WFLY-2705 > URL: https://issues.jboss.org/browse/WFLY-2705 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: CDI / Weld > Affects Versions: 8.0.0.CR1 > Environment: CentOS > java version "1.7.0_45" > OpenJDK Runtime Environment (rhel-2.4.3.2.el6_4-x86_64 u45-b15) > Reporter: Andre Pankraz > Assignee: Jozef Hartinger > > I think I'm doing something wrong if this is really a CR1, but I cannot get UTF working properly on Wildfly. (It works fine in same environment and same settings/code in jboss-as-7.2.0.Final.) > * If i have an JSF inputText in a form (hence POST) > * and I enter "TestÜÖÄ" > * I get "TestÃ?Ã?Ã" as result. > If I provide a <f:ajax render...> on this field, the ajax rendering creates the proper response, but if I submit the data I always get the wrong encoded result. > I created a minimalistic web app without any additional libs with just one JSF test page (see below). It works in jboss as 7.2 final but not in Wildfly CR1. > I have set in the environment: > -Dsun.jnu.encoding=UTF-8 -Dfile.encoding=UTF-8 > An encoding filter didn't help either. > May be I'm doing something wrong here, but I have seen quite some other bugs that don't really speak for a "Release-Candidate" so it might really be an issue? Have you really tried to deploy at least 2 or 3 bigger JSF apps onto this new version? Will add some more reports. > Example page for quick test: > <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> > <f:view encoding="UTF-8" xmlns:f="http://java.sun.com/jsf/core"> > <html lang="de" xmlns="http://www.w3.org/1999/xhtml" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:ui="http://java.sun.com/jsf/facelets"> > <h:head> > <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> > <title>Test</title> > </h:head> > <h:body> > <h1>Test ÜÄÖ</h1> > <h:form id="test"> > <h:inputText label="Test: " value="#{test.test}"> > <f:ajax render=":test" /> > </h:inputText> > AJAX: #{test.test} > <br /> > <h:commandButton action="#{test.print()}" value="Print" /> > </h:form> > </h:body> > </html> > </f:view> > package test; > import javax.enterprise.context.RequestScoped; > import javax.inject.Named; > @Named > @RequestScoped > public class Test { > private String test; > public String getTest() { > return test; > } > public void setTest(String test) { > this.test = test; > } > public String print() { > System.out.println("TEST: " + getTest()); > return "success"; > } > } -- 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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2705) Unicode and Umlaut problems in Wildfly

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-2705?page=com.atlassian.jira.plugin.... ] Stuart Douglas resolved WFLY-2705. ---------------------------------- Assignee: Jozef Hartinger (was: Stuart Douglas) Resolution: Duplicate Issue Looks like you are hitting WFLY-2531 There are a couple of workarounds you can do. You can either map the CDI conversation filter, or set the default encoding to UTF-8 at either the server level or by using jboss-web.xml. Alternatively if you are not using CDI you can remove the weld subsystem or exclude it using jboss-deployment-structure.xml > Unicode and Umlaut problems in Wildfly > -------------------------------------- > > Key: WFLY-2705 > URL: https://issues.jboss.org/browse/WFLY-2705 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web (Undertow) > Affects Versions: 8.0.0.CR1 > Environment: CentOS > java version "1.7.0_45" > OpenJDK Runtime Environment (rhel-2.4.3.2.el6_4-x86_64 u45-b15) > Reporter: Andre Pankraz > Assignee: Jozef Hartinger > > I think I'm doing something wrong if this is really a CR1, but I cannot get UTF working properly on Wildfly. (It works fine in same environment and same settings/code in jboss-as-7.2.0.Final.) > * If i have an JSF inputText in a form (hence POST) > * and I enter "TestÜÖÄ" > * I get "TestÃ?Ã?Ã" as result. > If I provide a <f:ajax render...> on this field, the ajax rendering creates the proper response, but if I submit the data I always get the wrong encoded result. > I created a minimalistic web app without any additional libs with just one JSF test page (see below). It works in jboss as 7.2 final but not in Wildfly CR1. > I have set in the environment: > -Dsun.jnu.encoding=UTF-8 -Dfile.encoding=UTF-8 > An encoding filter didn't help either. > May be I'm doing something wrong here, but I have seen quite some other bugs that don't really speak for a "Release-Candidate" so it might really be an issue? Have you really tried to deploy at least 2 or 3 bigger JSF apps onto this new version? Will add some more reports. > Example page for quick test: > <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> > <f:view encoding="UTF-8" xmlns:f="http://java.sun.com/jsf/core"> > <html lang="de" xmlns="http://www.w3.org/1999/xhtml" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:ui="http://java.sun.com/jsf/facelets"> > <h:head> > <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> > <title>Test</title> > </h:head> > <h:body> > <h1>Test ÜÄÖ</h1> > <h:form id="test"> > <h:inputText label="Test: " value="#{test.test}"> > <f:ajax render=":test" /> > </h:inputText> > AJAX: #{test.test} > <br /> > <h:commandButton action="#{test.print()}" value="Print" /> > </h:form> > </h:body> > </html> > </f:view> > package test; > import javax.enterprise.context.RequestScoped; > import javax.inject.Named; > @Named > @RequestScoped > public class Test { > private String test; > public String getTest() { > return test; > } > public void setTest(String test) { > this.test = test; > } > public String print() { > System.out.println("TEST: " + getTest()); > return "success"; > } > } -- 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

10 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2014