Hi Jason,

I haven't worked much on the xerces.pm. However, I am familiar with xerces-c
part. So, if you are interested, I can help out on the couple of
documentation items you have identified below:

* someone to document which functions in Xerces-C throw expceptions
  (and what class they throw: XMLException, SAXParseException,
  DOMException, ???). 

* someone to document which methods in Xerces-C have polymorphic
  parameter lists (i.e. there's more than one function with the same
  name, but a different argument list). 


Let me know how to proceed ...

Thanks,
Ram.

Ram Mareddy
Software Engineer
Siebel Systems, Inc.



-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Monday, June 18, 2001 10:06 PM
To: [EMAIL PROTECTED]
Subject: Help Maintaining Xerces.pm


Hey all,

There is plenty of room here at the Xerces.pm maintenance office for
more project committers. Harwin and Frederick Paul seem to have
disappeared into product-release morass and I haven't heard a peep
from them in months. 

I'm kinda feeling overwhelmed and I'd like some help.

Things high up on the wish list:

* someone to work on getting Xerces.pm running on Windows (Tom Watson
  are you still alive?)...

* someone to build binaries for the supported Architectures. Apache
  has a number of build machines for this purpose, but it takes time.

* someone to document which functions in Xerces-C throw expceptions
  (and what class they throw: XMLException, SAXParseException,
  DOMException, ???). 

* someone to add a more generic way to add exception handling to
  functions in Xerces.C (the wrapper code file auto-generated by
  SWIG). Currently I have to add a piece to postSource.pl (the perl
  script that modifies Xerces.C after SWIG creates it to add all the
  details that enables it to work properly for Xerces.pm) for each new
  method I uncover. This is tedious. I'd just like to have a list of
  method names, and whenever I encounter a call to a method in the
  list, I wrap it with exception handling code.

* someone to document which methods in Xerces-C have polymorphic
  parameter lists (i.e. there's more than one function with the same
  name, but a different argument list). 

* someone to fix the Xerces_header files to support polymorphic method
  invocation. I have a generic mechanism in place for doing this, but
  it just takes time typing.

* someone to port the other sample files for Xerces-C to Xerces.pm:
  - CreateDOMDocument
  - EnumVal
  - PParse
  - Redirect
  - SAX2Print
  - SAXPrint

I'm perfectly capable of implementing this all by myself, but I'm a
volunteer, Apache is not paying me to do this (however I would accept
donations). 

jas.

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



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

Reply via email to