Hi Ruwan:

Yes it is consistent. I am attaching the resource "echoEndpoint.xml" here.
Please tell where I have to set the content type?

-Thanks
tanmay



Ruwan Linton wrote:
> 
> OK, I think the problem is the Content-Type, "text/html;
> charset=iso-8859-1"
> 
> Can you set the content type to be text/xml on the resource and see?
> 
> Thanks,
> Ruwan
> 
> On Fri, Jun 20, 2008 at 7:08 AM, Ruwan Linton <[EMAIL PROTECTED]>
> wrote:
> 
>> Hi tanmay,
>>
>> Is this consistent? Please post the full log of synapse, theoretically it
>> should not lookup the registry second time and should get the resources
>> from
>> the local cache, because you have used them once?
>>
>> May be an issue with the char encoding in the system... please post the
>> full DEBUG log.
>>
>> Thanks,
>> Ruwan
>>
>>
>> On Fri, Jun 20, 2008 at 5:11 AM, tsaha <[EMAIL PROTECTED]>
>> wrote:
>>
>>>
>>> Hi Andreas:
>>>
>>> Thansk it solves the problem. But works only one time, 2nd time when I
>>> put
>>> another SOAP Pay load on TopicXA , I am getting the following error.
>>>
>>> Registry URI Syntax error reading from URL
>>> http://pasSCMdev/svn/incubator/wam-sy
>>> napse-registry/trunk/Endpoints/echoProxy/echoEndpoint.xml<http://pasSCMdev/svn/incubator/wam-synapse-registry/trunk/Endpoints/echoProxy/echoEndpoint.xml>
>>> java.net.URISyntaxException: Illegal character in path at index 10:
>>> text/html; c
>>> harset=iso-8859-1
>>>        at java.net.URI$Parser.fail(Unknown Source)
>>>        at java.net.URI$Parser.checkChars(Unknown Source)
>>>        at java.net.URI$Parser.parseHierarchical(Unknown Source)
>>>        at java.net.URI$Parser.parse(Unknown Source)
>>>        at java.net.URI.<init>(Unknown Source)
>>>        at
>>> org.apache.synapse.registry.url.SimpleURLRegistry.getRegistryEntry(Si
>>> mpleURLRegistry.java:142)
>>>        at
>>> org.apache.synapse.registry.AbstractRegistry.getResource(AbstractRegi
>>> stry.java:77)
>>>        at
>>> org.apache.synapse.config.SynapseConfiguration.getEndpoint(SynapseCon
>>> figuration.java:462)
>>>        at
>>> org.apache.synapse.core.axis2.Axis2MessageContext.getEndpoint(Axis2Me
>>> ssageContext.java:146)
>>>        at
>>> org.apache.synapse.endpoints.IndirectEndpoint.send(IndirectEndpoint.j
>>> ava:50)
>>>        at
>>> org.apache.synapse.core.axis2.ProxyServiceMessageReceiver.receive(Pro
>>> xyServiceMessageReceiver.java:179)
>>>        at
>>> org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:176)
>>>        at
>>> org.apache.synapse.transport.base.AbstractTransportListener.handleInc
>>> omingMessage(AbstractTransportListener.java:256)
>>>        at
>>> org.apache.synapse.transport.jms.JMSMessageReceiver$Worker.run(JMSMes
>>> sageReceiver.java:218)
>>>        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
>>> Source
>>> )
>>>        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown
>>> Source)
>>>        at java.lang.Thread.run(Unknown Source)
>>> 2008-06-19 16:36:28,639 [10.200.182.100-PS-TSAHA] [jms-Worker-4]  INFO
>>> LogMediat
>>> or To: , MessageID: ID:ffffffffcbed081a:2e080004:11AA32FAEB0, Direction:
>>> request
>>> , MESSAGE = Executing default "fault" sequence, ERROR_CODE = 00000,
>>> ERROR_MESSAG
>>> E = URI Syntax error reading from URL
>>> http://pasSCMdev/svn/incubator/wam-synapse
>>> -registry/trunk/Endpoints/echoProxy/echoEndpoint.xml<http://pasSCMdev/svn/incubator/wam-synapse-registry/trunk/Endpoints/echoProxy/echoEndpoint.xml>,
>>> Envelope: <?xml
>>> version='1
>>> .0' encoding='utf-8'?><soapenv:Envelope
>>> xmlns:soapenv="http://schemas.xmlsoap.or
>>> g/soap/envelope/"
>>> xmlns:ejb="http://ejbwebservice.westernasset.com/";><soapenv:Bo
>>> dy>
>>>      <ejb:echo>
>>>         <!--Optional:-->
>>>         <arg0>WA 6</arg0>
>>>      </ejb:echo>
>>>   </soapenv:Body></soapenv:Envelope>
>>>
>>> why it works only one time and I have not changed the echoEndpoint.xml ?
>>>
>>> thanks
>>> tanmay
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> Andreas Veithen wrote:
>>> >
>>> > Instead of using the "uri" attribute in the <publishWSDL> element, you
>>> > need to use "key" as in the other mediators.
>>> >
>>> > Andreas
>>> >
>>> > On 20 juin 08, at 00:51, tsaha wrote:
>>> >
>>> >>
>>> >> Can anybody pl tell how to make use of "Remote configuration via
>>> >> HTTP-based
>>> >> registries" ? I have added few endpoints, wsdls, xsl and etc into
>>> >> our SVN.
>>> >> Now I want my proxy to use those resources from SVN. My proxy
>>> >> configuration
>>> >> synapse_sample_regproxy.xml and svn trunk structure are attached
>>> here.
>>> >> <definitions xmlns="http://ws.apache.org/ns/synapse";>
>>> >>    <registry
>>> >> provider="org.apache.synapse.registry.url.SimpleURLRegistry">
>>> >>        <parameter
>>> >> name="root">http://devsvnhost/svn/incubator/wam-synapse-egistry/
>>> >> trunk/</parameter>
>>> >>        <parameter name="cachableDuration">15000</parameter>
>>> >>    </registry>
>>> >>
>>> >>    <proxy name="echoProxy" transports="jms">
>>> >>        <target>
>>> >>
>>> >>            <endpoint key="Endpoints/echoProxy/echoEndpoint.xml" />
>>> >>            <outSequence>
>>> >>                         <log level="full"/>
>>> >>                         <out>
>>> >>                              <xslt
>>> key="XSLT/echoProxy/echo_transform.xml"/>
>>> >>                         </out>
>>> >>        <clone>
>>> >>
>>> >>                 <target>
>>> >>                     <endpoint key="Endpoints/echoProxy/
>>> >> responseEndpointQ2.xml"
>>> >> />
>>> >>                 </target>
>>> >>
>>> >>                 <target>
>>> >>                  <endpoint key="Endpoints/echoProxy/
>>> >> responseEndpointQ3.xml" />
>>> >>                 </target>
>>> >>
>>> >>                 <target>
>>> >>                   <endpoint key="Endpoints/echoProxy/
>>> >> responseEndpointQ4.xml" />
>>> >>                </target>
>>> >>              </clone>
>>> >>           </outSequence>
>>> >>      </target>
>>> >>
>>> >>        <parameter
>>> >> name="transport.jms.ConnectionFactory">myTopicConnectionFactory</
>>> >> parameter>
>>> >>      <parameter name="transport.jms.Destination">TopicXA</parameter>
>>> >>        <parameter name="transport.jms.DestinationType">topic</
>>> >> parameter>
>>> >>        <publishWSDL uri="XSLT/echoProxy/echo_proxy.wsdl"/>
>>> >>      </proxy>
>>> >>
>>> >> </definitions>
>>> >>
>>> >> http://www.nabble.com/file/p18019866/svn_repo.bmp svn_repo.bmp
>>> >>
>>> >> But when I am starting the Synapse as "synapse -sample regproxy" , I
>>> >> am
>>> >> getting the following error
>>> >>
>>> >> roxyService Building Axis service for Proxy service : echoProxy
>>> >> 2008-06-19 15:50:24,324 [10.200.182.100-PS-TSAHA]
>>> >> [WrapperSimpleAppMain]
>>> >> FATAL S
>>> >> erverManager Synaps startup failed...
>>> >> java.lang.IllegalArgumentException: URI is not absolute
>>> >>        at java.net.URI.toURL(Unknown Source)
>>> >>        at
>>> >> org.apache.synapse.core.axis2.ProxyService.buildAxisService(ProxyServ
>>> >> ice.java:244)
>>> >>        at
>>> >> org.apache.synapse.core.axis2.SynapseInitializationModule.init(Synaps
>>> >> eInitializationModule.java:134)
>>> >>        at
>>> >> org.apache.axis2.context.ConfigurationContextFactory.initModules(Conf
>>> >> igurationContextFactory.java:226)
>>> >>        at
>>> >> org.apache.axis2.context.ConfigurationContextFactory.init(Configurati
>>> >> onContextFactory.java:204)
>>> >>        at
>>> >> org.apache.axis2.context.ConfigurationContextFactory.createConfigurat
>>> >> ionContext(ConfigurationContextFactory.java:80)
>>> >>        at
>>> >> org.apache.axis2.context.ConfigurationContextFactory.createConfigurat
>>> >> ionContextFromFileSystem(ConfigurationContextFactory.java:184)
>>> >>        at org.apache.synapse.ServerManager.start(ServerManager.java:
>>> >> 106)
>>> >>        at
>>> org.apache.synapse.SynapseServer.main(SynapseServer.java:81)
>>> >>        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> >>        at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
>>> >>        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
>>> >> Source)
>>> >>        at java.lang.reflect.Method.invoke(Unknown Source)
>>> >>        at
>>> >> org.tanukisoftware.wrapper.WrapperSimpleApp.run(WrapperSimpleApp.java
>>> >> :240)
>>> >>        at java.lang.Thread.run(Unknown Source)
>>> >>
>>> >> WrapperSimpleApp: Encountered an error running main:
>>> >> org.apache.synapse.SynapseE
>>> >> xception: Synapse startup failed
>>> >> org.apache.synapse.SynapseException: Synapse startup failed
>>> >>        at org.apache.synapse.ServerManager.start(ServerManager.java:
>>> >> 167)
>>> >>        at
>>> org.apache.synapse.SynapseServer.main(SynapseServer.java:81)
>>> >>        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> >>        at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
>>> >>        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
>>> >> Source)
>>> >>        at java.lang.reflect.Method.invoke(Unknown Source)
>>> >>        at
>>> >> org.tanukisoftware.wrapper.WrapperSimpleApp.run(WrapperSimpleApp.java
>>> >> :240)
>>> >>        at java.lang.Thread.run(Unknown Source)
>>> >> Caused by: java.lang.IllegalArgumentException: URI is not absolute
>>> >>        at java.net.URI.toURL(Unknown Source)
>>> >>
>>> >> Any idea how to configure this and make it working?
>>> >>
>>> >> -thanks
>>> >> tanmay
>>> >> --
>>> >> View this message in context:
>>> >>
>>> http://www.nabble.com/Remote-configuration-via-HTTP-based-registries-tp18019866p18019866.html
>>> >> Sent from the Synapse - User mailing list archive at Nabble.com.
>>> >>
>>> >
>>> >
>>> >
>>>
>>> --
>>> View this message in context:
>>> http://www.nabble.com/Remote-configuration-via-HTTP-based-registries-tp18019866p18020345.html
>>> Sent from the Synapse - User mailing list archive at Nabble.com.
>>>
>>>
>>
>>
>> --
>> Ruwan Linton
>> http://wso2.org - "Oxygenating the Web Services Platform"
>> http://ruwansblog.blogspot.com/
> 
> 
> 
> 
> -- 
> Ruwan Linton
> http://wso2.org - "Oxygenating the Web Services Platform"
> http://ruwansblog.blogspot.com/
> 
> 
http://www.nabble.com/file/p18073426/echoEndpoint.xml echoEndpoint.xml 
-- 
View this message in context: 
http://www.nabble.com/Remote-configuration-via-HTTP-based-registries-tp18019866p18073426.html
Sent from the Synapse - User mailing list archive at Nabble.com.

Reply via email to