axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Gainty" <>
Subject Re: Axis2 dispatcher and receiver
Date Fri, 20 Apr 2007 18:20:09 GMT

are you verified synapse has run thru all the published SI testcases with AXIS2 ?

(I did a quick run and see this displayed)

C:\Synapse\synapse-0.91\samples\axis2Client>ant stockquote

Buildfile: build.xml
    [mkdir] Created dir: C:\Synapse\synapse-0.91\samples\axis2Client\target\classes

    [javac] Compiling 10 source files to C:\Synapse\synapse-0.91\samples\axis2Cl
     [java] org.apache.axis2.AxisFault: SOAP message MUST NOT contain a Document
 Type Declaration(DTD); nested exception is:
     [java] SOAP message MUST NOT contain a
 Document Type Declaration(DTD)

I assume synapse is still in alpha ?

This email message and any files transmitted with it contain confidential
information intended only for the person(s) to whom this email message is
addressed.  If you have received this email message in error, please notify
the sender immediately by telephone or email and destroy the original
message without making a copy.  Thank you.

  ----- Original Message ----- 
  From: Soactive Inc 
  Sent: Friday, April 20, 2007 1:00 PM
  Subject: Re: Axis2 dispatcher and receiver

  Can you or someone else provide a step by step approach (concrete example) to use Synapse
to route to a simple external service without hardwiring any service information within the
Synapse configuration.

  I have tried to use Synapse but so far it doesn't seem to work for me. 

  On 4/20/07, Paul Fremantle <> wrote:

    You might like to take a look at Apache Synapse
    ( which is build on top of Axis2 and does
    exactly that.

    We have a flexible model where you can deploy any mediation before 
    routing the message on to an external service.


    On 4/19/07, Soactive Inc <> wrote:
    > I am trying to use axis2 to dispatch all requests to a particular service. 
    > This service also has a registered receiver which executes the appropriate
    > business logic (essentially calling other external services). All logic is
    > currently within the receiver and there is not much to be done in the actual 
    > service invoked by the dispatcher. I am faced with an issue where the
    > receiver is being called but not the service. Is there a particular
    > signature for the service operation that I need to use. Currently I use the 
    > following:
    > public boolean mediate(MessageContext synCtx) {...}
    > I am wondering why the receiver is invoked but not the actual service. Is
    > there a way to return / truncate processing directly from the receiver back 
    > to the caller?
    > Thanks in advance,
    > Ron

    Paul Fremantle
    VP/Technology, WSO2 and OASIS WS-RX TC Co-chair

    "Oxygenating the Web Service Platform",

    To unsubscribe, e-mail:
    For additional commands, e-mail: 

View raw message