Byrne
I think the only interface change is using "uddiversion => 2" on the "use"
statement.
Example:
==============
my $uddi_server = 'http://uddi.microsoft.com/inquire';
use UDDI::Lite uddiversion => 2, # UDDI v2
+trace=>[qw(headers fault debug)], # displays raw UDDI messages
(send/receive)
+autodispatch => proxy => $uddi_server,
import => 'UDDI::Data',
import => ['UDDI::Lite' => ':find'] # import find method names
;
===============
There may have also been a change to the importable labels. They are delete,
auth, save, validate, find, get. Or, inquiry or publish (which import
respective subsets of the preceeding).
It should be noted that v3 support is incomplete. The problem with v3 is
that the schema uses more non-UDDI namespaces. Accessing attributes and
elements is not as automatic as v1 and v2.
This began to be a problem in v2 when the language attribute was xml:lang.
This wasn't too bad with just one attribute requiring special qualifiying on
two elements (name and description). But, v3 is taking this to new levels.
xml:lang occurs on more elements. And, other namespaces are being used (like
"dsig" on
the signiture *element*).
There are some other things which I'm not sure how UDDI::Lite should or
shouldn't try to handle. Like v3's new support for multi-queries into a
single complex query. I remember something else stood out to me but I can't
find it at the moment. (It was the XML feature which lets you specify the
rules at validation time. I thought one of the methods had this.)
Mark
|
