On Tue, Sep 15, 2009 at 9:51 AM, Rajesh_lakhotia <[email protected]>wrote:

>
> Where to get this snapshot ?
> Could you please direct me to the location.
>

Latest nightly available at :
http://hudson.zones.apache.org/hudson/job/Synapse%20-%20Trunk/lastStableBuild/org.apache.synapse$synapse-distribution/

Thanks,
Hiranya


>
>
> Hiranya Jayathilaka-3 wrote:
> >
> > On Tue, Sep 15, 2009 at 9:31 AM, Rajesh_lakhotia
> > <[email protected]>wrote:
> >
> >>
> >> Using Synapse 1.2  for routing.
> >>
> >> I have a wsdl which used few xsds. those included xsds also include and
> >> impre few other xsds.
> >> I am getting Namespace conflict error while starting the Synapse.
> >>
> >> I understand there was a JIRA created for this and it was supposed to be
> >> fix
> >> but it seems its not.
> >>
> >
> > Did you try this on a snapshot build? If not can you please try that out?
> > According to the JIRA the problem is fixed on the trunk. If the problem
> > still exists on the trunk please reopen the JIRA and post your WSDL and
> > XSD.
> >
> > Thanks,
> > Hiranya
> >
> >
> >> posted this under that but thought I should bump it up.
> >>
> >> http://www.nabble.com/forum/ViewPost.jtp?post=25437816&framed=y
> >>
> >> Can some one help....
> >>
> >> --
> >> View this message in context:
> >>
> http://www.nabble.com/XMLSchemaException-when-including-XSD-in-WSDL-tp25447466p25447466.html
> >> Sent from the Synapse - User mailing list archive at Nabble.com.
> >>
> >>
> >
> >
> > --
> > Hiranya Jayathilaka
> > Software Engineer;
> > WSO2 Inc.;  http://wso2.org
> > E-mail: [email protected];  Mobile: +94 77 633 3491
> > Blog: http://techfeast-hiranya.blogspot.com
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/XMLSchemaException-when-including-XSD-in-WSDL-tp25447466p25447595.html
> Sent from the Synapse - User mailing list archive at Nabble.com.
>
>


-- 
Hiranya Jayathilaka
Software Engineer;
WSO2 Inc.;  http://wso2.org
E-mail: [email protected];  Mobile: +94 77 633 3491
Blog: http://techfeast-hiranya.blogspot.com

Reply via email to