I cant get to http://issues.apache.org/jira/browse/SYNAPSE  currently, seems
down

On Thu, Apr 24, 2008 at 7:37 PM, Ruwan Linton <[EMAIL PROTECTED]>
wrote:

> Wayne / Zarig,
>
> Could one of you please raise a JIRA for this on synapse, I will fix this
> ASAP...
>
> Thanks,
> Ruwan
>
> On Thu, Apr 24, 2008 at 10:36 PM, Wayne Keenan <[EMAIL PROTECTED]>
> wrote:
>
> > That's a hardcoded path in the callout mediator, I ment to raise a JIRA
> > but
> > forgot.  You coul din the meantime put in the missing dir and files
> >
> > On Thu, Apr 24, 2008 at 5:53 PM, khld zarig <[EMAIL PROTECTED]> wrote:
> >
> > > Hi,
> > > I just have a strange exception when I tried to use callout mediator:
> > >
> > > I tried to use synapse with callout mediator:
> > >
> > > However when I tried to use the same example (430) with
> > > synapse-war-1.1.1.war which is deployed in jboss AS 4.2.1, it throws
> > > Exception which is:
> > >
> > >
> > > 17:40:21,878 INFO  [STDOUT] 2008-04-24 17:40:21,878 [-] [main]  INFO
> > > SynapseInitializationModule Initializing Synapse at : Thu Apr 24
> > 17:40:21
> > > BST 2008
> > > 17:40:21,893 INFO  [STDOUT] 2008-04-24 17:40:21,893
> > > [128.240.150.106-morralee] [main]  INFO SynapseInitializationModule
> > Loading
> > > mediator extensions...
> > > 17:40:21,893 INFO  [STDOUT] 2008-04-24 17:40:21,893
> > > [128.240.150.106-morralee] [main]  INFO SynapseInitializationModule
> > > Initializing the Synapse configuration ...
> > > 17:40:21,893 INFO  [STDOUT] 2008-04-24 17:40:21,893
> > > [128.240.150.106-morralee] [main]  INFO XMLConfigurationBuilder
> > Generating
> > > the Synapse configuration model by parsing the XML configuration
> > > 17:40:22,752 INFO  [STDOUT] 2008-04-24 17:40:22,752
> > > [128.240.150.106-morralee] [main]  INFO SynapseConfigurationBuilder
> > Loaded
> > > Synapse configuration from :
> > >
> >
> Z:\jboss6_good\jboss-4.2.1.GA\server\all\.\tmp\deploy\tmp44289synapse-war-1.1.1-exp.war\\WEB-INF/conf\synapse.xml
> > > 17:40:22,768 INFO  [STDOUT] 2008-04-24 17:40:22,768
> > > [128.240.150.106-morralee] [main] ERROR CalloutMediator Error
> > initializing
> > > callout mediator : Couldn't find repository location
> > > './samples/axis2Client/client_repo'
> > > org.apache.axis2.AxisFault: Couldn't find repository location
> > > './samples/axis2Client/client_repo'
> > >        at
> > >
> >
> org.apache.axis2.deployment.FileSystemConfigurator.<init>(FileSystemConfigurator.java:67)
> > >        at
> > >
> >
> org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContextFromFileSystem(ConfigurationContextFactory.java:
> > > 180)
> > >        at
> > >
> >
> org.apache.synapse.mediators.builtin.CalloutMediator.init(CalloutMediator.java:173)
> > >        at
> > >
> >
> org.apache.synapse.mediators.AbstractListMediator.init(AbstractListMediator.java:107)
> > >        at
> > >
> >
> org.apache.synapse.mediators.base.SequenceMediator.init(SequenceMediator.java:192)
> > >        at
> > >
> >
> org.apache.synapse.config.SynapseConfiguration.init(SynapseConfiguration.java:785)
> > >        at
> > >
> >
> org.apache.synapse.core.axis2.SynapseInitializationModule.getConfiguration(SynapseInitializationModule.java:197)
> > >        at
> > >
> >
> org.apache.synapse.core.axis2.SynapseInitializationModule.init(SynapseInitializationModule.java:84)
> > >        at
> > >
> >
> org.apache.axis2.context.ConfigurationContextFactory.initModules(ConfigurationContextFactory.java:222)
> > >        at
> > >
> >
> org.apache.axis2.context.ConfigurationContextFactory.init(ConfigurationContextFactory.java:200)
> > >        at
> > >
> >
> org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:76)
> > >        at
> > >
> >
> org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContextFromFileSystem(ConfigurationContextFactory.java:
> > > 180)
> > >        at
> org.apache.synapse.ServerManager.start(ServerManager.java:86)
> > >        at
> > >
> >
> org.apache.synapse.core.axis2.SynapseStartUpServlet.init(SynapseStartUpServlet.java:90)
> > >        at
> > >
> >
> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1161)
> > >        at
> > >
> org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:981)
> > >        at
> > >
> >
> org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4069)
> > >        at
> > >
> >
> org.apache.catalina.core.StandardContext.start(StandardContext.java:4373)
> > >        at
> > >
> >
> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:761)
> > >        at
> > >
> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:741)
> > >        at
> > > org.apache.catalina.core.StandardHost.addChild(StandardHost.java:553)
> > >
> > >
> > > May I mention that, when synapse-war-1.1.1.war deployed in jbossAS
> 4.2.1
> > > with any other configuration file (synapse_sample_0.xml  -
> > >  synapse_sample_100.xml )
> > >  is working  fine, however with synapse_sample_430.xml it throws the
> > > mentioned Exception above…??
> > >
> > > Can any one please help in this??
> > >
> > > Thanks in advance
> > >
> > >
> > >
> > >
> > >
> > > Date: Tue, 22 Apr 2008 17:00:54 +0530From: [EMAIL PROTECTED]:
> > > [email protected]; [EMAIL PROTECTED]: Re: calling
> > external
> > > ws from synapse
> > > ZarigFirst of all you need to subscribe to the
> > [EMAIL PROTECTED] before you can post messages and receive
> > replies. I manually approved
> > > your mail through moderation, and copied this email to your private
> > mailbox
> > > this time :-)
> > > this is synapse.xml:
> > >
> > > ...
> > > <syn:class name="samples.mediators.test1"/>
> > > <syn:send>
> > > ...
> > > this is my mediator:
> > >
> > > ...        RPCServiceClient serviceClient = null;...The problem is
> that
> > > you are trying to use standard Axis2 to invoke the callout from within
> > your
> > > mediator, and then trying to send.. and this probably conflicts with
> the
> > > axis2 configuration initialized by the Synapse environment already
> > initiated
> > > by the way, i know callout mediator, however I think it can not
> satisfy
> > my
> > > requirements.
> > >  Why do you say that this does not satisfy your requirements? Can you
> > > elaborate your requirement a bit more.. The callout mediator performs
> a
> > > blocking send, while the send mediator will not block when using
> > > non-blocking transports such as the NIO based http/s.. These should
> > allow
> > > you to do almost any scenario without writing your own mediator to do
> a
> > > callback.. you typically would want to write a new mediator to perform
> a
> > > custom transformation (e.g. proprietary data formats) etc and not for
> > > sending out..asankha
> > > _________________________________________________________________
> > > Be a superhero and win! Play the Iron Man Mashup Game
> > > http://www.ironmanmashup.co.uk
> >
>
>
>
> --
> Ruwan Linton
> http://www.wso2.org - "Oxygenating the Web Services Platform"
>

Reply via email to