I updated axis2 code, rebuilt the standard distribution, ran WSDL2Java, and 
the Stubs still dechare in-only operations as OutOnlyAxisOperation in this 
way: 

    protected static org.apache.axis2.description.AxisOperation[] _operations;
    _operations = new org.apache.axis2.description.AxisOperation[5];
     __operation = new org.apache.axis2.description.OutOnlyAxisOperation();
     __operation.setName(...));
     _operations[0] = __operation;
     _service.addOperation(__operation);

   In the WSDL file, operations are defined this way:

        <wsdl:operation name="operation1">
                <wsdl:input message="tns:operation1InMessage"/>
        </wsdl:operation>


On Thursday 09 February 2006 04:25, Ajith Ranabahu wrote:
> This bug has been identified and already fixed!
>
> On 2/8/06, Rubén Naranjo Izquierdo <[EMAIL PROTECTED]> wrote:
> >    Hi,
> >
> >    I downloaded the latest codebase, tried the last code generator and
> > realised that in generated stubs (with "-g" option); in-only operations
> > are declared as "org.apache.axis2.description.OutOnlyAxisOperation". Is
> > this behaviour normal or we are dealing with a new bug?
> >
> >    Thanks!
> >
> >         Rubén Naranjo
> >
> > On Tuesday 07 February 2006 15:26, Ajith Ranabahu wrote:
> > > Hi Andreas,
> > > Yes this bug was realised recently and fixed in the latest codebase.
> > > Now the codegenerator generates correct message receivers based on the
> > > operation
> > >
> > > On 2/7/06, Andreas Bobek <[EMAIL PROTECTED]> wrote:
> > > > Hi,
> > > >
> > > > I have a very small WSDL file with only one in-only operation.
> > > > When running wsdl2java it generates a services.xml file with
> > > > mep="http://www.w3.org/2004/08/wsdl/in-out";
> > > > and a MessageReceiver class inheriting from
> > > > AbstractInOutSyncMessageReceiver.
> > > > As expected, when invoking the service with ClientAPI it sends back a
> > > > fault. At service side RawXMLINOnlyMessageReceiver is used instead of
> > > > the generated MessageReceiver class.
> > > >
> > > > Is this bug already known? I couldn't find another post.
> > > > Thanks, Andreas Bobek.
> > >
> > > --
> > > Ajith Ranabahu
>
> --
> Ajith Ranabahu

Reply via email to