December 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SECURITY-769) Initialize AbstractServerLoginModule#validOptions with correct size

by Philippe Marschall (JIRA)

[ https://issues.jboss.org/browse/SECURITY-769?page=com.atlassian.jira.plug... ] Philippe Marschall resolved SECURITY-769. ----------------------------------------- Resolution: Done Pull request has been merged. > Initialize AbstractServerLoginModule#validOptions with correct size > ------------------------------------------------------------------- > > Key: SECURITY-769 > URL: https://issues.jboss.org/browse/SECURITY-769 > Project: PicketBox > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: JBossSX > Reporter: Philippe Marschall > Assignee: Stefan Guilhen > Fix For: PicketBox_4_0_20.Final > > > {{AbstractServerLoginModule#validOptions}} is initialized with the default {{HashSet}} size (which is the default {{HashMap}}) size. However since it's lazily initialized in {{addValidOptions}} and we have the valid module options there we know what the right size will be. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2533) Add ability to set default character encoding on a subsystem level

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-2533?page=com.atlassian.jira.plugin.... ] Tomaz Cerar updated WFLY-2533: ------------------------------ Comment: was deleted (was: Vielen Dank für Ihre Nachricht. Ich bin aktuell nicht im Büro und werde am Montag, den 13. Januar 2014 zurückkehren. Nachrichten die eine Antwort benötigen werde ich dann beantworten. Markus Karnik === Thank you for your email. I am away from the office and will return on Monday, January 13, 2014. If your message requires a reply, I will respond when I return. Markus Karnik ) > Add ability to set default character encoding on a subsystem level > ------------------------------------------------------------------ > > Key: WFLY-2533 > URL: https://issues.jboss.org/browse/WFLY-2533 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Web (Undertow) > Reporter: Stuart Douglas > Assignee: Tomaz Cerar > Fix For: 8.0.0.CR1 > > > Stuart: the charset one should be pretty simple, just an attribute on <servlet-container? > Stuart: ideally we would also have it in jboss-web.xml as well > Stuart: I should also add an option to use the connector encoding > Stuart: as connectors have their own encoding set > Stuart: that is used to decode the URL > Stuart: we should have an option to use the connector encoding as the default encoding -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2533) Add ability to set default character encoding on a subsystem level

by Markus Karnik (JIRA)

[ https://issues.jboss.org/browse/WFLY-2533?page=com.atlassian.jira.plugin.... ] Markus Karnik commented on WFLY-2533: ------------------------------------- Vielen Dank für Ihre Nachricht. Ich bin aktuell nicht im Büro und werde am Montag, den 13. Januar 2014 zurückkehren. Nachrichten die eine Antwort benötigen werde ich dann beantworten. Markus Karnik === Thank you for your email. I am away from the office and will return on Monday, January 13, 2014. If your message requires a reply, I will respond when I return. Markus Karnik > Add ability to set default character encoding on a subsystem level > ------------------------------------------------------------------ > > Key: WFLY-2533 > URL: https://issues.jboss.org/browse/WFLY-2533 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Web (Undertow) > Reporter: Stuart Douglas > Assignee: Tomaz Cerar > Fix For: 8.0.0.CR1 > > > Stuart: the charset one should be pretty simple, just an attribute on <servlet-container? > Stuart: ideally we would also have it in jboss-web.xml as well > Stuart: I should also add an option to use the connector encoding > Stuart: as connectors have their own encoding set > Stuart: that is used to decode the URL > Stuart: we should have an option to use the connector encoding as the default encoding -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2533) Add ability to set default character encoding on a subsystem level

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-2533?page=com.atlassian.jira.plugin.... ] Tomaz Cerar commented on WFLY-2533: ----------------------------------- Yes it was bug in parser, not sure how I missed that. Added a test to address that. PR with a fix https://github.com/wildfly/wildfly/pull/5651 > Add ability to set default character encoding on a subsystem level > ------------------------------------------------------------------ > > Key: WFLY-2533 > URL: https://issues.jboss.org/browse/WFLY-2533 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Web (Undertow) > Reporter: Stuart Douglas > Assignee: Tomaz Cerar > Fix For: 8.0.0.CR1 > > > Stuart: the charset one should be pretty simple, just an attribute on <servlet-container? > Stuart: ideally we would also have it in jboss-web.xml as well > Stuart: I should also add an option to use the connector encoding > Stuart: as connectors have their own encoding set > Stuart: that is used to decode the URL > Stuart: we should have an option to use the connector encoding as the default encoding -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBASM-43) jsch object can not be created

by ali ahmed (JIRA)

ali ahmed created JBASM-43: ------------------------------ Summary: jsch object can not be created Key: JBASM-43 URL: https://issues.jboss.org/browse/JBASM-43 Project: JBoss AS Server Manager Issue Type: Bug Reporter: ali ahmed Assignee: Shelly McGowan create a singleton ejb that contains a scheduler method which tries to create Jsch object (to create a session to list directories). the debug hangs and no exception is thrown. tried using of jsch-0.1.40 and jsch-0.1.50 and same result -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (EJBTHREE-2302) When using Weld the backing EJB is called 27 times.

by Robb Greathouse (JIRA)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-364) ClasspathKieProject fails vfs: path for jar deployments and exploded ear

by Nicolas-Xavier Vanderlinden (JIRA)

