What I'm seeing is that logged messages are never seen, and just
result in extra postings to this list.
On Dec 8, 2007 9:56 AM, Steve Eynon [EMAIL PROTECTED] wrote:
Except for maybe adding extra configuration for a test version of an
application I can't think why you'd want to extend the module
This leaves me with two questions:
My App Module class extended the
Component Module class. (Doh!) I now remember doing this to have the
Jetty Launcher in Eclipse pick up the component module configuration.
1) Why would you extend a module class so that it is effectively
included, when all you
Hi Chris,
You are correct and I agree with everything you say, no buts. You are
even right in your assumption that I'm not aware of the @SubModule
annotation. I don't recall seeing it mentioned anywhere, but will look
it up in a minute.
To address your specific points (...of my inadequacy -
To clear this one up, I was in error. My App Module class extended the
Component Module class. (Doh!) I now remember doing this to have the
Jetty Launcher in Eclipse pick up the component module configuration.
During my tour of the tapestry source I came across the
tapestry.modules system
Makes me wonder if Tapestry modules should be final?
On Dec 8, 2007 9:12 AM, Steve Eynon [EMAIL PROTECTED] wrote:
To clear this one up, I was in error. My App Module class extended the
Component Module class. (Doh!) I now remember doing this to have the
Jetty Launcher in Eclipse pick up the
Except for maybe adding extra configuration for a test version of an
application I can't think why you'd want to extend the module class.
That said, it's quite a constraint to impose for the module class
doesn't *need* to be final. (And guaranteed someone, somewhere will
want to at some point for
You say you've tried auto binding, but have you tried explicitly setting
the id? Like so:
public static void bind(ServiceBinder binder)
{
binder.bind(AssetFinder.class,
AssetFinderImpl.class).withId(AssetFinderWithExplicitId);
}
Auto binding assigns the class name as the service id,
On 12/5/07, Steve Eynon [EMAIL PROTECTED] wrote:
To clarify, I only have the one component module (the
WebsiteTagsModule) and it is only in that .jar that I specify the
Tapestry-Module-Classes property in the MANIFEST.MF.
So take a look at your environment. Once I ran into a similar problem
To clarify, I only have the one component module (the
WebsiteTagsModule) and it is only in that .jar that I specify the
Tapestry-Module-Classes property in the MANIFEST.MF.
Cheers for thinking about this,
Steve.
On 05/12/2007, Chris Lewis [EMAIL PROTECTED] wrote:
Nice catch :-). Does TIoC
Hello,
I have a number of T5 web apps that all use a common component module.
In the component's module class (as defined by the
Tapestry-Module-Classes property in its jar's MANIFEST.MF) there is a
simlpe build method:
public static AssetFinder buildAssetFinder(@InjectService AssetSource
So, there's no chance that you have a copy of the common module lib on
the general classpath and in WEB-INF/lib?
On Dec 5, 2007 7:26 AM, Steve Eynon [EMAIL PROTECTED] wrote:
Hello,
I have a number of T5 web apps that all use a common component module.
In the component's module class (as
Nice catch :-). Does TIoC 'know' which modules it has loaded? If so
perhaps an exception should be thrown, or at least a log message made,
if an app attempts to (indirectly) load a module more than once.
Thiago HP wrote:
On 12/5/07, Steve Eynon [EMAIL PROTECTED] wrote:
On 12/5/07, Steve Eynon [EMAIL PROTECTED] wrote:
java.lang.RuntimeException:
Service id 'AssetFinder' has already been defined by
com.alienfactory.websitetags.WebsiteTagsModule.buildAssetFinder
(AssetSource)
(at WebsiteTagsModule.java:28)
and may not be redefined by
Hi,
have you tried explicitly setting the id?
No I didn't try explicitly setting the service id for I only have the
one service which I only define the once. (Will try it tonight
though!)
So, there's no chance that you have a copy of the common module lib on
the general classpath and in
That's true, if its not clear, only the module containing the
WebsiteTagsModule class should have an entry in its Manifest pointing
to the class.
On Dec 5, 2007 8:25 AM, Thiago HP [EMAIL PROTECTED] wrote:
On 12/5/07, Steve Eynon [EMAIL PROTECTED] wrote:
java.lang.RuntimeException:
Service
15 matches
Mail list logo
