Hi Roshan,
we'll try AIX this morning - thanks..
John Hawkins
| Roshan Weerasuriya <[EMAIL PROTECTED]>
24/01/2005 08:22
|
|
hi John,
I made changes to SimpleAxisServer and not the build is fine. I took a
fresh chekout and applied the changes and commited it. Not it builds
fine on Linux, not sure abt AIX.
> I'm also confused becuase the implementations that I see return NULL -
> > are you going to finish these in time?
What are the implementatoins which return NULL?
> 1. Simple axis server appears to be failing - not had time to look
> > into.
Added the implementations of the virtual funtions
getIncomingSOAPMimeHeaders() and getAttachment() and commited. Not it
builds.
> 2. apachetransport.h - The method signatures were wrong (you're
> > returning ISoapAttachment now right?).
Now it returns ISoapAttachment* instead of a char*. This
ISoapAttachment* encapsulates the entire attachment including attachment
heades and the body.
>This was also true for axis
> > transport 3 which also failed.
Opps... yes. With your changes now it builds.
>This was also true for axis
> > transport 3 which also failed.
> > Please can you tell me what to return here - it's returning
> > NULL now but I'm guessing it shouldn't :-)
Nithya and Rangika has implemented support for attachments only at
Server side, for the moment. Any implementer who supports Attachments at
client side, will have to provide the correct implmentations for those
mehtods (which you have implemented to return NULL as a hack). So for
the moment it is OK to keep them to return NULL.
> 3. In apachetransport.h again - the getAttachments method use to
> > return "value" - was this a placeholder ? I've now made it return
> NULL
> > - please can you verify what it should be returning.
Nithya and Rangika have added Attachment support for the Apache2 module.
They will have to added the Attachment support for the Apache (1.x)
module as well.
4. getIncomingSOAPMimeHeaders - Should this be on the Transport
> > interface - isn't this transport specific? And - it returns NULL in
> > the implementation - what should it be
> >
Can you elaborate more on this?
Rgds,
Roshan
On Mon, 2005-01-24 at 03:12, John Hawkins wrote:
> AIX and linux.
>
> Windows is very worryingly forgiving !
>
> John Hawkins
>
>
>
>
> Roshan Weerasuriya
> <[EMAIL PROTECTED]>
>
> 22/01/2005 10:25
> Please respond to
> "Apache AXIS C Developers List"
> To
> Apache AXIS C
> Developers List
> <[email protected]>
> cc
>
> Subject
> Re: broken the
> build
>
>
>
>
> hi John,
>
> On which o/s the build fails, windows or linux?
>
> Roshan
>
> On Sat, 2005-01-22 at 00:36, John Hawkins wrote:
> > Hi Nithya,
> >
> > Your latest changes broke the build. I've committed some "fixes"
> which
> > I need to discuss here please.
> > Generally: I'm kinda confused by this - I thought we weren't going
> to
> > make changes for Attachments in 1.5?
> > I'm also confused becuase the implementations that I see return NULL
> -
> > are you going to finish these in time?
> >
> >
> > The issues I hacked out were ->
> >
> >
> > 1. Simple axis server appears to be failing - not had time to look
> > into.
> >
> >
> > 2. apachetransport.h - The method signatures were wrong (you're
> > returning ISoapAttachment now right?). This was also true for axis
> > transport 3 which also failed.
> > Please can you tell me what to return here - it's returning
> > NULL now but I'm guessing it shouldn't :-)
> > 3. In apachetransport.h again - the getAttachments method use to
> > return "value" - was this a placeholder ? I've now made it return
> NULL
> > - please can you verify what it should be returning.
> >
> > 4. getIncomingSOAPMimeHeaders - Should this be on the Transport
> > interface - isn't this transport specific? And - it returns NULL in
> > the implementation - what should it be
> >
> >
> >
> > sorry - to dump this on you - but I've done quite a bit and need
> some
> > blanks filling in please.
> >
> > many thanks,
> > John.
> >
> >
> >
> >
> >
> >
> > John Hawkins
> >
>
>
