incubator-connectors-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Simon Willnauer <>
Subject Re: Meridio connector build strategy
Date Mon, 15 Feb 2010 13:25:04 GMT
good to see you are making progress! I have no experience with the
Meridio software but I can imagine what a pain it is to get this
right. I think we should concentrate on making progress over
perfection and follow the path with the least pain for now. We have
many many tasks ahead so I would suggest not to waste time on a
perfect solution but make is working somehow so we can build the
source and run tests or whatever depends on that code.

maybe I'm completely wrong but for now i would say just checkin the
stubs and we are fine, provided this is the quickest and least painful


On Mon, Feb 15, 2010 at 1:55 PM, Karl Wright <> wrote:
> All the straightforward connectors now have ant build scripts, so I'm
> starting work on the nastier ones.
> Meridio is the nastiest of the web-service-based connectors.  It's nasty for
> two reasons:
> (a) it depends on wsdls and xsds whose rights to redistribute have been
> explicitly declined by Autonomy (Meridio's owner), and
> (b) even if you have these wsdls and xsds available to you, they required
> hand modification in order to work properly with axis and castor.
> When the software grant was done, MetaCarta attempted to address these
> problems by specifying a process for obtaining and modifying the wsdls.
>  This process, however, requires not only a properly-installed Meridio
> instance of the right version (5.0 SP1, I believe), but also use of
> Microsoft's xmlpatch/xmldiff utility, which I believe is only available as
> an .exe on Windows.
> My strategy, therefore, for dealing with this connector seems to be either:
> (1) Locate or write an equivalent xmlpatch/xmldiff utility in the java
> world, and incorporate the patch/diff process in the build, or
> (2) Do all the work to pre-generate the java stubs using castor and axis for
> the Meridio web services, and check in those stub classes.
> I know we had this discussion before vis-a-vis the SharePoint connector, but
> the lack of an xmldiff utility throws and additional difficulty in the way
> for this connector.  Please advise.
> Karl

View raw message