[JBoss JIRA] (WFLY-2533) Add ability to set default character encoding on a subsystem level
by Norbert Kozłowski (JIRA)
[ https://issues.jboss.org/browse/WFLY-2533?page=com.atlassian.jira.plugin.... ]
Norbert Kozłowski commented on WFLY-2533:
-----------------------------------------
Works great. Thanks
> 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
[JBoss JIRA] (SECURITY-770) Support external password for keystore of PicketBoxVault implementation
by Ivo Studensky (JIRA)
[ https://issues.jboss.org/browse/SECURITY-770?page=com.atlassian.jira.plug... ]
Ivo Studensky reassigned SECURITY-770:
--------------------------------------
Assignee: Peter Skopek (was: Ivo Studensky)
I don't have commit permissions to the svn repository. Peter, could you commit it please?
> Support external password for keystore of PicketBoxVault implementation
> -----------------------------------------------------------------------
>
> Key: SECURITY-770
> URL: https://issues.jboss.org/browse/SECURITY-770
> Project: PicketBox
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: JBossSX
> Affects Versions: PicketBox_4_0_19.Final
> Reporter: Ivo Studensky
> Assignee: Peter Skopek
> Attachments: SECURITY-770_with_testcase_2.patch
>
>
> At the moment, the default implementation of Vault supports masked keystore password only. It would be nice to add a facility for external keystore password too so that customers can either define an external command to get the password or define their own class which provides a password for the keystore.
--
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
[JBoss JIRA] (SECURITY-770) Support external password for keystore of PicketBoxVault implementation
by Ivo Studensky (JIRA)
[ https://issues.jboss.org/browse/SECURITY-770?page=com.atlassian.jira.plug... ]
Ivo Studensky updated SECURITY-770:
-----------------------------------
Attachment: (was: SECURITY-770_with_testcase.patch)
> Support external password for keystore of PicketBoxVault implementation
> -----------------------------------------------------------------------
>
> Key: SECURITY-770
> URL: https://issues.jboss.org/browse/SECURITY-770
> Project: PicketBox
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: JBossSX
> Affects Versions: PicketBox_4_0_19.Final
> Reporter: Ivo Studensky
> Assignee: Ivo Studensky
> Attachments: SECURITY-770_with_testcase_2.patch
>
>
> At the moment, the default implementation of Vault supports masked keystore password only. It would be nice to add a facility for external keystore password too so that customers can either define an external command to get the password or define their own class which provides a password for the keystore.
--
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
[JBoss JIRA] (SECURITY-770) Support external password for keystore of PicketBoxVault implementation
by Ivo Studensky (JIRA)
[ https://issues.jboss.org/browse/SECURITY-770?page=com.atlassian.jira.plug... ]
Ivo Studensky updated SECURITY-770:
-----------------------------------
Attachment: SECURITY-770_with_testcase_2.patch
> Support external password for keystore of PicketBoxVault implementation
> -----------------------------------------------------------------------
>
> Key: SECURITY-770
> URL: https://issues.jboss.org/browse/SECURITY-770
> Project: PicketBox
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: JBossSX
> Affects Versions: PicketBox_4_0_19.Final
> Reporter: Ivo Studensky
> Assignee: Ivo Studensky
> Attachments: SECURITY-770_with_testcase.patch, SECURITY-770_with_testcase_2.patch
>
>
> At the moment, the default implementation of Vault supports masked keystore password only. It would be nice to add a facility for external keystore password too so that customers can either define an external command to get the password or define their own class which provides a password for the keystore.
--
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
[JBoss JIRA] (DROOLS-362) Make Drools work with Janino 2.6.1 and javax.tools API
by John Engelke (JIRA)
[ https://issues.jboss.org/browse/DROOLS-362?page=com.atlassian.jira.plugin... ]
John Engelke commented on DROOLS-362:
-------------------------------------
Apparently there are others suffering from this affliction, also: https://groups.google.com/forum/#!topic/cascading-user/q0zchNOwaoU
"The version of Janino that drools seems to work with is 2.5.16 where the CompileException Class is bundled with the jar. The version of the Janino that cascading 2.6.1 refactored those classes into its own jar under commons-compiler and I am Using drools 5.5.0-Final."
> Make Drools work with Janino 2.6.1 and javax.tools API
> ------------------------------------------------------
>
> Key: DROOLS-362
> URL: https://issues.jboss.org/browse/DROOLS-362
> Project: Drools
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Affects Versions: 5.5.0.Final, 6.0.0.Final
> Environment: JDK 1.7.0_45
> Reporter: John Engelke
> Assignee: Mark Proctor
> Labels: Drools, Janino
>
> Drools can be set to leverage the Janino "super-small, super-fast Java(TM) compiler." But it only works with version 2.5.16, not the latest version 2.6.1.
> Unfortunately, Janino does not support language features above 1.4/1.5 (partial 1.5).
> Version 2.6.1 includes an option to use the JDK built-in javax.tools.JavaCompiler: "JANINO can be configured to use javax.tools.JavaCompiler (available since JDK 1.6), i.e. JAVAC, which removes the Java 5-related limitations." [ See http://docs.codehaus.org/display/JANINO/Home#Home-what ] Unfortunately, this is only available when using the jars commons-compiler.jar and commons-compiler-jdk.jar, which are themselves only available in Janino 2.6.1. [ See http://docs.codehaus.org/display/JANINO/Advanced ]
> This is a nice little blocker for those of us who don't totally agree (or simply cannot agree) with the Eclipse license. Eclipse JDT is out. And, apparently, so is the double-diamond operator (until this is fixed)!
> Thanks.
--
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
[JBoss JIRA] (DROOLS-362) Make Drools work with Janino 2.6.1 and javax.tools API
by John Engelke (JIRA)
[ https://issues.jboss.org/browse/DROOLS-362?page=com.atlassian.jira.plugin... ]
John Engelke commented on DROOLS-362:
-------------------------------------
Here are some stack traces ...
Exception in thread "main" java.lang.ExceptionInInitializerError
...
Caused by: org.drools.RuntimeDroolsException: Unable to load dialect 'org.drools.rule.builder.dialect.java.JavaDialectConfiguration:java:org.drools.rule.builder.dialect.java.JavaDialectConfiguration'
at org.drools.compiler.PackageBuilderConfiguration.addDialect(PackageBuilderConfiguration.java:321)
at org.drools.compiler.PackageBuilderConfiguration.buildDialectConfigurationMap(PackageBuilderConfiguration.java:307)
at org.drools.compiler.PackageBuilderConfiguration.init(PackageBuilderConfiguration.java:192)
at org.drools.compiler.PackageBuilderConfiguration.<init>(PackageBuilderConfiguration.java:170)
at org.drools.builder.impl.KnowledgeBuilderFactoryServiceImpl.newKnowledgeBuilderConfiguration(KnowledgeBuilderFactoryServiceImpl.java:22)
at org.drools.builder.KnowledgeBuilderFactory.newKnowledgeBuilderConfiguration(KnowledgeBuilderFactory.java:74)
at com.foo.foo.rules.DroolsEngine.<clinit>(DroolsEngine.java:46)
... 7 more
Caused by: java.lang.RuntimeException: The Janino jar is not in the classpath
at org.drools.rule.builder.dialect.java.JavaDialectConfiguration.setCompiler(JavaDialectConfiguration.java:106)
at org.drools.rule.builder.dialect.java.JavaDialectConfiguration.init(JavaDialectConfiguration.java:61)
at org.drools.compiler.PackageBuilderConfiguration.addDialect(PackageBuilderConfiguration.java:317)
... 13 more
> Make Drools work with Janino 2.6.1 and javax.tools API
> ------------------------------------------------------
>
> Key: DROOLS-362
> URL: https://issues.jboss.org/browse/DROOLS-362
> Project: Drools
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Affects Versions: 5.5.0.Final, 6.0.0.Final
> Environment: JDK 1.7.0_45
> Reporter: John Engelke
> Assignee: Mark Proctor
> Labels: Drools, Janino
>
> Drools can be set to leverage the Janino "super-small, super-fast Java(TM) compiler." But it only works with version 2.5.16, not the latest version 2.6.1.
> Unfortunately, Janino does not support language features above 1.4/1.5 (partial 1.5).
> Version 2.6.1 includes an option to use the JDK built-in javax.tools.JavaCompiler: "JANINO can be configured to use javax.tools.JavaCompiler (available since JDK 1.6), i.e. JAVAC, which removes the Java 5-related limitations." [ See http://docs.codehaus.org/display/JANINO/Home#Home-what ] Unfortunately, this is only available when using the jars commons-compiler.jar and commons-compiler-jdk.jar, which are themselves only available in Janino 2.6.1. [ See http://docs.codehaus.org/display/JANINO/Advanced ]
> This is a nice little blocker for those of us who don't totally agree (or simply cannot agree) with the Eclipse license. Eclipse JDT is out. And, apparently, so is the double-diamond operator (until this is fixed)!
> Thanks.
--
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
[JBoss JIRA] (DROOLS-362) Make Drools work with Janino 2.6.1 and javax.tools API
by John Engelke (JIRA)
[ https://issues.jboss.org/browse/DROOLS-362?page=com.atlassian.jira.plugin... ]
John Engelke updated DROOLS-362:
--------------------------------
Description:
Drools can be set to leverage the Janino "super-small, super-fast Java(TM) compiler." But it only works with version 2.5.16, not the latest version 2.6.1.
Unfortunately, Janino does not support language features above 1.4/1.5 (partial 1.5).
Version 2.6.1 includes an option to use the JDK built-in javax.tools.JavaCompiler: "JANINO can be configured to use javax.tools.JavaCompiler (available since JDK 1.6), i.e. JAVAC, which removes the Java 5-related limitations." [ See http://docs.codehaus.org/display/JANINO/Home#Home-what ] Unfortunately, this is only available when using the jars commons-compiler.jar and commons-compiler-jdk.jar, which are themselves only available in Janino 2.6.1. [ See http://docs.codehaus.org/display/JANINO/Advanced ]
This is a nice little blocker for those of us who don't totally agree (or simply cannot agree) with the Eclipse license. Eclipse JDT is out. And, apparently, so is the double-diamond operator (until this is fixed)!
Thanks.
was:
Drools can be set to leverage the Janino "super-small, super-fast Java(TM) compiler." But it only works with version 2.5.16, not the latest version 2.6.1.
Unfortunately, Janino does not support language features above 1.4/1.5 (partial 1.5).
Version 2.6.1 includes an option to use the JDK build-in javax.tools.JavaCompiler: "JANINO can be configured to use javax.tools.JavaCompiler (available since JDK 1.6), i.e. JAVAC, which removes the Java 5-related limitations." [ See http://docs.codehaus.org/display/JANINO/Home#Home-what ] Unfortunately, this is only available when using the jars commons-compiler.jar and commons-compiler-jdk.jar, which are themselves only available in Janino 2.6.1. [ See http://docs.codehaus.org/display/JANINO/Advanced ]
This is a nice little blocker for those of us who don't totally agree (or simply cannot agree) with the Eclipse license. Eclipse JDT is out. And, apparently, so is the double-diamond operator (until this is fixed)!
Thanks.
> Make Drools work with Janino 2.6.1 and javax.tools API
> ------------------------------------------------------
>
> Key: DROOLS-362
> URL: https://issues.jboss.org/browse/DROOLS-362
> Project: Drools
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Affects Versions: 5.5.0.Final, 6.0.0.Final
> Environment: JDK 1.7.0_45
> Reporter: John Engelke
> Assignee: Mark Proctor
> Labels: Drools, Janino
>
> Drools can be set to leverage the Janino "super-small, super-fast Java(TM) compiler." But it only works with version 2.5.16, not the latest version 2.6.1.
> Unfortunately, Janino does not support language features above 1.4/1.5 (partial 1.5).
> Version 2.6.1 includes an option to use the JDK built-in javax.tools.JavaCompiler: "JANINO can be configured to use javax.tools.JavaCompiler (available since JDK 1.6), i.e. JAVAC, which removes the Java 5-related limitations." [ See http://docs.codehaus.org/display/JANINO/Home#Home-what ] Unfortunately, this is only available when using the jars commons-compiler.jar and commons-compiler-jdk.jar, which are themselves only available in Janino 2.6.1. [ See http://docs.codehaus.org/display/JANINO/Advanced ]
> This is a nice little blocker for those of us who don't totally agree (or simply cannot agree) with the Eclipse license. Eclipse JDT is out. And, apparently, so is the double-diamond operator (until this is fixed)!
> Thanks.
--
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
[JBoss JIRA] (DROOLS-362) Make Drools work with Janino 2.6.1 and javax.tools API
by John Engelke (JIRA)
John Engelke created DROOLS-362:
-----------------------------------
Summary: Make Drools work with Janino 2.6.1 and javax.tools API
Key: DROOLS-362
URL: https://issues.jboss.org/browse/DROOLS-362
Project: Drools
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 6.0.0.Final, 5.5.0.Final
Environment: JDK 1.7.0_45
Reporter: John Engelke
Assignee: Mark Proctor
Drools can be set to leverage the Janino "super-small, super-fast Java(TM) compiler." But it only works with version 2.5.16, not the latest version 2.6.1.
Unfortunately, Janino does not support language features above 1.4/1.5 (partial 1.5).
Version 2.6.1 includes an option to use the JDK build-in javax.tools.JavaCompiler: "JANINO can be configured to use javax.tools.JavaCompiler (available since JDK 1.6), i.e. JAVAC, which removes the Java 5-related limitations." [ See http://docs.codehaus.org/display/JANINO/Home#Home-what ] Unfortunately, this is only available when using the jars commons-compiler.jar and commons-compiler-jdk.jar, which are themselves only available in Janino 2.6.1. [ See http://docs.codehaus.org/display/JANINO/Advanced ]
This is a nice little blocker for those of us who don't totally agree (or simply cannot agree) with the Eclipse license. Eclipse JDT is out. And, apparently, so is the double-diamond operator (until this is fixed)!
Thanks.
--
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