WSE 3.0 is fully supported with .NET 2.0. You can find out more about it
@
http://msdn2.microsoft.com/en-us/webservices/aa740663.aspx
There is a link to download it from the link above. There are also links
to hands on labs on the page above that should hopefully provide you
with what you need.
J
ubject: Re: [Axis2] HappyAxis fails: getRequestURL() not found
Yep, it works with Tomcat 5.5 + JDK 1.5. I'll eventually need to
incorporate Axis2 into our existing web server, which is running Tomcat
3.3. Is that going to be a problem?
Greg
On 11/27/06, John, Anil <[EMAIL PROTECTED]>
Greg,
Any particular reason you are using Tomcat 3.3? The current version is
5.5.X.
Don't know if it will help, but when I went through setting up my dev
environment for web service development with Axis, I documented it @
http://www.aniltj.com/blog/2006/02/06/InstallAndConfigureApacheTomc
There is a pretty good intro to WS-RM @ InfoQ from Paul. Don't think
that you can go wrong with it as he is the OASIS TC Co-Chair for WS-RM
as well as the VP of Tech at WSO2 :-)
http://www.infoq.com/articles/fremantle-wsrm-introduction
Regards,
- Anil
:-
:- Anil John
:- Johns Hopkins Univers
>Try instead.
>Or maybe a substitution group.
Support for substitution groups is pretty much of a non-starter in .NET.
So if this the service contract (WSDL/Schema etc. etc..) will be shared
with anyone using .NET so that they can generated their client proxies
from that info, I would recommend
Tim,
The issue that you are running into is very expected in that there
really is no direct mapping between certain language specific artifacts
and XML Schema.
A way around this is to first define what a Polygon is in XML Schema,
generate the appropriate WSDL and go in the other direction with
WS
Mike,
Which version of the Systinet registry are you using? The
UDDI 2.0 compliant one or the newer UDDI 3.0 compliant one?
Instead of directly generating the client side stubs from
the UDDI wsdl's, have you considered using the UDDI4J Library @ http://uddi4j.sourceforge.net/ ?
I do not
Leslie,
As an aside, provided you have an InterOp friendly WSDL and
Schema, on the .NET side you have an additional option for generating the
client proxy than the built-in wsdl.exe.
That is to use the free WSCF Visual
Studio.NET addin @http://www.thinktecture.com/Resources/Software/WSCon
.
regards,
~Thilina
On 7/19/05, John, Anil <[EMAIL PROTECTED]> wrote:
> to resolve
> such issues at this early stage rather than when things are more s
--
"May the SourcE be with u"
http://www.bloglines.com/blog/thilina
ms/archives/003213.html
-- dims
On 7/19/05, John, Anil <[EMAIL PROTECTED]> wrote:
>
>
> Greetings,
>
> I am curious to find out what the timeline for MTOM support is for
Axis.
>
> Especially given that Sun and Microsoft demo'd MTOM InterOp between
> th
Title: MTOM Support in Axis?
Greetings,
I am curious to find out what the timeline for MTOM support is for Axis.
Especially given that Sun and Microsoft demo'd MTOM InterOp between their Web service toolkits at JavaOne recently.
Regards,
- Anil
Just to add to Anne's comment RE: .NET
If you are going to be exposing your web service for consumption by
varied clients, it may be worthwhile to consider the WSDL/Schema first
approach to implementing your web service and client piece.
In short:
- Define the messages that are going to be exchan
12 matches
Mail list logo
