axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Davanum Srinivas (JIRA)" <>
Subject [jira] Created: (AXIS2-682) Problems testing Axis2 1.0 with Oracle OC4J (9.0.4)
Date Sat, 06 May 2006 03:33:27 GMT
Problems testing Axis2 1.0 with Oracle OC4J (9.0.4) 

         Key: AXIS2-682
     Project: Apache Axis 2.0 (Axis2)
        Type: Bug

    Reporter: Davanum Srinivas


I copied the content of axis2.war into a web application and run it from
the OC4J container (9.0.4) from JDeveloper
I noticed the following problems:

1. Because we have an 'error.jsp' file and an 'Error' subdirectory in
the axis2-web directory, the jsp compiler reports an error:
Error: package and class have same name: _axis2_2d_web._error

Resolution: rename the directory 'Error' to 'Errors' and change the
error-page urls in the web.xml accordingly.

2. When I click on the 'Services' link on the Welcome page,  the
contenttype of the result page is text/plain instead of text/html, so I
get the page source in Firefox. The same behavior in all pages that are
generated using the request.getRequestDispatcher(jspname).include().
Putting the following line before the dispatching in the renderView
method of the AbstractAgent class resolves the problem:


3. Getting the wsdl of the 'version' service on the service list page
(url: context-root/services/version?wsdl) displays an error:
Requested resource not found!

This is because the line 87 in ListingAgent does not detect the wsdl
request parameter:
httpServletRequest.getParameter("wsdl") returns null in OC4J
(request.getParameterNames() returns an empty enumeration).
Calling with context-root/services/version?wsdl=x will return the wsdl.

I have never used jsp with OC4J before (we use Velocity), so I think the
OC4J gurus can comment these issues and hopefully can find better solutions.

One more strange code fragment in (around line 114):

           // Handling the response
           AxisMessage outaxisMessage =
           if (inaxisMessage != null) {
               messageNameSpace =

instead of checking  inaxisMessage != null probably we should check
outaxisMessage != null. I think the problem is the result of copy/pasting.


This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message