I think, it is better to include XPath as part of Axiom, rather than a
separate project/sub project. Since it is an addition of functionality,
whether XPath is part of the same library, or separate library, the
level of unstableness will be same. It will not modify any existing
functionality. But, later in time, if we want to use some functionlity
of XPath in our Axiom logic, (for example, methods like
axiom_element_get_children_with_xpath()), then it is better to include
XPath as part of axiom.
Regards,
Shankar.
Supun Kamburugamuva wrote:
HI Dumindu,
I think if we can include XPath as a seperate library it will be
better. If we include this to the Axiom it will make the Axiom much
heavier. Axiom is a well tested module and adding a large peice of not
very well tested code can make the Axiom unstable. Also if we make
XPath a separate sub project under Axiom it will be easier for us to
maintain.
Supun.
On Mon, Oct 6, 2008 at 11:32 AM, Dumindu Pallewela
<[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote:
Hi All,
I have started on integrating the XPath implementation done by
Varuna for GSoC [1] with our main trunk. I assume that (xpath
being specific to axiom), we can compile it directly into
libaxis2_axiom.so. Thus the source will go to /axiom/src/xpath
directory, and the includes, tests accordingly to relevant
directories relative to that location. You can find the branch I'm
working at [2].
Thanks,
Dumindu.
[1] http://issues.apache.org/jira/browse/AXIS2C-595
[2]
https://svn.apache.org/repos/asf/webservices/axis2/branches/c/xpath_integration/
--
Software Engineer, WSO2 Inc
http://wso2.org
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
