True, that's a new addition, it does give an answer for some of the classes ;)
On Wed, Nov 26, 2008 at 7:23 PM, Leonardo Uribe <[EMAIL PROTECTED]> wrote: > > > On Wed, Nov 26, 2008 at 7:15 PM, Leonardo Uribe <[EMAIL PROTECTED]> wrote: > >> Hi >> >> We have to take into account that tomahawk needs to generate the jsp tag >> hierarchy changing the package names of generated jsp tag classes from >> org.apache.myfaces.taglib to org.apache.myfaces.shared_tomahawk.taglib (this >> is done when myfaces-metadata.xml for tomahawk is generated). It is >> difficult to see this point clear now, but at first look sounds good. >> >> Based on some tests long time ago (checking incompatibilities of trinidad >> optimized state saving and facelets), facelets has some inner components >> used only when build the component tree from the abstract syntax tree. I >> think we need a package for that too (if in our implementation appears). >> > > Just a suggestion, checking the snapshot of the jsf 2.0 javadoc at > > > https://javaserverfaces-spec-public.dev.java.net/nonav/snapshots/pr1/javadocs/index.html > > It seems to be a new package called javax.faces.webapp.pld.facelets with a > class called FaceletHandler (all tag handlers should inherit from there). It > could be good to add it to the branch to start coding that part. > > regards > > Leonardo Uribe > > >> >> regards >> >> Leonardo Uribe >> >> On Wed, Nov 26, 2008 at 6:54 PM, Simon Lessard <[EMAIL PROTECTED] >> > wrote: >> >>> Hi all, >>> >>> We're reaching the point of integrating Facelets to the core 2.0 branch >>> and we need to determine what kind of package structure we'll be using.My >>> first thought would be to concentrate core Facelets classes in >>> org.apache.myfaces.application.facelets and place the tag classes in >>> org.apache.myfaces.taglib.facelets.core/html/* and move jsp specific tags >>> from org.apache.myfaces.taglib.* to org.apache.myfaces.taglib.jsp.* >>> >> >>> Is there any better suggestion for this? >>> >>> >>> Thanks, >>> >>> ~ Simon >>> >> >> >
