(Thank goodness the juddi-dev xpost is gone...

How might that work?  can you sketch some psuedo code?

I assume that me as a client programmer will have no need to change anything?


On Oct 22, 2005, at 1:01 PM, Anil Saldhana wrote:

Here is what we can do.

We can make the ConnectionFactories to have semantics
of what they represent:

a) ConnectionFactory that works off of the juddi data
types (current setup).
b) ConnectionFactory that works off of the xmlbeans
setup. (provided by RedHat).
c) ConnectionFactory that works off of the ebxml
stuff. (Level 1)

What are your thoughts on this?


--- Fernando Nasser <[EMAIL PROTECTED]> wrote:


Hi Geir,

Geir Magnusson Jr. wrote:

1) How can you remove the jUDDI dependency from

Scout?




It is removing dependencies from jUDDI types only,
and using XMLBeans
instead.  Just to make the JAXR part of the code
easier to integrate in
AppServers without having to load all jUDDI classes
and dependencies.

Of course, Scout still implements JAXR and has a
UDDI provider that
allows access to jUDDI registries, and any other
UDDI-compliant registry.

Now it can also access ebXML registries (so it is
now level 1).



2) Why was that discussed on the *juddi* list, and

not scout?




It should have been cross-posted.  It is my fault: 2
years ago when I
first tried to get involved in Scout there was no
list specific to Scout
yet and I was told to use the juddi list.  I mislead
Deepak to post in
that list.  Fortunately it seems that many (most?
all?) of the Scout
developers are also in the jUDDI list.

Regards to all.

Fernando






__________________________________
Yahoo! FareChase: Search multiple travel sites in one click.
http://farechase.yahoo.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



--
Geir Magnusson Jr                                  +1-203-665-6437
[EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to