Hi Paul The issue here is , we cannot build a OMNode from a text if it is doesn't represent a valid XML, even text had wrapped with CDATA . If the AXIOM adds this capability , then we can use the existing API. By the way , I believe that the registry API need to avoid tight coupling with AXIOM.
Thanks Indika On Tue, Apr 15, 2008 at 4:05 AM, Paul Fremantle <[EMAIL PROTECTED]> wrote: > Indika > > Can't an OMNode be an OMText? In which case the content can just be text? > > Paul > > On Mon, Apr 14, 2008 at 2:31 PM, indika kumara <[EMAIL PROTECTED]> > wrote: > > Hi Wayne, > > > > Whether the underlying registry is the wso2registry or simple URL > registry , > > synapse uses its registry API . The current registry API tightly > couples > > with OMNode as its API has a 'lookup' method which expects to be > returned a > > OMNode as the result. In order to support non-XML content as registry > > resources , it is needed refactoring the current API by removing OMNode > > dependency and providing more an abstract API. > > > > I will do the required changes. > > > > By the way , wso2registry is a dedicated product for the Registry space > , so > > , it will be an obvious alternative for the simple URL Registry. > > Currently,you cannot plug the wso2regustry in to the synapse but you > can use > > the wso2registry with the wso2 ESB(https://wso2.org/projects/esb/java) > which > > wraps the core as synapse as it is and provides a management console. > > > > Thanks > > Indika > > > > > > -- > Paul Fremantle > Co-Founder and CTO, WSO2 > Apache Synapse PMC Chair > OASIS WS-RX TC Co-chair > > blog: http://pzf.fremantle.org > [EMAIL PROTECTED] > > "Oxygenating the Web Service Platform", www.wso2.com >
