Just a quick update. I was able to get the client to the point where it
got an connection refused so I *assume* it would have done the soap call.
There is one issue it seems the current axiom snapshot jars in the
apache nightly repo are out of sync with what the snapshot jars required
by axis. I received a:
java.lang.AbstractMethodError:
org.apache.axiom.om.impl.llom.OMNamespaceImpl.get
NamespaceURI()Ljava/lang/String;
at org.apache.axis2.context.MessageContext.setEnvelope(MessageContext.ja
To resolve this I checked out Axiom source built it and used those
jars. That's about where I'm at. This is something going for the
client, so now I'll be moving on to seeing what the server is doing.
Rick wrote:
Ant, didn't have your work so I hacked out my own. I have it
compiling with maven and in eclipse. I've checked it in. All it does
is compile I'm sure. Have a quick look and see what I have jives with
yours.
ant elder wrote:
Rick, I've had a look at the latest Axis2 snapshot builds and it doesn't
seem so bad, just a few changes and it all compiles ok in eclipse.
Haven't
got your WS client sample running yet but hopefully will soon and I'll
looking at moving to the snapshot builds over the weekend or maybe
Monday.
I'll watch out for you on IRC over the weekend to coordinate with what
you're doing.
...ant
On 8/11/06, ant elder <[EMAIL PROTECTED]> wrote:
Could you describe how to get the ws client sample running?
I'll just have a go moving to a snapshot build on my local machine
and see
if there's any issues. Don't think we need a branch or to split this
btw
client and service just yet, it may end up being quite a painless
upgrade
...ant
On 8/11/06, Rick <[EMAIL PROTECTED]> wrote:
>
> Well with some hacks I have been able to get the client
(reference) to
> execute a web service. With what I checked in the server side was
also
> loaded but there are some configuring issues I haven't looked at but
> they are axis related and something that may even be different with a
> newer version of Axis. So I guess I'm saying is if no other
issues and
> using snap shots of Axis is the way to go... let the fun begin:-) I'm
> actually available to help out now.. I was thinking we could split
> server/client, how does that sound? If we want we could work on this
> in a branch so as to not disrupt others.
> ant elder wrote:
> > There was an offline chat yesterday about moving up to a newer
Axis2
> > build
> > to pick up some recent fixes. I'm a bit nervous about doing this
right
> > now
> > while Rick is in the middle of trying to get the WS binding to
go, and
> > while
> > the WS binding doesn't really work yet so we wont be able to easily
> > confirm
> > our code still works with the newer Axis2. How should we do this?
> > Should we
> > have a known SNAPSHOT build that we keep in a private maven
repository
> > like
> > we did pre-M1? Should I just go ahead and make the necessary
changes
> > or wait
> > till you're at some clean point Rick? Should I wait till we have a
> > service
> > and reference working before upgrading so we can know if the
upgrade
> > causes
> > us any problems?
> >
> > ...ant
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
