ave the need to deploy some code as both a web service
and a web application. The JSPs will allow a user to configure their
subscription and the Web Services will then allow the user to get
updates to their subscription remotely.
What I want to know is what is the best practice for the srever sid
I currently have the need to deploy some code as both a web service and
a web application. The JSPs will allow a user to configure their
subscription and the Web Services will then allow the user to get
updates to their subscription remotely.
What I want to know is what is the best practice
Hi,
I'm wondering what the best practice is for handling beans that contain
methods returning java.util.Locale or java.util.TimeZone. I'm currently
using Axis 1.2RC1.
This relates to messages from Java2WSDL such as:
[WARN] Types - -The class java.util.Locale is defined in a jav
Le 19 nov. 04, à 09:25, HG a écrit :
As I understand it there was two approaches to the subject. Use Schema
Extensions or add a xsd:any element to the end of the superchema
(version
1). This assumes that you have schemas for both datatypes and messages.
The idea is that you can replace the xsd:any
rsday, November 18, 2004 4:04 PM
Subject: RE: Best Practice
> Henrik,
>
> No, not the only approach. It really depends on what changes you're
making.
>
>
> Most changes that I've come across have been small changes/extensions to
> existing services--adding new oper
mber 17, 2004 3:01 AM
To: [EMAIL PROTECTED]
Subject: Re: Best Practice
Hi Ed
Is this *really* the only approach? Defining it at a new endpoint?
I mean that's what I do for know, because I can't think of any other
way...but..you know.. :-)
Maybe this would be a task for the UDDI r
Please respond to [EMAIL PROTECTED]
To
[EMAIL PROTECTED]
cc
Subject
Re: Best Practice
The problem with this approach is that you're exporting
your object
model. This works fine for simple applications where you've got clients
that only talk to one web servic
to obtain
data objects from one service and use it in another service. (I mean
complex and deep objects.)
Am I missing something which will come and bite me at a later time? Or
have I been plain lucky?
Regards
Sagar
-Original Message-
From: Dennis Sosnoski [mailto:[EMAIL PROTE
Wednesday, November 17, 2004 1:14 PM
To: [EMAIL PROTECTED]
Subject: Re: Best Practice
Anand Natrajan wrote:
>SOAP is always going to be slower than RMI, no question. But by
adopting
>SOAP as a facade for my application, do I not gain
language-independence,
>flexibility, loose coupling
my API, but then
generating a SOAP version of the API to gain all of those advantages? The
only significant risk I see is that when designing my "code-centric" API, I
may use language-specific artifacts, e.g., hashes in Perl, or Sets in Java.
These structures may not translate well into othe
se language-specific artifacts, e.g., hashes in Perl, or Sets in Java.
These structures may not translate well into other languages. But as long as
I keep _that_ best practice in mind, I don't see an issue.
In response to Anne's earlier mail, I understand the point about being able
to identi
Anne,
I'm not sure what you mean by code-centric, versus WSDL
centric. The approach of writing the business functionality first (if it's
not already there) and then generating the first WSDL from that, before
deploying as a web service, may be thought of as code centric, but is not
tightly couple
On Tue, 16 Nov 2004, Jim Murphy wrote:
: Anand Natrajan wrote:
:
: > So what's my approach? Much as there is talk about writing WSDLs first, I
: > prefer generating them automatically. I can do all the refactoring I want in
: > my Java code and trust the java2wsdl generator to generate non-import
2004 7:00 PM
To: [EMAIL PROTECTED]
Subject: Re: Best Practice
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
I love this sentence, honest!
Can you be slightly more precise with the document-orientation ? I feel
a taste of REST, but this might only be an artificial spice.
thanks
paul
Le 17 nov. 04, à 14:52, Anne Thomas Manes a écrit :
Code centricity is a fine approach if your goal is to use SOAP as a
s
environments, then you should take a WSDL-centric
approach.
Anne
-Original Message-
From: Joe Plautz [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 16, 2004 7:00 PM
To: [EMAIL PROTECTED]
Subject: Re: Best Practice
Be code centric as opposed to WSDL centric. With Axis we can expose
environments, then you should take a WSDL-centric
approach.
Anne
-Original Message-
From: Joe Plautz [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 16, 2004 7:00 PM
To: [EMAIL PROTECTED]
Subject: Re: Best Practice
Be code centric as opposed to WSDL centric. With Axis we can expose
Some interesting discussion, here. I noticed
that many people seem to use WSDL generation. I don't think this is standard
(or done in a standard way) for all web service runtimes but it might not
generate very readable WSDL. One poster said something about the names
of parameters but we also add d
al Message -
From: "Ed Saltelli" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, November 17, 2004 5:15 AM
Subject: RE: Best Practice
>
> You refactor without changing the interface/WSDL to your service?!
>
> A WSDL artifact published to external
esday, November 16, 2004 6:12
PM
Subject: Re: Best Practice
Thanks, Joe.
I've had a quick glance through the mailing
list, back a year, but couldn't find anything obvious, in the best practice
area. In this particular aspect, I
prefer to work from Java. The way I see
ember 16, 2004 5:49 PM
To: [EMAIL PROTECTED]
Subject: Re: Best Practice
Anand Natrajan wrote:
> So what's my approach? Much as there is talk about writing WSDLs first, I
> prefer generating them automatically. I can do all the refactoring I want
in
> my Java code and trust the jav
another
without doing a detailed analysis of each WSDL file.
Anne
-Original Message-
From: Anand Natrajan [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 16, 2004 1:19 PM
To: [EMAIL PROTECTED]
Subject: RE: Best Practice
While I understand the attraction to factor out common definitions
security and
authorization in web services but there is just too much information and
it is kinda hard to select an approach to follow.
Thanks
-Original Message-
From: Jim Murphy [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 16, 2004 2:53 PM
To: [EMAIL PROTECTED]
Subject: Re: Best
PM
To: [EMAIL PROTECTED]
Subject: RE: Best Practice
Jim,
Could u direct to some resources about WS Security that possibly have some
examples related to Axis . I googled about security and authorization in web
services but there is just too much information and it is kinda hard to
select an approa
-
From: Jim Murphy [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 16, 2004 2:53 PM
To: [EMAIL PROTECTED]
Subject: Re: Best Practice
Joe Plautz wrote:
> Yes it was. It's something the carries application specific
information
> as well as customer and user specific information. It
EMAIL PROTECTED]
Subject: RE: Best Practice
While I understand the attraction to factor out common definitions into a
separate schema file, I am a bit conflicted about the use of schema files
within a WSDL for describing a service.
If your WSDL imports a schema, you can no longer hand out a sing
EMAIL PROTECTED]
Subject: RE: Best Practice
While I understand the attraction to factor out common definitions into a
separate schema file, I am a bit conflicted about the use of schema files
within a WSDL for describing a service.
If your WSDL imports a schema, you can no longer hand out a sing
Joe Plautz wrote:
Yes it was. It's something the carries application specific information
as well as customer and user specific information. It's not great by any
means, but it doesn't allow access either. But, by doing it this way,
I've tried to keep the services as more of one time shots. Not
Anand Natrajan wrote:
So what's my approach? Much as there is talk about writing WSDLs first, I
prefer generating them automatically. I can do all the refactoring I want in
my Java code and trust the java2wsdl generator to generate non-import WSDLs.
So how do you keep you clients from breaking when
lto:[EMAIL PROTECTED]
Sent: Tuesday, November 16, 2004 1:09 PM
To: [EMAIL PROTECTED]
Subject: Re: Best Practice
I think at a minimum, you use https. For actual authorization, I've had
to create a home brew of sorts because of the way we store use
information. This forces clients to send an
: Best Practice
I think at a minimum, you use https. For actual authorization, I've had
to create a home brew of sorts because of the way we store use
information. This forces clients to send an authentication object as
part of the message. There seem to be much more elegant solutions
invo
From: Joe Plautz [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 16, 2004 10:59 AM
To: [EMAIL PROTECTED]
Subject: Re: Best Practice
I'll try and be more positive next time. I was trying to be impartial
;-) I do agree that the developer doesn't have to deal much with the
WSDD. Usin
]
Subject: Re: Best Practice
I'll try and be more positive next time. I was trying to be impartial
;-) I do agree that the developer doesn't have to deal much with the
WSDD. Using the ant axis tasks should be a best practice. It does
automate a lot of stuff that doesn't need to b
: WSDD. Using the ant axis tasks should be a best practice. It does
: automate a lot of stuff that doesn't need to be dealt with. I would
: actually go farther and say that it would be nice to be able to go from
: class to WSDD in one easy step. Create your business classes, generate
: the WSD
I'll try and be more positive next time. I was trying to be impartial
;-) I do agree that the developer doesn't have to deal much with the
WSDD. Using the ant axis tasks should be a best practice. It does
automate a lot of stuff that doesn't need to be dealt with. I would
actu
nguages and technologies in the
: > past and, no doubt, best practices will emerge on web services, in the
: > future. Quite a good, thin, book of Java is "Java with Style" (or some
: > such title). It would be nice to have something like that for web
: > services, but, until then
Joe.
I've had a quick glance through the mailing list, back a year, but
couldn't find anything obvious, in the best practice area.
In this particular aspect, I prefer to work from Java. The way I see it,
I'm developing some business functionality, that might be usable in many
w
the namespace to
:http://foo-url"; />
:
: In addition, you must declare the namespace to reference any elements within
: the namespace:
: xmlns:foo="urn:foo"
:
: The same goes for schema imports.
:
: Anne
:
: _
:
: From: HG [mailto:[EMAIL PROTECTED]
: Sent: Tuesday, Nove
ing [EMAIL PROTECTED]:
> Thanks, Joe.
>
> I've had a quick glance through the mailing list, back a year, but
> couldn't find anything obvious, in the best practice area.
>
> In this particular aspect, I prefer to work from Java. The way I see it,
> I'm develop
Thanks, Joe.
I've had a quick glance through the mailing
list, back a year, but couldn't find anything obvious, in the best practice
area.
In this particular aspect, I prefer to work
from Java. The way I see it, I'm developing some business functionality,
that might be usable in
va is "Java with Style" (or some
such title). It would be nice to have something like that for web
services, but, until then, if anyone has produced anything in this vein,
that would be great.
Thanks for the links. I was aware of them but don't think they have
anything specific on b
Thanx for sharing this info.
It makes sence in respect of generation of proxies
in the different IDEs/tools
/Henrik
- Original Message -
From:
Anne Thomas Manes
To: [EMAIL PROTECTED]
Sent: Tuesday, November 16, 2004 3:17
PM
Subject: RE: Best Practice
eference any elements within the namespace:
xmlns:foo=”urn:foo”
The same goes for schema imports.
Anne
From: HG
[mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 16, 2004
8:57 AM
To: [EMAIL PROTECTED]
Subject: Re: Best Practice
Hi Anne
Thanx for your fan
eference any elements within the namespace:
xmlns:foo=”urn:foo”
The same goes for schema imports.
Anne
From: HG
[mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 16, 2004
8:57 AM
To: [EMAIL PROTECTED]
Subject: Re: Best Practice
Hi Anne
Thanx for your fan
Hi again Anne.
Nope. No need for these WSDL imports..I was mixing
things up...posts are done on a pure "brain dump" basis..
- Original Message -
From:
Anne Thomas Manes
To: [EMAIL PROTECTED]
Sent: Tuesday, November 16, 2004 2:58
PM
Subject: RE: Bes
- Original Message -
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, November
16, 2004 1:45 PM
Subject: Re: Best Practice
Thanks,
Henrik.
That's
the sort of thing I'm after.
I
couldn't quite work out
- Original Message -
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, November
16, 2004 1:45 PM
Subject: Re: Best Practice
Thanks,
Henrik.
That's
the sort of thing I'm after.
I
couldn't quite work out
o you know that WS-I Basic Profile
suggests according to schema imports and wsdl imports in respect to
namespaces.?
/Henrik
- Original Message -
From:
Anne Thomas Manes
To: [EMAIL PROTECTED]
Sent: Tuesday, November 16, 2004 2:45
PM
Subject: RE: Bes
,
Anne
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 16, 2004
7:46 AM
To: [EMAIL PROTECTED]
Subject: Re: Best Practice
Thanks,
Henrik.
That's
the sort of thing I'm after.
I
couldn't quite work out the difference between 1 and 2, th
,
Anne
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 16, 2004
7:46 AM
To: [EMAIL PROTECTED]
Subject: Re: Best Practice
Thanks,
Henrik.
That's
the sort of thing I'm after.
I
couldn't quite work out the difference between 1 and 2, th
e and to maintain namespace
compatibility (eg. generate to the same namspace each time)
Hope it helps and clears things up..
/Henrik
- Original Message -
From:
[EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, November 16, 2004 1:45
PM
Subject: Re: Best Practice
Thanks, Henrik.
That's the sort of thing I'm after.
I couldn't quite work out the difference between 1 and
2, though. In 1, you are defining the messages for the service methods
and this naturally includes the parameters of the methods. In 2, it seems
you're doing the same thing again (except for
- Your WSDL doesn't get cluttered with
types
Anyone... comments on these steps are
welcome...
Regards
Henrik
- Original Message -
From:
[EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, November 16, 2004 12:41
PM
Subject: Re: Best Practice
Does no on
have anything specific on best practice, though some
of the information might prove useful for a best practices guide.
Cheers,
Tony
Hi Tony
Not sure what you're after in particular,
For W3C's efforts in this area see links from http://www.w3.org/2002/ws/
For OASIS efforts see http:/
books" you may find other helpful references.
HTH
Nikki
--On Tuesday, November 16, 2004 11:41:41 + [EMAIL PROTECTED] wrote:
Does no one have, or have knowledge of, any best practice in the web
service arena?
I'm looking for a set of hints and tips, rather than a 800 page book
Does no one have, or have knowledge of, any
best practice in the web service arena?
I'm looking for a set of hints and tips, rather
than a 800 page book.
Tony
Does anyone know of a published set of best
practices, both for web services in general and Axis in particular?
I've scour
Does anyone know of a published set of best
practices, both for web services in general and Axis in particular?
I've scoured the Net and found a few bits
and pieces, but I'm looking for something more substantial (though not
*too* substantial).
Tony
Hi,
I'd like to kwnow what is the better way to retrieve configuration
parameters in classes deployted as Axis Web Services.
I could use properties file on file system, but I don't know if there is a
better way (I need to retrieve connection parameters for accessing my DB).
Thanks in advance
--
ng if there was any industry-standard 'best
practice' for doing this.
For instance, let's say i have the following:
Cat modify(Cat c)
Cat modify(Cat c, String name)
Dog modify(Dog d)
Some of the possible solutions include:
1) Appending numbers
Cat modify1(Cat c)
Cat m
'best
practice' for doing this.
For instance, let's say i have the following:
Cat modify(Cat c)
Cat modify(Cat c, String name)
Dog modify(Dog d)
Some of the possible solutions include:
1) Appending numbers
Cat modify1(Cat c)
Cat modify2(Cat c, String name)
Do
know what the "best practice" is for this sort of situation, but
what *I* would do is define a simple handler that performs the necessary
initialization in its init() method and add it to your for
the offending element. Keep in mind that if any of the handlers'
init() methods th
HI,
Sorry for this long winded question. I have a doc/literal web
service with a default scope of 'Request' so that the implementation class
is created with each service request. I want to perform initialization
ideally when the service is deployed, before it is ever hit( meaning before
I
[mailto:[EMAIL PROTECTED]
Sent: 12 December 2003 12:13
To: [EMAIL PROTECTED]
Subject: RE: Best practice for Java Object types like Integer, Long, ...
Keith,
In general, the approach you are taking will not work with other languages.
You see for example, C# does not include a Long data type. It onl
[mailto:[EMAIL PROTECTED]
Sent: Friday, December 12, 2003 6:00 AM
To: Axis-User (E-mail)
Subject: Best practice for Java Object types like Integer, Long, ...
Not an Axis-specific question, more about WSDL and Java...
I have a number of methods with parameters or return types like
java.lang.Integer or
[mailto:[EMAIL PROTECTED]
Sent: Friday, December 12, 2003 6:00 AM
To: Axis-User (E-mail)
Subject: Best practice for Java Object types like Integer, Long, ...
Not an Axis-specific question, more about WSDL and Java...
I have a number of methods with parameters or return types like
java.lang.Integer or
Not an Axis-specific question, more about WSDL and Java...
I have a number of methods with parameters or return types like java.lang.Integer or
java.lang.Long.
Using Java2WSDL/WSDL2Java these get converted into int and long, which is not what I
need - null is a valid value. But I can't put nill
66 matches
Mail list logo
