components without jwc file

[Norbert Sándor <de...@erinors.com>]

Hello!

If a component is without a jwc file, why cannot it be declared 
explicitly in the library/application file?
Like:

    <component-type type="SomeComponent" 
class="com.example.SomeComponent" />

IMHO this explicit declaration would be a more natural extension of the 
framework than using component-class-packages:
- The extensive use of jwc-less components _may_ result in empty library 
files. How would a user instantly see which components are exactly part 
of that library?
- Probably it's a bad design decision but 2 libraries may share the same 
package.
- How would an automatic component doc generation tool / wysiwyg 
designer know exactly which components belong to a given library? For 
such tools it _must_ be explicitly specified which components are part 
of the library, then why not do that once in the .library/.application file?

I would remove the "component-class-packages" configuration option and 
prefer the above explicit declaration.

What do you think?

Regards:
Norbi

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org