parameternames in your auto generated wsdl, cause the the params looks like
in0, in1, in2... .
Then you use wsdl2java to generate your stub, locator, skeleton, impl and
maybe a testclient.
Now you can implement and deploy your Service by unsing the addtional
generated .wsdd files.
Hope this h
legacy functionality people
are
> trying to SOAP service enable.
>
> Bottom line: implementing a WS-I compliant SOAP service in Java is not a
> trivial thing. There are two types of people building Web Services in
Java:
> those who are extremely frustrated with the completely stupid
string contains xml
formated text?
If there are any sites that cover this information, please forward them on
to me.
Any help will be appreciated!!!
Thanks,
Joe Plautz
[EMAIL PROTECTED]
. Keep the
interface
as simple as possible.
Ross
-Original Message-
From: Joe Plautz [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 11, 2004 9:48 AM
To: [EMAIL PROTECTED]
Subject: Best Practices?
I'm a newbie looking for guidance in creating WebServices with Axis. I've
gone thr
bug reports)
> - What would you do if you were to write/re-write parts of axis?
> (enhancements requests)
>
> If we can't create new bug reports / enchancements to tell axis
> developers how axis should behave in the future (1.2 Final) then all
> discussion is just water under t
ion itself. Anyone can edit the wiki
content. (http://nagoya.apache.org/wiki/apachewiki.cgi?AxisProjectPages)
thanks,
-- dims
On Thu, 13 May 2004 08:47:30 -0500, Joe Plautz <[EMAIL PROTECTED]> wrote:
>
> I agree with Andy. Hence, why I started this thread looking for guidance.
>
>
Re: Best Practices?
>
> Let's twist this discussion on its head
> - Is there a list of bugs hiding in there somewhere? (bug reports)
> - What would you do if you were to write/re-write parts of axis?
> (enhancements requests)
>
> If we can't create new bug reports
the
data to be passed to the operation. Next, you'd click the submit button and
be presented with the results of the operation.
> -----Original Message-
> From: Joe Plautz [mailto:[EMAIL PROTECTED]
> Sent: Thursday, May 13, 2004 1:40 PM
> To: [EMAIL PROTECTED]
> Subject:
Hello all, I'm not sure where to post this one? But here it goes.
I am having an issue with a chunked response when connecting to Axis on
Tomcat using Power Builder. Aparently, Power Builder issues a request using
HTTP 1.1 but it does not accept a chunked response back. Does anyone know if
there i
way you wish. But, like EJB and other distributed
technologies they need to be used where appropriate. Deciding where it's
appropriate is something that comes with experience not reading it from
somewhere.
Have a great day,
Joe Plautz
[EMAIL PROTECTED] wrote:
Thanks, Nikki.
We have a stand
. But, like EJB and other distributed
technologies they need to be used where appropriate. Deciding where it's
appropriate is something that comes with experience not reading it from
somewhere.
Have a great day,
Joe Plautz
deal with Java and Ant alone, not WSDDs and WSDLs. The only
gripe I have with this process is that Axis's wsdl2java insists on putting
_client-side_ stubs in the same directory as _server-side_ WSDDs. There's no
getting around that because both get generated in the same task. Annoying
mplemented authentication using a
user authentication object.
Hope this helps,
Joe Plautz
Vikas Phonsa wrote:
I would appreciate if someone could comment on the security and
authorization aspects of the web services.
What is everybody using in that regard?
Thanks
Vikas
-Original Message-----
s. Not as
something that needs to be called over and over again in rapid succession.
Vikas Phonsa wrote:
Hi Joe,
Thanks for your answer. Could you elaborate a little bit about the
authentication object? Was that part of the SOAP message?
Thanks
Vikas
-Original Message-----
From: Joe Plautz [mai
Be code centric as opposed to WSDL centric. With Axis we can expose our
code in a relatively easy manner without the need of creating a WSDL
first which is perfect.
Anne Thomas Manes wrote:
I'm thinking about reusability.
Picture yourself a couple of years from now when your company has a few
s. (But why not just use RMI?)
If your goal is to develop language-independent, flexible, loosely coupled,
document-oriented, SOA environments, then you should take a WSDL-centric
approach.
Anne
-Original Message-
From: Joe Plautz [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 16,
In tomcat's documentation you can find all that you need for connection
pooling. I don't know of any restrictions on pools, but I have at least
10 going right now.
look here:
http://jakarta.apache.org/tomcat/tomcat-5.0-doc/jndi-datasource-examples-howto.html
Joe
METIN ZAVRAK wrote:
Hi,
Is there
Bare with me please I haven't dealt with this in a while so my specifics
might not be accurate. As you maybe aware of chunking is part of the
HTTP 1.1 specification. If you are specifying that you are submitting a
request in in HTTP 1.1 that means you will accept chunking in return. If
you sub
Hello all,
I don't know how many of you have seen the example floating around about
using WSS4J in axis. If it's already been posted, them my apologies. I
thought it might be appropriate to share it here.
http://weblogs.asp.net/jdanforth/archive/2005/01/16/354060.aspx
Have a great day,
Joe
tion, user info is being stored in client
specific databases. I've come up with my own ideas, which include
sending the "authentication" piece as part of the message. If anyone has
any alternative ideas please let me know.
Thanks,
Joe Plautz
20 matches
Mail list logo
