You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by Geoff Longman <gl...@gmail.com> on 2005/08/13 04:59:43 UTC
Spindle & T4 - new observation
So, I'm working on the never ending port of Spindle to T4 and I just
noticed something that will definitely clash...
This statement w/regards to searching for page classes in the packages
listed in the application specification :
"The list of packages is optional, and the default Java package is
searched last."
on page:
http://jakarta.apache.org/tapestry/UsersGuide/page-class.html
Eclipse doesn't handle the default package well at all. One might note
that Eclipse refactoring, in many cases, will not update classes found
in the default package. Why this is I used to know but have forgotten.
At one point I tried to implement my own handling of default packages
but the code was a mass of spaghetti and I soon ditched it.
Long story short, Spindle will not look for classes in the default package.
Geoff
PS. Ah, I see that Component class searching also occurs this way.
--
The Spindle guy. http://spindle.sf.net
Get help with Spindle:
http://lists.sourceforge.net/mailman/listinfo/spindle-user
Announcement Feed:
http://www.jroller.com/rss/glongman?catname=/Announcements
Feature Updates: http://spindle.sf.net/updates
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org