Re: xmlc 2.2 alpha 4

Chris Webb <[email protected]>
Newsgroups gmane.comp.java.enhydra.xmlc
Organization VoxSurf Ltd
Message-ID <[email protected]>
Yeah I got the latest from ObjectWeb. A few points:

1. I think Ant should also be put in xmlc/xmlc/modules/xmlc/lib because 
of the XMLC taskdef Ant dependacy. I realise that Ant is required 
globally but I think it's a better approach not to deliver Ant for the 
purpose of building everything as people generally have Ant installed on 
their development envionment for that purpose. Also adding a particular 
version of Ant to XMLC lib allows us to add some guarantee that the 
XMLC  taskdef will work with the right version of Ant. Does that make 
any sense?

2. It would be great to have an Ant taskdef that creates the HTML 
LazyDOMs as I don't build under Linux/Unix.

Cheers,
Chris


David Li wrote:

> you download from ObjectWeb, right? Just want to make sure.
>
> http://debian-sf.objectweb.org/projects/xmlc
>
> Well... I am still trying to make sense of the build system in XMLC. 
> Putting all the jars in top level makes it easier to maintain but it 
> seems to makes more senses to put it under individual modules since 
> only XMLC uses bcel.jar and servlet.jar.
>
> David
>
> On Wednesday, Mar 19, 2003, at 21:38 Asia/Shanghai, Chris Webb wrote:
>
>> David,
>>
>> Just downloaded the CVS source and I was wondering if would make more 
>> sense to have the servlet.jar and bcel.jar under a directory 
>> xmlc/xmlc/modules/xmlc/lib as these are directly required by XMLC. > 
>> Yes?
>>
>> Regards,
>> Chris
>>
>> David Li wrote:
>>
>>> Hi Chris,
>>>
>>>   Sorry that I haven't gotten around to integrate the path you 
>>> submit. I probably won't get a chance to work on XMLC for another 
>>> week or two. Would it be possible for you to take a look at the CVS 
>>> on ObjectWeb's SF? Would be great if you could give me a patch 
>>> against that tree. Otherwise, could you point me to the source to be 
>>> modified?
>>>
>>>   For the features, please post it here in a separate mails. I will 
>>> see what I can do.
>>>
>>> David
>>>
>>>
>>> On Wednesday, Mar 19, 2003, at 18:21 Asia/Shanghai, Chris Webb wrote:
>>>
>>>> David,
>>>>
>>>> We can't really upgrade XMLC until the extended lazy dom support 
>>>> that I submitted has been integrated. Any ideas when this will be? 
>>>> DO you need some help? Also I have some other feature requests, 
>>>> what is the appropriate way to submit these now?
>>>>
>>>> Cheers,
>>>> Chris
>>>>
>>>> David Li wrote:
>>>>
>>>>> It's alpha because I haven't gotten a chance to update the naming. :)
>>>>>
>>>>> We have been using it in production for over 2 months and just 
>>>>> shipped a product with it. It's pretty stable.
>>>>>
>>>>> David
>>>>>
>>>>> On Wednesday, Mar 19, 2003, at 16:59 Asia/Shanghai, Arno Schatz 
>>>>> wrote:
>>>>>
>>>>>> Hi David,
>>>>>>
>>>>>> How stable is that code, since you write 'aplha'? I am reluctant 
>>>>>> to use for production. However I would be interested solving the 
>>>>>> classpath issues.
>>>>>>
>>>>>> thanks,
>>>>>>     Arno
>>>>>>
>>>>>> David Li wrote:
>>>>>>
>>>>>>> Sorry that this takes a while. I finally get around to do the 
>>>>>>> name space renaming and has uploaded it to
>>>>>>> http://homepage.mac.com/taweili/XMLC.html
>>>>>>> It pass most of the unit tests (those fails are with layout 
>>>>>>> inconsistency due to the name change from org.apache to 
>>>>>>> org.enhydra.apache). The demo app is working.
>>>>>>> The namespace of the modified Apache Xerces parser has been 
>>>>>>> moved from org.apache to org.enhydra.apache. Now, the 
>>>>>>> application deployment should not run into conflict with the 
>>>>>>> existing Xerces bundled with the run time.
>>>>>>> Feedback and suggestion is appreciated.
>>>>>>> David
>>>>>>> _______________________________________________
>>>>>>> XMLC mailing list
>>>>>>> [email protected]
>>>>>>> http://www.enhydra.org/mailman/listinfo.cgi/xmlc
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> XMLC mailing list
>>>>>> [email protected]
>>>>>> http://www.enhydra.org/mailman/listinfo.cgi/xmlc
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> XMLC mailing list
>>>>> [email protected]
>>>>> http://www.enhydra.org/mailman/listinfo.cgi/xmlc
>>>>
>>>>
>>>>
>>>>
>>>> -- 
>>>> Chris Webb
>>>> Voxsurf Ltd.
>>>> 3rd Floor
>>>> Elme House
>>>> 133 Long Acre
>>>> London WC2E 9DT
>>>>
>>>> Tel. +44 (0) 20 7240 3621   x 206
>>>> Mob. +44 (0) 77 8639 2359
>>>> Fax. +44 (0) 20 7379 7573
>>>> e-mail : [email protected]
>>>> Voice Demo. +44 (0) 870 744 7223 http://www.voxsurf.com
>>>>
>>>> Email disclaimer: This can be viewed at 
>>>> http://www.voxsurf.com/disclaimer.html
>>>>
>>>>
>>>> _______________________________________________
>>>> XMLC mailing list
>>>> [email protected]
>>>> http://www.enhydra.org/mailman/listinfo.cgi/xmlc
>>>
>>>
>>>
>>> _______________________________________________
>>> XMLC mailing list
>>> [email protected]
>>> http://www.enhydra.org/mailman/listinfo.cgi/xmlc
>>
>>
>>
>> -- 
>> Chris Webb
>> Voxsurf Ltd.
>> 3rd Floor
>> Elme House
>> 133 Long Acre
>> London WC2E 9DT
>>
>> Tel. +44 (0) 20 7240 3621   x 206
>> Mob. +44 (0) 77 8639 2359
>> Fax. +44 (0) 20 7379 7573
>> e-mail : [email protected]
>> Voice Demo. +44 (0) 870 744 7223 http://www.voxsurf.com
>>
>> Email disclaimer: This can be viewed at 
>> http://www.voxsurf.com/disclaimer.html
>>
>>
>> _______________________________________________
>> XMLC mailing list
>> [email protected]
>> http://www.enhydra.org/mailman/listinfo.cgi/xmlc
>
>
> _______________________________________________
> XMLC mailing list
> [email protected]
> http://www.enhydra.org/mailman/listinfo.cgi/xmlc


-- 
Chris Webb
Voxsurf Ltd.
3rd Floor
Elme House
133 Long Acre
London WC2E 9DT

Tel. +44 (0) 20 7240 3621   x 206
Mob. +44 (0) 77 8639 2359
Fax. +44 (0) 20 7379 7573
e-mail : [email protected]
Voice Demo. +44 (0) 870 744 7223 
http://www.voxsurf.com

Email disclaimer: This can be viewed at http://www.voxsurf.com/disclaimer.html
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.