[ https://issues.jboss.org/browse/DROOLS-364?page=com.atlassian.jira.plugin... ] Nicolas-Xavier Vanderlinden updated DROOLS-364: ----------------------------------------------- Environment: JBoss AS 7.1.1 > ClasspathKieProject fails vfs: path for jar deployments and exploded ear > ------------------------------------------------------------------------ > > Key: DROOLS-364 > URL: https://issues.jboss.org/browse/DROOLS-364 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.0.0.Final > Environment: JBoss AS 7.1.1 > Reporter: Nicolas-Xavier Vanderlinden > Assignee: Mark Proctor > > Drools is not able to load kmodule.xml from an exploded ear. > 17:24:45,116 WARN Unable to load pom.properties tried recursing down from\Project\Geline\jboss-as-7.1.1.Final\standalone\deployments\geline.ear\service-impl-1.4.0-SNAPcontent > null > 17:24:45,116 ERROR Unable to build index of kmodule.xml url=vfs:/E:/Project/Geline/jboss-as-7.1.1.Final/standalone/deployments/geline.ear/service-impl-1.4.0-SNAPSHOT.jar/META-INF/kmodule.xml > 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, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-386) CommandFactoryServiceImpl cannot be cast to CommandFactoryService

by Nicolas-Xavier Vanderlinden (JIRA)

[ https://issues.jboss.org/browse/DROOLS-386?page=com.atlassian.jira.plugin... ] Nicolas-Xavier Vanderlinden commented on DROOLS-386: ---------------------------------------------------- {code} private static void loadProvider() { try { Class<CommandFactoryService> cls = (Class<CommandFactoryService>) Class.forName( "org.drools.core.command.impl.CommandFactoryServiceImpl" ); setCommandFactoryProvider( cls.newInstance() ); } catch ( Exception e2 ) { throw new RuntimeException( "Provider org.drools.core.command.impl.CommandFactoryProviderImpl could not be set.", e2 ); } } private static synchronized void setCommandFactoryProvider(CommandFactoryService provider) { CommandFactory.provider = provider; } {code} {code} public class CommandFactoryServiceImpl implements KieCommands { {code} > CommandFactoryServiceImpl cannot be cast to CommandFactoryService > ----------------------------------------------------------------- > > Key: DROOLS-386 > URL: https://issues.jboss.org/browse/DROOLS-386 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.0.0.Final > Environment: JBoss AS 7.1.1 > Reporter: Nicolas-Xavier Vanderlinden > Assignee: Mark Proctor > > Caused by: java.lang.ClassCastException: org.drools.core.command.impl.CommandFactoryServiceImpl cannot be cast to org.drools.command.CommandFactoryService > at org.drools.command.CommandFactory.loadProvider(CommandFactory.java:372) [knowledge-api-6.0.1.Final.jar:6.0.1.Final] > CommandFactoryServiceImpl does not implement CommandFactoryService -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-386) CommandFactoryServiceImpl cannot be cast to CommandFactoryService

by Nicolas-Xavier Vanderlinden (JIRA)

Nicolas-Xavier Vanderlinden created DROOLS-386: -------------------------------------------------- Summary: CommandFactoryServiceImpl cannot be cast to CommandFactoryService Key: DROOLS-386 URL: https://issues.jboss.org/browse/DROOLS-386 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 6.0.0.Final Environment: JBoss AS 7.1.1 Reporter: Nicolas-Xavier Vanderlinden Assignee: Mark Proctor Caused by: java.lang.ClassCastException: org.drools.core.command.impl.CommandFactoryServiceImpl cannot be cast to org.drools.command.CommandFactoryService at org.drools.command.CommandFactory.loadProvider(CommandFactory.java:372) [knowledge-api-6.0.1.Final.jar:6.0.1.Final] CommandFactoryServiceImpl does not implement CommandFactoryService -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2681) HTTP Management Interface Content-Type header is broken

by Dino Tsoumakis (JIRA)

Dino Tsoumakis created WFLY-2681: ------------------------------------ Summary: HTTP Management Interface Content-Type header is broken Key: WFLY-2681 URL: https://issues.jboss.org/browse/WFLY-2681 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: Domain Management Affects Versions: 8.0.0.CR1 Reporter: Dino Tsoumakis Assignee: Brian Stansberry Fix For: 8.0.0.Final *Problem:* HTTP Domain Management Interfaces returns invalid Content-Type header: {code} Content-Type: application/json;utf-8 {code} This breaks management for lots of REST clients. *Proposed solution:* According to [W3C|https://www.w3.org/International/O-HTTP-charset] and [rfc2616|http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.7] the Content-Type header should be: {code} Content-Type: application/json; charset=utf-8 {code} BTW: JBoss 7.1.1 behaviour is ok. It does not send any charset parameter at all. *Example:* Request contains the following headers: {code} 3 > Accept: application/json 3 > Content-Type: application/json ... {code} Wildfly 8.0.0.CR1 response after digest authentication is: {code} 4 < 200 4 < Authentication-Info: nextnonce="EB9WbpMrUuwNMTM4NzY3MDc2NzAxMgXaHXwaKEWPxbxUj1ihuOg=" 4 < Connection: keep-alive 4 < Content-Type: application/json;utf-8 4 < Transfer-Encoding: chunked {code} JBoss 7.1.1 response after digest authentication is: {code} 4 < 200 4 < Content-type: application/json 4 < Date: Sat, 21 Dec 2013 23:48:36 GMT 4 < Transfer-encoding: chunked {code} -- 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, 6 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 December 2013