Should I add Jira about this?

After all, it is pretty pointless to have this symbol provider if it can't
work. (Perhaps there is some way to overcome this problem?)

 - 99


Ulrich Stärk wrote:
> 
> A Filter is passed a FilterConfig object where you can call
> getServletContext() and get the ServletContext. So the availability
> shouldn't be a problem. I rather believe that it doesn't get set in
> ApplicationGlobals until a certain point which is after building the
> SymbolSource...
> 
> Uli
> 
> Am Mo, 22.09.2008, 16:01, schrieb Peter Stavrinides:
>> Just a wild guess, but it sounds like an 'order of things' type problem,
>> Tapestry being a filter and not essentially a servlet, the context might
>> not be available at that point.
>>
>> ----- Original Message -----
>> From: "Ulrich Stärk" <[EMAIL PROTECTED]>
>> To: "Tapestry users" <users@tapestry.apache.org>
>> Sent: Monday, 22 September, 2008 4:51:23 PM GMT +02:00 Athens, Beirut,
>> Bucharest, Istanbul
>> Subject: NPE when trying to contribute ServletContextSymbolProvider to
>> SymbolSource (WAS: Re: Page pool hard limit and page instance usage)
>>
>> The problem seems to be, that the ServletContext provided by
>> ApplicationGlobals is null when Tapestry tries to contribute the
>> ServletContextSymbolProvider to the SymbolSource service. I don't know
>> why
>> this is the case. Maybe someone else can shed some light on this.
>>
>> Uli
>>
>> Am Mo, 22.09.2008, 08:08, schrieb 9902468:
>>>
>>> Hi again,
>>>
>>> I'm hitting my head to wall here with ServletContextSymbolProvider. It
>>> is
>>> configured like this:
>>>
>>> public static void
>>> contributeSymbolSource(OrderedConfiguration<SymbolProvider>
>>> configuration,
>>> @InjectService("ServletContextSymbolProvider") SymbolProvider
>>> servletContextSymbolProvider)
>>>     {
>>>         configuration.add("ServletContextSymbolProvider" ,
>>> servletContextSymbolProvider, "after:SystemProperties",
>>> "before:ApplicationDefaults");
>>>     }
>>>
>>>     public static ServletContextSymbolProvider
>>> buildServletContextSymbolProvider(ApplicationGlobals globals){
>>>         return new
>>> ServletContextSymbolProvider(globals.getServletContext());
>>>     }
>>>
>>> And it always ends to this error:
>>> java.lang.RuntimeException: Unable to instantiate class
>>> org.apache.tapestry5.services.TapestryModule as a module builder:
>>> Exception
>>> constructing service 'Alias': Error invoking service builder method
>>> org.apache.tapestry5.services.TapestryModule.buildAlias(Logger, String,
>>> AliasManager, Collection) (at TapestryModule.java:217) (for service
>>> 'Alias'): Exception constructing service 'SymbolSource': Error invoking
>>> constructor
>>> o
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Re%3A-NPE-when-trying-to-contribute-ServletContextSymbolProvider-to---SymbolSource-%28WAS%3A-Re%3A-Page-pool-hard-limit-and-page-instance-usage%29-tp19609348p19621689.html
Sent from the Tapestry - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to