[
https://issues.apache.org/jira/browse/AXIS2-3099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12518428
]
Jorge Fernández commented on AXIS2-3099:
----------------------------------------
Yes I have but don't worry.
Both problems are resolved with the RC released today.
I can use Jedit and axis2 detects rampart now.
Thanks,
Jorge Fernández
> Internal server error when modifying axis2.xml in axis2 1.3 war distribution
> ----------------------------------------------------------------------------
>
> Key: AXIS2-3099
> URL: https://issues.apache.org/jira/browse/AXIS2-3099
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: deployment
> Affects Versions: 1.3
> Environment: Windows XP SP2, Tomcat 6.0, Java 6.0
> Reporter: Jorge Fernández
> Priority: Critical
> Attachments: axis2-Jorge-edited-by-notepad.xml, axis2.xml,
> excepcion.txt
>
>
> Whenever I modify axis2.xml of the war distribution, I get an error page from
> listServices page or when I display an WSDL
> In Hapiness Page I see:
> Examinin Version Service:
> There was a problem in Axis2 version service , may be the service not
> available or some thing has gone wrong. But this does not mean system is not
> working ! Try to upload some other service and check to see whether it is
> working.
> For stoping that problem I have to backup and restore the original axis2.xml
> file that came in the war distribution
> When that happens I receive this at the client the message in the attached
> file when invoking the service.
> Also I can see that each time I run tomcat, my services.xml is updated,
> apparently with no changes but is modified on disk and the same happens with
> axis2.xml
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
