robert lazarski created AXIS2-5909:
--------------------------------------
Summary: happyaxis.jsp doesn't support httpclient4, doesn't pick
up custom WEB-INF/conf/axis2.xml
Key: AXIS2-5909
URL: https://issues.apache.org/jira/browse/AXIS2-5909
Project: Axis2
Issue Type: Bug
Affects Versions: 1.7.7
Reporter: robert lazarski
Axis2 1.7.x introduced the ability to use the httpclient4 libs instead of the
unsupported httpclient3 libs via changes to WEB-INF/conf/axis2.xml , however
those changes are not picked up in the following code in happyaxis.jsp:
ConfigurationContext configctx =
ConfigurationContextFactory.createConfigurationContextFromF
ileSystem(null, null);
If there are no httpclient3 libs in the WAR because they were purposely removed
and httpclient4 was configured as a replacement, the happyaxis.jsp validate
link will still attempt to load those httpclient3 classes. The result is:
java.lang.NoClassDefFoundError: org/apache/commons/httpclient
/HttpConnectionManager
The distributed axis2.war/WEB-INF/web.xml shows commented out args on
AxisServlet for the axis repo, but those didn't appear to help the
happyaxis.jsp loading of the validate link with httpclient4 configured.
This code tweak in happyaxis.jsp does seem to work. Any reason this code would
not be a good idea by default? And imho the axis2 team should also consider
removing httpclient3 support entirely for security reasons.
ConfigurationContext configctx =
ConfigurationContextFactory.createConfigurationContextFromF
ileSystem("/WEB-INF/conf", "axis2.xml");
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
