Thread: RE: [Bodington-developers] Addition to HEAD: Custom transformations of IMS CP manifests using XSLT

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

> From: Alexis O'Connor=20
> Well good job you told us here where it came from as you=20
> didn't in the CVS commit comment ;-).

Point.  Comment updated.

		- Peter

We're also using Xalan to do some XSLTs on RSS feeds in WebLearn, we should
probably see if there's common code, and standardise on where the XSLT
stylesheets are located?

Colin

____________________________________
Colin Tatham
VLE Team
Oxford University Computing Services
www.oucs.ox.ac.uk/ltg/vle/
www.bodington.org

> -----Original Message-----
> From: bod...@li...
> [mailto:bod...@li...]On Behalf Of
> Peter Crowther
> Sent: 31 May 2005 13:16
> To: bod...@li...
> Subject: [Bodington-developers] Addition to HEAD: Custom 
> transformations
> of IMS CP manifests using XSLT
> 
> 
> Just added: the ability to transform IMS content package manifests on
> import.  This uses Xalan-J 2.6.0, which has been added to the lib
> directory as xalan.jar.  Note that this is the Apache jar, 
> *not* the Sun
> JWSDP one which has many of the classes in odd packages.  Testing has
> been on 1.4.2_08 SDK, Tomcat 5.0.28 only.
> 
> Details on file format are in
> tomcatadd/webapps/bodington/WEB-INF/xslt/readme.txt.
> 
> The new version *should* be backwardly-compatible with older
> installations that don't have Xalan, can't load Xalan due to some
> incompatibility with their preferred XML parser, don't have a 
> transforms
> directory, or have malformed transformations; in all these cases,
> Bodington logs an error and falls back to loading the 
> provided manifest
> without transformation.
> 
> 		- Peter
> 
> --
> Peter Crowther, Director, Melandra Limited
> John Dalton House, 121 Deansgate, Manchester M3 2AB
> t: +44 (0)161 828 8736  f: +44 (0)161 832 5683
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by Yahoo.
> Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
> Search APIs Find out how you can build Yahoo! directly into your own
> Applications - visit 
> http://developer.yahoo.net/?fr=fad-ysdn-ostg-q22005
> _______________________________________________
> Bodington-developers mailing list
> Bod...@li...
> https://lists.sourceforge.net/lists/listinfo/bodington-developers
> 

> From: [...] Colin Tatham
> We're also using Xalan to do some XSLTs on RSS feeds in=20
> WebLearn, we should probably see if there's common code, and=20
> standardise on where the XSLT stylesheets are located?

We should indeed.  The piece I've added is about 60 lines derived from
the Pipe example, and simply implements a flexible mechanism for piping
a XML file through a configurable series of transforms and into an
output file.  A more general version would probably use streams, not
files; not sure whether yours already does this.

src/org/bodington/server/ims/XSLTPipeline.java if you want to eyeball it
and tell me you've already got one :-).

		- Peter

> From: Alexis O'Connor=20
> Sorry to be so anal about it, but with the limited scope for file=20
> meta-data in CVS (and personal strong opposition to=20
> versioning jars via=20
> the file name!) it strikes me that the third-party versioning=20
> of a file is best placed in the CVS commit comment itself.

In the case of jars, many/most carry version information in their
manifest.  I'm aware of your views on versioning via the filename; I've
seen it work both ways (and I've seen the pain caused both ways), so I'm
essentially agnostic on that.

> It appears as though some muppet has added the xalan from=20
> JWSDP onto the SPWS branch already.

That would be me.  Or, more accurately, you taking the file from me.

> Why he did that when I, I mean, he had the Xalan=20
> library on his machine I don't know ;-). (Ah, probably because he was=20
> trying to second guess where some other developer had got his=20
> jars from...).

No, it's because SPWS uses a JAXB-produced parser and therefore I passed
the JWSDP libraries to you.  I suspect it will be faster to remove the
dependency on Sun's custom Xalan from SPWS than it will be to ensure
that future uses of Xalan in the rest of Bodington are compatible with
Sun's bastardised version.

		- Peter

> 
> No, it's because SPWS uses a JAXB-produced parser and therefore I passed
> the JWSDP libraries to you.  I suspect it will be faster to remove the
> dependency on Sun's custom Xalan from SPWS than it will be to ensure
> that future uses of Xalan in the rest of Bodington are compatible with
> Sun's bastardised version.
> 
> 		- Peter

I do indeed stand corrected on multiple counts!

You are clearly well on top of the various issues and actually it now 
all makes pretty good sense (to me anyway :-) ).

Alexis

> From: Alexis O'Connor=20
> You are clearly well on top of the various issues

<blink>

I am? :-)

> and actually it now=20
> all makes pretty good sense (to me anyway :-) ).

OK.

		- Peter

Peter Crowther wrote:
>>From: Alexis O'Connor 
>>Well good job you told us here where it came from as you 
>>didn't in the CVS commit comment ;-).
> 
> 
> Point.  Comment updated.
> 
> 		- Peter
> 

Thanks for that.

Sorry to be so anal about it, but with the limited scope for file 
meta-data in CVS (and personal strong opposition to versioning jars via 
the file name!) it strikes me that the third-party versioning of a file 
is best placed in the CVS commit comment itself.

It appears as though some muppet has added the xalan from JWSDP onto the 
SPWS branch already. Why he did that when I, I mean, he had the Xalan 
library on his machine I don't know ;-). (Ah, probably because he was 
trying to second guess where some other developer had got his jars from 
...).

Alexis