Fast report, fast fix, can't ask faster, thanks Wouter and Ryan :-)
Judy
Wouter van Reeven wrote:
> Thanks again. That was a quick fix :-) I'll check it out asap.
>
>
> Wouter
>
> On Wed, Nov 11, 2009 at 08:34:22AM -0800, Ryan Lubke wrote:
>
>> On 11/10/09 10:05 AM, Wouter van Reeven wrote:
>>
>>> Thanks! I would have been happy to file the bug myself, but thanks
>>> anyway :-)
>>>
>>>
>> A new build of Mojarra was integrated early yesterday evening. You
>> should be able
>> to verify with lat night's nightly build of V3.
>>
>> Thanks for the report.
>>
>>> Wouter
>>>
>>> On Tue, Nov 10, 2009 at 10:02:15AM -0800, Ryan Lubke wrote:
>>>
>>>
>>>> Please see: https://javaserverfaces.dev.java.net/issues/show_bug.cgi?id=1405
>>>>
>>>> On 11/10/09 7:45 AM, Wouter van Reeven wrote:
>>>>
>>>>
>>>>> Hi all,
>>>>>
>>>>>
>>>>> While I am rehearsing my JEE5 to JEE6 migration presentation for
>>>>> tomorrow, I run into this issue that I have seen before but forgot to
>>>>> mention.
>>>>>
>>>>> According to tje JSF 2.0 spec it is possible to do without a
>>>>> faces-config.xml file. When I remove the file from my project and reload
>>>>> the application, it runs perfectly ok. However, GlassFish v3 complains
>>>>> about a missing file and keeps on throwing FileNotFoundExceptions:
>>>>>
>>>>> java.io.FileNotFoundException
>>>>> at org.apache.naming.resources.DirContextURLConnection.getInputStream(DirContextURLConnection.java:395)
>>>>> at com.sun.faces.config.ConfigureListener$WebConfigResourceMonitor$Monitor.getLastModified(ConfigureListener.java:1025)
>>>>> at com.sun.faces.config.ConfigureListener$WebConfigResourceMonitor$Monitor.hasBeenModified(ConfigureListener.java:1001)
>>>>> at com.sun.faces.config.ConfigureListener$WebConfigResourceMonitor.run(ConfigureListener.java:960)
>>>>> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
>>>>> at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
>>>>> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
>>>>> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
>>>>> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181)
>>>>> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205)
>>>>> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>>>>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>>>>> at java.lang.Thread.run(Thread.java:619)
>>>>>
>>>>> Is this a known issue? Sorry to not search the issue database myself,
>>>>> but I am a bit stressed about finishing the preparations for my demo :-)
>>>>>
>>>>>
>>>>> Thanks, Wouter
>>>>>
>>>>>
>>>>>
>>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: quality-unsubscribe_at_glassfish.dev.java.net
>>>> For additional commands, e-mail: quality-help_at_glassfish.dev.java.net
>>>>
>>>>
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: quality-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: quality-help_at_glassfish.dev.java.net
>>
>
>