You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Paul Fremantle (JIRA)" <ax...@ws.apache.org> on 2005/03/14 23:59:09 UTC

[jira] Commented: (AXIS-1829) I'm using the documentation element in WSDD to store complex xml and it isn't handling CDATA properly

     [ http://issues.apache.org/jira/browse/AXIS-1829?page=comments#action_60794 ]
     
Paul Fremantle commented on AXIS-1829:
--------------------------------------

Its fixed.... in RC3. 

> I'm using the documentation element in WSDD to store complex xml and it isn't handling CDATA properly
> -----------------------------------------------------------------------------------------------------
>
>          Key: AXIS-1829
>          URL: http://issues.apache.org/jira/browse/AXIS-1829
>      Project: Axis
>         Type: Bug
>   Components: Deployment / Registries
>     Versions: 1.2RC1
>  Environment: WinXP, JDK1.4
>     Reporter: Paul Fremantle

>
> I have created a new provider, which works fine. However, I want to use the documentation element of the WSDD file to store information that includes embedded XML. Although I can use CDATA in the deploy.wsdd, when the WSDD gets serialised in server-config.wsdd it loses the CDATA wrapper and is no longer properly stored.
> I have effected a simple fix which is to always put <![CDATA[ and ]]> around the documentation elements in WSDD. To do this I added the two inserted lines (>>) into WSDDDocumentation.java:
>     public void writeToContext(SerializationContext context)
>             throws IOException
>     {
>         context.startElement(QNAME_DOC, null);
> >> 	context.writeString("<![CDATA[");
>         context.writeString(value);
> >>	context.writeString("]]>");
>         context.endElement();
>     }
> It works in my scenarios.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira