Re: does urlregexpmapping work correctly?

Attached is a zip file containing a very simple example of the problem I am 
seeing. In this example there is only one -urlregexpmapping args being 
executed. I am using xmlc 2.2beta. There is a readme.txt that explains setup 
and what I am seeing. If anyone has a few minutes to see if they see the same 
problem, it would help.

Thank you for your time,

-Kyle Aaron

>>> hoju@xxxxxxxx 7/30/2003 10:41:46 AM >>>
Hi Kyle,

At 09:21 AM 7/30/2003 -0600, you wrote:
>I have been doing more tests on the -urlregexpmapping arg to the xmlc 
>command. It seems that the xmlc command will support two -urlregexpmapping 
>args but not more. To test this, I created an index.htm that has a three 
>images in it with the urls ../images/im1.gif, ../images/im2.gif, 
>and  ../images/im3.gif. I use three -urlregexpmapping args to replace each 
>../images/im<num>.gif to be images/im<num>.jpg. Only two of the mappings 
>take place. The third is ignored.

Can you attach actual test cases you used, including your options.xmlc and 
the html files (attach in a zip file)?

>I have two questions:
>Has anyone experienced this problem before and how did you resolve it?
>Should this be listed as a bug since xmlc's documentation says that many 
>-urlregexpmapping args can be used?

I would think it is a bug.  I trust you are using the latest XMLC?  That 
is, either XMLC-2.2beta1 or the latest XMLC CVS?  If not, see:
http://forge.objectweb.org/projects/xmlc/ 


>Also, for some reason the -urlregexpmapping does not support the lookahead 
>feature. This feature is supported by GNU but only with the expression 
>syntax set to Perl 5. The default xmlc is using is another syntax that 
>does not support lookahead.

Any idea where this is set?  I haven't looked at how XMLC implements 
-urlregexpmapping as of yet, so any pointers would be helpful.  I don't see 
why XMLC's default shouldn't allow full functionality?  Anyone else have 
comments on this?

>One last note; the most recent version of Java's regex supports both 
>lookahead and lookbehind. This could really become handy in urlmappings.

I don't foresee using the JDK's regexp stuff since that wasn't added until 
j2sdk1.4, right?  I think we still want to say we are compatible with 
JDK1.3.1 (or maybe even 1.3.0).  I also don't see changing from gnu-regexp 
for the XMLC-2.2 release since we are purely in bugfix mode moving toward 
release at this time.  We could consider moving to one of the Jakarta 
regexp packages for a later XMLC release which, very likely, supports 
lookbehind.  Maybe you can investigate this?

Jake


>- Kyle Aaron
>
>
>
>
>------------------------------------------------------------------------------
>This message may contain confidential information, and is intended only 
>for the use of the individual(s) to whom it is addressed.
>
>
>==============================================================================
>
>
>_______________________________________________
>XMLC mailing list
>XMLC@xxxxxxxxxxx 
>http://www.enhydra.org/mailman/listinfo.cgi/xmlc 

_______________________________________________
XMLC mailing list
XMLC@xxxxxxxxxxx 
http://www.enhydra.org/mailman/listinfo.cgi/xmlc 



------------------------------------------------------------------------------
This message may contain confidential information, and is intended only for the 
use of the individual(s) to whom it is addressed.


==============================================================================

url_mapping_example.zip
Description: Zip compressed data