This is off topic from federations, but JAXR is
implemented for Sun's Service Registry. Sun's Service
Registry is one registry we are using for the Feb demo
that Rex mentioned. I have that up and going at:
Everything you can do with JAXR as a client app you
can do through the Registry web console.
I am now trying to figure out how our RA meta-model
fits into the ebXML RIM model which is what is
referenced in section 4 of the JAXR document. If
anyone is interested, here is a link to the 3.0
version of the ebXML RIM document:
The ebXML Registry Information Model does define a
federation object but that is to federate an entire
registry with another registry. I think federation at
this level is too course grained to solve a lot of the
cross ownership boundary issues that will be common to
the majority of people who jump into a SOA-ecosystem.
There are multiple granularity levels that the
federation problem can be approached from.
Federation is an important concept and I wanted to get
other input about its placement in relation to our RA
Service Description.
Danny
--- "Jeffrey A. Estefan"
Danny,
Where are you going with this federation business???
Are you proposing something along the lines of the
Federated Enterprise
Reference Architecture (FERA) model?
(See Section 3.0)
There was a big play in the ebXML world on this
(see, e.g.,
I saw it go nowhere when
I attended the OASIS Symposium up in San Francisco a
few years ago. There
were briefings from the ebSOA TC folks and, again,
it has gone absolutely
nowhere. In fact, I have not seen it referenced
anywhere outside this
community or even the analyst community.
I'm really worried that once again, we're getting
distracted and we NEED TO
FINISH THE RA!!!!!! Our work has gone one far too
long in my opinion. We
need to stay focused as a razor.
If you're looking to build out a tool for your
registry/repository, then you
should leverage the various service metadata
information models (IMs) out
there. The IM described in JSR 93 (JAXR) is one of
the best I've seen. And
it supports both UDDI and ebXML standards. I've
attached a copy of the
original spec. Check out Section 4 and in
particular, Fig. 11, which
provides a UML class diagram depicting the IM.
Cheers...
- Jeff E.
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave
the OASIS TC that
generates this mail. You may a link to this group
and all your TCs in OASIS
at:
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. You may a link to this group and all your TCs in OASIS
at: