posted 19 years ago
This begs the real question: For the purposes of building a Web Service from a JavaBean, what's the technical definition of a JavaBean? I was under the impression that same John had, that the class had to be Serializable, which is obviously not true.
I'm working with the IBM Redbook samples, and the first one is a JavaBean-based Web Service. The class, WeatherForecast, implements no interface and extends no superclass. Every WS-published method throws 'Exception,' but other than that, there's nothing special going on.
So what elements DO you need so that a JavaBean can grow up to be a Web Service? What exceptions should it throw and are there any considerations about deployment layout (directory/jar structure)?
Keeping the answer limited to Web Service requirements...
...When is a JavaBean really a JavaBean?
Thanks.
Doug Hoople
MCSD.NET, MCDBA, MCSE, MCT, SCJP1.4