RE: Web Services Metadata

[Ias <ia...@hotmail.com>]

Sorry for my late response. Please see inline below.

> > I'd like to discuss how we are going to develop web services metadata
> > (WSM). Currently Axis has its own WSM implementation hosted at ws-
> > axis/contrib.
> Ias,
> 
> Yes - let's start to figure out the JSR 181 piece of Beehive.  As you
> probably already know (but for the benefit of anyone who does not),
> BEA is the spec lead for JSR 181 and is therefore responsible for
> delivering a Reference Implementation and TCK.  While it is probably best
> if BEA develops the TCK on its own (I doubt there's a large Apache
> community to support building a TCK), it would make sense for the RI
> to just be the result of the Web Services piece of Beehive.

Personally I hope we can cooperate not only building the RI but also the TCK
even if all the Beehive WSM developers are not able to make the TCK by
themselves. What I'm thinking is coding Beehive WSM with test cases based on
assertions from JSR-181 APIs and specs. Those test cases will be bases of
the TCK. In other words, how to test a JSR-181 implementation will naturally
lead to how to certify it. It would be a great model for both Apache and BEA
to interact closely in the beginning of working on JSR-181.

> 
> So, you mentioned having some code already in the Axis project.
> Can you tell us more about that?  Are you, dims, and Jongjin all
> working on it already?  Where have you made the most progress
> already?

Okay, Axis WSM is a sort of an early prototype for JSR-181 (WSM from now
on), in particular, used with Axis. Because Axis was not originally designed
to support WSM, it has obvious limits to fulfill the spec. (That's why Axis
team is going for Axis 2 for a better integration.) As far as we are
concerned about Axis 1, we need to change it in a wide range to support
concepts brought by WSM. That's also why we, Axis team, all stay at the
prototype stage. Jongjin refactored Axis to be more friendly with WSM on his
JEUS (Tmax' J2EE server) codebase, so probably we are going to start both
sides, I mean pure WSM part and Axis support part, soon. According to my
Beehive WSM proposal draft,

Standard WSM APIs
-----------------
Beehive WSM APIs
-----------------
Axis implementation of BWSM
----------------------------
Axis support of WSM

the above layers are what we have been considering so far.

That's all I've got for you. Is there any point you want to know more,
please let me know where it is.

Thanks,

Ias

> 
> Thanks,
> Cliff