[JBoss JIRA] (WFLY-254) tomcatAuthentication attribute on the AJP connector
by Matthias W (JIRA)
[ https://issues.jboss.org/browse/WFLY-254?page=com.atlassian.jira.plugin.s... ]
Matthias W commented on WFLY-254:
---------------------------------
Is it possible to add the parameter requiredSecret via System-Properties?
ie. org.apache.coyote.ajp.AprProcessor.REQUIREDSECRET
Thanks
> tomcatAuthentication attribute on the AJP connector
> ---------------------------------------------------
>
> Key: WFLY-254
> URL: https://issues.jboss.org/browse/WFLY-254
> Project: WildFly
> Issue Type: Feature Request
> Components: Web (JBoss Web)
> Environment: Windows Server 2003 32 bit, IIS 6, tomcat connector 1.2.28 used as an extension
> Reporter: Brett Prucha
> Assignee: Jean-Frederic Clere
> Priority: Minor
> Fix For: 8.0.0.Alpha1
>
>
> In JBoss 5.1.0 I could set the tomcatAuthentication attribute of the AJP connector to false to allow IIS to handle the authentication and pass that along to JBoss. I'm wanting to upgrade to JBoss 7 but unable to set this attribute in version 7.0.0 final to make this work. This attribute is descibed in the tomcat documentation at http://tomcat.apache.org/tomcat-7.0-doc/config/ajp.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
13 years, 2 months
[JBoss JIRA] (JASSIST-196) Dont use ==, instead use .equals() for strings
by oliver z (JIRA)
oliver z created JASSIST-196:
--------------------------------
Summary: Dont use ==, instead use .equals() for strings
Key: JASSIST-196
URL: https://issues.jboss.org/browse/JASSIST-196
Project: Javassist
Issue Type: Quality Risk
Affects Versions: 3.17.1-GA
Reporter: oliver z
Assignee: Shigeru Chiba
I just used a code quality tool to scan my application which uses javassist.
It is complaining about a few "==" instead of .equals().
Occurance at least in: AccessorMaker.java:127
Would be nice if this could be fixed because as its a very little change.
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
13 years, 2 months
[JBoss JIRA] (WFLY-1293) Update License Header for KDCServerAnnotationProcessor
by Darran Lofthouse (JIRA)
Darran Lofthouse created WFLY-1293:
--------------------------------------
Summary: Update License Header for KDCServerAnnotationProcessor
Key: WFLY-1293
URL: https://issues.jboss.org/browse/WFLY-1293
Project: WildFly
Issue Type: Task
Components: Test Suite
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 8.0.0.Alpha1
The purpose of KDCServerAnnotationProcessor is to work around an initialisation problem using Apache Directory Server - however the class is actually based on an implementation in the Apache Directory Server project so the license needs updating to reflect this.
--
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
13 years, 2 months
[JBoss JIRA] (WFLY-1154) Allow the server to ignore files or groups of files at deployment time
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFLY-1154?page=com.atlassian.jira.plugin.... ]
Stuart Douglas updated WFLY-1154:
---------------------------------
Assignee: (was: Stuart Douglas)
Fix Version/s: Awaiting Volunteers
> Allow the server to ignore files or groups of files at deployment time
> ----------------------------------------------------------------------
>
> Key: WFLY-1154
> URL: https://issues.jboss.org/browse/WFLY-1154
> Project: WildFly
> Issue Type: Feature Request
> Components: Server
> Reporter: Marius Bogoevici
> Fix For: Awaiting Volunteers
>
>
> Legacy and migrated applications may occasionally contain files which are incompatible with the Java EE specification and can cause the application to fail the deployment. The difference between those cases and really faulty Java EE applications lies in the intent of the developer - whether they wish for those files to be picked up by the server and processed, or not.
> In such cases, it may be useful to expand the deployment specification and to be able to instruct the server to ignore particular files at deployment time.
--
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
13 years, 2 months