ObjectWeb Consortium
Search ObjectWeb Mail Archive: 

Advanced Search - Powered by Google


Mail Archive Home | xmlc List | Febuary 2000 Index

<--  Date Index  --> <--  Thread Index  -->

Re: Rocks: XMLC: Generating accessor methods


Hi Ryan,

Ryan Benjamin Shaw <ryan@xxxxxxxxxxxxxxx> writes:
> Currently, if XMLC encounters a Node id that
> is not a legal Java identifier, it does not
> generate an accessor method for that Node.

> 1) Give a warning when the compiler encounters
> this: ("Illegal Java ID: Not generating accessor") 

Actually, if one supplies the -methods option, it will
produce a listing of the IDs that don't have methods 
generated. Just realized that this is not actually
documented.

The logic here was that a page will contain a lot of 
ids that are used for other reasons (javascript) and
that always generating warnings would be annoying.
 
> 2) Come up with a standard way of converting
> strings that are legal id attribute values but
> not legal Java identifiers to legal Java identifiers.

This is really the thing to do and something that would be part of the
meta-data file.  Essentially, one could provide a mapping for an id to the
name use in the generated method.  This could be used for any id, not just
invalid ones.

> What do you guys think?

Gotta start getting that XMLC DTD together...

Mark
-----------------------------------------------------------------------------
To unsubscribe from this mailing list, send email to majordomo@xxxxxxxxxxx
with the text "unsubscribe rocks-group" in the body of the email.
If you have other questions regarding this mailing list, send email to
the list admin at owner-rocks-group@xxxxxxxxxxxx




<--  Date Index  --> <--  Thread Index  -->

Reply via email to:

Powered by MHonArc.

Copyright © 1999-2005, ObjectWeb Consortium | contact | webmaster.