You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@myfaces.apache.org by Catalin Kormos <ca...@gmail.com> on 2007/01/29 21:54:51 UTC
Dojo widgets not working on IE
Hi,
Any of you experiencing problems using Dojo based components on IE, like
modalDialog or inputSuggestAjax? i keep getting this kind of messages, and
only on IE:
Jan 29, 2007 9:48:13 PM
org.apache.myfaces.renderkit.html.util.MyFacesResourceLoader serveResource
SEVERE: Unable to find resource src/widget.js for component
dojo.DojoResourceLoader. Check that this file is available in the classpath
in sub-directory /resource of the package-directory.
It works perfectly fine on Firefox, and it did worked on IE too, a few days
ago. I'm using the latest 1.1.5 snapshots that i built from the SVN with
facelets.
Thanks,
Catalin
Re: Dojo widgets not working on IE
Posted by Werner Punz <we...@gmx.at>.
Catalin Kormos schrieb:
> Hi,
>
> Any of you experiencing problems using Dojo based components on IE, like
> modalDialog or inputSuggestAjax? i keep getting this kind of messages,
> and only on IE:
>
> Jan 29, 2007 9:48:13 PM
> org.apache.myfaces.renderkit.html.util.MyFacesResourceLoader serveResource
> SEVERE: Unable to find resource src/widget.js for component
> dojo.DojoResourceLoader. Check that this file is available in the
> classpath in sub-directory /resource of the package-directory.
>
> It works perfectly fine on Firefox, and it did worked on IE too, a few
> days ago. I'm using the latest 1.1.5 snapshots that i built from the SVN
> with facelets.
>
Ah ok sorry for this confusion, there indeed is a bug but it is ie only.
I tried the dialog as well and can reproduce the problem,
it must have been introduced somewhere in the dojo utils,
I am affected by it as well.
I will look into it, not quite sure what it is probably an
initialisation timing issue. Best bet to nail it down for now
is to check the change history of the dojo utils if someone has
introduced a "fix" into the component creation code which broke it.
I have to look into that due to a similar problem in the fisheye someone
reported me as well, so I will be onto it in about two hours.
Werner
Re: Dojo widgets not working on IE
Posted by Catalin Kormos <ca...@gmail.com>.
Hey, very good news! :) Many thanks to Mario as well.
Regards,
Catalin
On 2/1/07, Werner Punz <we...@gmx.at> wrote:
>
> Ok guys, the issue has been fixed, Mario fixed it (I just helped him to
> type and to test here).
> If need it prompty get a checkout from svn and to a compile yourself,
> if not wait for the nightly build to get the fix in.
>
> The problem was some newly introduced encoding code, which
> triggered a bug in the ie rendering engine.
>
> The + side of all those changes (which also introduced the bug) is that
> resource reloading from the server into the browser should happen way
> less often and generally the
> resource loading is more efficient.
>
>
> Cheers
>
> Werner
>
>
>
> Catalin Kormos schrieb:
> > Hi Werner,
> >
> > Many thanks for you efforts on resolving this issue, i realy appreciate
> > it :).
> >
>
>
Re: Dojo widgets not working on IE
Posted by Werner Punz <we...@gmx.at>.
Ok guys, the issue has been fixed, Mario fixed it (I just helped him to
type and to test here).
If need it prompty get a checkout from svn and to a compile yourself,
if not wait for the nightly build to get the fix in.
The problem was some newly introduced encoding code, which
triggered a bug in the ie rendering engine.
The + side of all those changes (which also introduced the bug) is that
resource reloading from the server into the browser should happen way
less often and generally the
resource loading is more efficient.
Cheers
Werner
Catalin Kormos schrieb:
> Hi Werner,
>
> Many thanks for you efforts on resolving this issue, i realy appreciate
> it :).
>
Re: Dojo widgets not working on IE
Posted by Werner Punz <we...@gmx.at>.
Actually I was looking into the codepart, but it was not the issue, but
good news
I could nail down the problem so far to a single class
like Mario suspected something in the MyFacesResourceLoader goes haywire
I still suspect some content length problems triggering an inerhently
evil IE bug.
There is a quick workaround, revert the class to a state before
24/1/2007 and recompile it, that should fix the issue for now.
Since Marios additions are useful and also improve the performance
tremendously I will not revert the codebase yet in svn, but I will
try to fix the bug the next few hours, if I can find it.
If I cannot find it I will revert the version in the svn back to a
working condition, so that you guys should get a working version soon.
Cheers
Werner
Catalin Kormos schrieb:
> Hi Werner,
>
> Many thanks for you efforts on resolving this issue, i realy appreciate
> it :).
>
Re: Re: Dojo widgets not working on IE
Posted by Catalin Kormos <ca...@gmail.com>.
Hi Werner,
Many thanks for you efforts on resolving this issue, i realy appreciate it
:).
Cheers,
Catalin
On 2/1/07, Joshua Pheneger <jo...@vegas.com> wrote:
>
> Werner,
>
> Glad you were able to find the issue. Please let me know when you have
> a build I can test.
>
> Regards,
> Joshua Pheneger
>
> -----Original Message-----
> From: news [mailto:news@sea.gmane.org] On Behalf Of Werner Punz
> Sent: Thursday, February 01, 2007 1:21 AM
> To: users@myfaces.apache.org
> Subject: Re: Dojo widgets not working on IE
>
> Werner Punz schrieb:
> > Joshua Pheneger schrieb:
> >> Please update when this fix is available. I am in the process of
> >> testing a fix for scrolling dialog boxes and this error is now
> >> preventing me from testing my fix.
> >>
> >> Regards,
> >> Joshua Pheneger
> >>
> > Jousha I am still trying to figure some things out here, what is the
> > configuration does your server run on?
> > The reason why I am asking is, because I want to know if this is a
> > dual core/multi core issue or some problems with the Mac JDK or (or a
> > bug triggered in it)
> >
> >
> Ok, I got a good indication of the cause of this problem it seems that
> the cause is a content-length bug triggered in ie in certain conditions,
> it has been readded, due to some speed optimizations in the resource
> loader (thanks Mario for the hint)
>
> the code at fault is :
>
>
> if (lastModified == browserDate)
> {
> // the browser already has the correct version
>
> response.setStatus(HttpURLConnection.HTTP_NOT_MODIFIED);
> return;
> }
> located in the MyFacesResourceLoader
>
> It is probably a missing content length there, or a wrong one.
>
> Problem is I cannot test fix and commit it now, only in the evening.
> So another one has to do it for now, or you guys have to wait a little
> bit.
>
RE: Re: Dojo widgets not working on IE
Posted by Joshua Pheneger <jo...@vegas.com>.
Werner,
Glad you were able to find the issue. Please let me know when you have
a build I can test.
Regards,
Joshua Pheneger
-----Original Message-----
From: news [mailto:news@sea.gmane.org] On Behalf Of Werner Punz
Sent: Thursday, February 01, 2007 1:21 AM
To: users@myfaces.apache.org
Subject: Re: Dojo widgets not working on IE
Werner Punz schrieb:
> Joshua Pheneger schrieb:
>> Please update when this fix is available. I am in the process of
>> testing a fix for scrolling dialog boxes and this error is now
>> preventing me from testing my fix.
>>
>> Regards,
>> Joshua Pheneger
>>
> Jousha I am still trying to figure some things out here, what is the
> configuration does your server run on?
> The reason why I am asking is, because I want to know if this is a
> dual core/multi core issue or some problems with the Mac JDK or (or a
> bug triggered in it)
>
>
Ok, I got a good indication of the cause of this problem it seems that
the cause is a content-length bug triggered in ie in certain conditions,
it has been readded, due to some speed optimizations in the resource
loader (thanks Mario for the hint)
the code at fault is :
if (lastModified == browserDate)
{
// the browser already has the correct version
response.setStatus(HttpURLConnection.HTTP_NOT_MODIFIED);
return;
}
located in the MyFacesResourceLoader
It is probably a missing content length there, or a wrong one.
Problem is I cannot test fix and commit it now, only in the evening.
So another one has to do it for now, or you guys have to wait a little
bit.
Re: Dojo widgets not working on IE
Posted by Werner Punz <we...@gmx.at>.
Werner Punz schrieb:
> Joshua Pheneger schrieb:
>> Please update when this fix is available. I am in the process of
>> testing a fix for scrolling dialog boxes and this error is now
>> preventing me from testing my fix.
>>
>> Regards,
>> Joshua Pheneger
>>
> Jousha I am still trying to figure some things out here,
> what is the configuration does your server run on?
> The reason why I am asking is, because I want to know
> if this is a dual core/multi core issue
> or some problems with the Mac JDK or (or a bug triggered in it)
>
>
Ok, I got a good indication of the cause of this problem
it seems that the cause is a content-length bug triggered in ie in
certain conditions, it has been readded, due to some speed optimizations
in the resource loader (thanks Mario for the hint)
the code at fault is :
if (lastModified == browserDate)
{
// the browser already has the correct version
response.setStatus(HttpURLConnection.HTTP_NOT_MODIFIED);
return;
}
located in the MyFacesResourceLoader
It is probably a missing content length there, or a wrong one.
Problem is I cannot test fix and commit it now, only in the evening.
So another one has to do it for now, or you guys have to wait a little bit.
Re: Dojo widgets not working on IE
Posted by Werner Punz <we...@gmx.at>.
Joshua Pheneger schrieb:
> Please update when this fix is available. I am in the process of
> testing a fix for scrolling dialog boxes and this error is now
> preventing me from testing my fix.
>
> Regards,
> Joshua Pheneger
>
Jousha I am still trying to figure some things out here,
what is the configuration does your server run on?
The reason why I am asking is, because I want to know
if this is a dual core/multi core issue
or some problems with the Mac JDK or (or a bug triggered in it)
RE: Re: Dojo widgets not working on IE
Posted by Joshua Pheneger <jo...@vegas.com>.
Please update when this fix is available. I am in the process of
testing a fix for scrolling dialog boxes and this error is now
preventing me from testing my fix.
Regards,
Joshua Pheneger
-----Original Message-----
From: news [mailto:news@sea.gmane.org] On Behalf Of Werner Punz
Sent: Wednesday, January 31, 2007 2:00 PM
To: users@myfaces.apache.org
Subject: Re: Dojo widgets not working on IE
Ok, I am getting closer,
I upgraded the tomcat versions, the problem still persists.
Funny thing is, it is only on a Mac (running an intel Dual Core) If I
serve the file from linux on a single core notebook in the same Tomcat
configuration the problems are gone.
This looks like a timing issue, i am not sure if the mac is at fault
here, or the Dual core is triggering something in the JVM, I got a
similar report from a user whom I am trying to fix some issues in the
Fisheye for.
Anyway, dojo is not at fault here, the problem either is the jdk or some
resource loader code going haiwire.
The funny thing is, once I switched tomcats the client abort exception
stopped (maybe it was ignored due to different settings) but the result
of not working dojo controls persisted.
I will add a note in the jira report, someone else has to take over
that, I have to say this is beyound the domain where I am good at :-(
Werner
Werner Punz schrieb:
> Ok I am ccing this into the devs list, some other people have to look
> into the issue as well!
>
>
> I think I found the cause of all evil regarding the non initializing
> components:
>
> 2007 21:46:29 org.apache.myfaces.shared_tomahawk.config.MyfacesConfig
> getStringInitParameter
> INFO: No context init parameter
> 'org.apache.myfaces.RESOURCE_VIRTUAL_PATH' found, using default value
> /faces/myFacesExtensionResource
> 31.01.2007 21:46:29
> org.apache.myfaces.shared_tomahawk.config.MyfacesConfig
> getCurrentInstance
> INFO: Starting up Tomahawk on the MyFaces-JSF-Implementation
> 31.01.2007 21:46:30
> org.apache.myfaces.shared_impl.config.MyfacesConfig
> getBooleanInitParameter
> INFO: No context init parameter
> 'org.apache.myfaces.READONLY_AS_DISABLED_FOR_SELECTS' found, using
> default value true
> 31.01.2007 21:46:30
> org.apache.myfaces.shared_impl.config.MyfacesConfig
> getStringInitParameter
> INFO: No context init parameter
> 'org.apache.myfaces.RESOURCE_VIRTUAL_PATH' found, using default value
> /faces/myFacesExtensionResource
> 31.01.2007 21:46:30
> org.apache.myfaces.shared_impl.config.MyfacesConfig
> getCurrentInstance
> INFO: Starting up Tomahawk on the MyFaces-JSF-Implementation
> 31.01.2007 21:46:40
> org.apache.myfaces.renderkit.html.util.DefaultAddResource
> serveResource
> SCHWERWIEGEND: Error while serving resource:
> dojo.DojoResourceLoader/dojo.js, message : null
> ClientAbortException: java.net.SocketException: Broken pipe
> at
>
org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.j
ava:366)
> at
org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:433)
> at
>
org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:314
)
> at
org.apache.catalina.connector.OutputBuffer.close(OutputBuffer.java:278)
> at
>
org.apache.catalina.connector.CoyoteOutputStream.close(CoyoteOutputStrea
m.java:103)
> at
>
org.apache.myfaces.renderkit.html.util.MyFacesResourceLoader.writeResour
ce(MyFacesResourceLoader.java:244)
> at
>
org.apache.myfaces.renderkit.html.util.MyFacesResourceLoader.serveResour
ce(MyFacesResourceLoader.java:217)
> at
>
org.apache.myfaces.renderkit.html.util.DefaultAddResource.serveResource(
DefaultAddResource.java:606)
> at
>
org.apache.myfaces.webapp.filter.ExtensionsFilter.doFilter(ExtensionsFil
ter.java:128)
> at
>
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica
tionFilterChain.java:202)
> at
>
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt
erChain.java:173)
> at
>
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv
e.java:213)
> at
>
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv
e.java:178)
> at
>
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java
:126)
> at
>
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java
:105)
> at
>
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.
java:107)
> at
>
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:1
48)
> at
>
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:86
9)
> at
>
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.proc
essConnection(Http11BaseProtocol.java:664)
> at
>
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint
.java:527)
> at
>
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollow
erWorkerThread.java:80)
> at
>
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool
.java:684)
> at java.lang.Thread.run(Thread.java:613)
> Caused by: java.net.SocketException: Broken pipe
> at java.net.SocketOutputStream.socketWrite0(Native Method)
> at
java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
> at
java.net.SocketOutputStream.write(SocketOutputStream.java:136)
> at
>
org.apache.coyote.http11.InternalOutputBuffer.realWriteBytes(InternalOut
putBuffer.java:746)
> at
org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:433)
> at
org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:348)
> at
>
org.apache.coyote.http11.InternalOutputBuffer$OutputStreamOutputBuffer.d
oWrite(InternalOutputBuffer.java:769)
> at
>
org.apache.coyote.http11.filters.IdentityOutputFilter.doWrite(IdentityOu
tputFilter.java:117)
> at
>
org.apache.coyote.http11.InternalOutputBuffer.doWrite(InternalOutputBuff
er.java:579)
> at org.apache.coyote.Response.doWrite(Response.java:559)
> at
>
org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.j
ava:361)
> ... 22 more
>
>
> But the funny thing is, this does not happen always, something must be
> going badly wrong in the resource loader, which is code I have
> absolutely no clue about (sorry have not touched it so far)
>
> My personal assumption is, that the ie to my knowledge chokes on
> resources if you do not serve the filelength upfront, under certain
> conditions. I have no clue why I am getting this and others like
> cagatay under similar conditions do not get it, and why I only get it
> at certain controls!
>
> Can anyone who hase more insight into the resource loader look into
> the problem?
>
>
> I can remember something along those lines already once was in there
> and has been fixed, but now it is here again (oh joy)
>
> Werner
>
>
> Werner Punz schrieb:
>> Catalin Kormos schrieb:
>>> Hi,
>>>
>>> Any of you experiencing problems using Dojo based components on IE,
>>> like modalDialog or inputSuggestAjax? i keep getting this kind of
>>> messages, and only on IE:
>>>
>>> Jan 29, 2007 9:48:13 PM
>>> org.apache.myfaces.renderkit.html.util.MyFacesResourceLoader
>>> serveResource
>>> SEVERE: Unable to find resource src/widget.js for component
>>> dojo.DojoResourceLoader. Check that this file is available in the
>>> classpath in sub-directory /resource of the package-directory.
>>>
>>> It works perfectly fine on Firefox, and it did worked on IE too, a
>>> few days ago. I'm using the latest 1.1.5 snapshots that i built from
>>> the SVN with facelets.
>>>
>> Ok I filed a bugreport on this one, I will start to investigate into
>> it tonight.
>>
>>
>
>
Re: Dojo widgets not working on IE
Posted by Werner Punz <we...@gmx.at>.
Ok, I am getting closer,
I upgraded the tomcat versions, the problem still persists.
Funny thing is, it is only on a Mac (running an intel Dual Core)
If I serve the file from linux on a single core notebook
in the same Tomcat configuration the problems are gone.
This looks like a timing issue, i am not sure if the mac
is at fault here, or the Dual core is triggering
something in the JVM, I got a similar report from
a user whom I am trying to fix some issues in the Fisheye for.
Anyway, dojo is not at fault here, the problem either is the jdk
or some resource loader code going haiwire.
The funny thing is, once I switched tomcats the client abort exception
stopped (maybe it was ignored due to different settings) but the result
of not working dojo controls persisted.
I will add a note in the jira report, someone else has to take
over that, I have to say this is beyound the domain where I am
good at :-(
Werner
Werner Punz schrieb:
> Ok I am ccing this into the devs list, some other people have to
> look into the issue as well!
>
>
> I think I found the cause of all evil regarding the non initializing
> components:
>
> 2007 21:46:29 org.apache.myfaces.shared_tomahawk.config.MyfacesConfig
> getStringInitParameter
> INFO: No context init parameter
> 'org.apache.myfaces.RESOURCE_VIRTUAL_PATH' found, using default value
> /faces/myFacesExtensionResource
> 31.01.2007 21:46:29
> org.apache.myfaces.shared_tomahawk.config.MyfacesConfig getCurrentInstance
> INFO: Starting up Tomahawk on the MyFaces-JSF-Implementation
> 31.01.2007 21:46:30 org.apache.myfaces.shared_impl.config.MyfacesConfig
> getBooleanInitParameter
> INFO: No context init parameter
> 'org.apache.myfaces.READONLY_AS_DISABLED_FOR_SELECTS' found, using
> default value true
> 31.01.2007 21:46:30 org.apache.myfaces.shared_impl.config.MyfacesConfig
> getStringInitParameter
> INFO: No context init parameter
> 'org.apache.myfaces.RESOURCE_VIRTUAL_PATH' found, using default value
> /faces/myFacesExtensionResource
> 31.01.2007 21:46:30 org.apache.myfaces.shared_impl.config.MyfacesConfig
> getCurrentInstance
> INFO: Starting up Tomahawk on the MyFaces-JSF-Implementation
> 31.01.2007 21:46:40
> org.apache.myfaces.renderkit.html.util.DefaultAddResource serveResource
> SCHWERWIEGEND: Error while serving resource:
> dojo.DojoResourceLoader/dojo.js, message : null
> ClientAbortException: java.net.SocketException: Broken pipe
> at
> org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:366)
> at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:433)
> at
> org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:314)
> at org.apache.catalina.connector.OutputBuffer.close(OutputBuffer.java:278)
> at
> org.apache.catalina.connector.CoyoteOutputStream.close(CoyoteOutputStream.java:103)
> at
> org.apache.myfaces.renderkit.html.util.MyFacesResourceLoader.writeResource(MyFacesResourceLoader.java:244)
> at
> org.apache.myfaces.renderkit.html.util.MyFacesResourceLoader.serveResource(MyFacesResourceLoader.java:217)
> at
> org.apache.myfaces.renderkit.html.util.DefaultAddResource.serveResource(DefaultAddResource.java:606)
> at
> org.apache.myfaces.webapp.filter.ExtensionsFilter.doFilter(ExtensionsFilter.java:128)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
> at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
> at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
> at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
> at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
> at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
> at
> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
> at
> org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
> at
> org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
> at
> org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
> at
> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
> at java.lang.Thread.run(Thread.java:613)
> Caused by: java.net.SocketException: Broken pipe
> at java.net.SocketOutputStream.socketWrite0(Native Method)
> at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
> at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
> at
> org.apache.coyote.http11.InternalOutputBuffer.realWriteBytes(InternalOutputBuffer.java:746)
> at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:433)
> at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:348)
> at
> org.apache.coyote.http11.InternalOutputBuffer$OutputStreamOutputBuffer.doWrite(InternalOutputBuffer.java:769)
> at
> org.apache.coyote.http11.filters.IdentityOutputFilter.doWrite(IdentityOutputFilter.java:117)
> at
> org.apache.coyote.http11.InternalOutputBuffer.doWrite(InternalOutputBuffer.java:579)
> at org.apache.coyote.Response.doWrite(Response.java:559)
> at
> org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:361)
> ... 22 more
>
>
> But the funny thing is, this does not happen always, something must be
> going badly wrong in the resource loader, which is code I have
> absolutely no clue about (sorry have not touched it so far)
>
> My personal assumption is, that the ie to my knowledge chokes on
> resources if you do not serve the filelength upfront, under certain
> conditions. I have no clue why I am getting this and others
> like cagatay under similar conditions do not get it, and why I only
> get it at certain controls!
>
> Can anyone who hase more insight into the resource loader look into the
> problem?
>
>
> I can remember something along those lines already once was in there
> and has been fixed, but now it is here again (oh joy)
>
> Werner
>
>
> Werner Punz schrieb:
>> Catalin Kormos schrieb:
>>> Hi,
>>>
>>> Any of you experiencing problems using Dojo based components on IE, like
>>> modalDialog or inputSuggestAjax? i keep getting this kind of messages,
>>> and only on IE:
>>>
>>> Jan 29, 2007 9:48:13 PM
>>> org.apache.myfaces.renderkit.html.util.MyFacesResourceLoader serveResource
>>> SEVERE: Unable to find resource src/widget.js for component
>>> dojo.DojoResourceLoader. Check that this file is available in the
>>> classpath in sub-directory /resource of the package-directory.
>>>
>>> It works perfectly fine on Firefox, and it did worked on IE too, a few
>>> days ago. I'm using the latest 1.1.5 snapshots that i built from the SVN
>>> with facelets.
>>>
>> Ok I filed a bugreport on this one, I will start to investigate into it
>> tonight.
>>
>>
>
>
Re: Dojo widgets not working on IE
Posted by Werner Punz <we...@gmx.at>.
Jeff Bischoff schrieb:
> Werner Punz wrote:
>> I think I found the cause of all evil regarding the non initializing
>> components:
>
> Was it money? :P
>
> My second guess is "women".
>
>
>
>
actually no...
the mac has some problems in my case.. ;-)
well close enough
Re: Dojo widgets not working on IE
Posted by Jeff Bischoff <jb...@klkurz.com>.
Werner Punz wrote:
> I think I found the cause of all evil regarding the non initializing
> components:
Was it money? :P
My second guess is "women".
Re: Dojo widgets not working on IE
Posted by Werner Punz <we...@gmx.at>.
Ok I am ccing this into the devs list, some other people have to
look into the issue as well!
I think I found the cause of all evil regarding the non initializing
components:
2007 21:46:29 org.apache.myfaces.shared_tomahawk.config.MyfacesConfig
getStringInitParameter
INFO: No context init parameter
'org.apache.myfaces.RESOURCE_VIRTUAL_PATH' found, using default value
/faces/myFacesExtensionResource
31.01.2007 21:46:29
org.apache.myfaces.shared_tomahawk.config.MyfacesConfig getCurrentInstance
INFO: Starting up Tomahawk on the MyFaces-JSF-Implementation
31.01.2007 21:46:30 org.apache.myfaces.shared_impl.config.MyfacesConfig
getBooleanInitParameter
INFO: No context init parameter
'org.apache.myfaces.READONLY_AS_DISABLED_FOR_SELECTS' found, using
default value true
31.01.2007 21:46:30 org.apache.myfaces.shared_impl.config.MyfacesConfig
getStringInitParameter
INFO: No context init parameter
'org.apache.myfaces.RESOURCE_VIRTUAL_PATH' found, using default value
/faces/myFacesExtensionResource
31.01.2007 21:46:30 org.apache.myfaces.shared_impl.config.MyfacesConfig
getCurrentInstance
INFO: Starting up Tomahawk on the MyFaces-JSF-Implementation
31.01.2007 21:46:40
org.apache.myfaces.renderkit.html.util.DefaultAddResource serveResource
SCHWERWIEGEND: Error while serving resource:
dojo.DojoResourceLoader/dojo.js, message : null
ClientAbortException: java.net.SocketException: Broken pipe
at
org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:366)
at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:433)
at
org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:314)
at org.apache.catalina.connector.OutputBuffer.close(OutputBuffer.java:278)
at
org.apache.catalina.connector.CoyoteOutputStream.close(CoyoteOutputStream.java:103)
at
org.apache.myfaces.renderkit.html.util.MyFacesResourceLoader.writeResource(MyFacesResourceLoader.java:244)
at
org.apache.myfaces.renderkit.html.util.MyFacesResourceLoader.serveResource(MyFacesResourceLoader.java:217)
at
org.apache.myfaces.renderkit.html.util.DefaultAddResource.serveResource(DefaultAddResource.java:606)
at
org.apache.myfaces.webapp.filter.ExtensionsFilter.doFilter(ExtensionsFilter.java:128)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
at
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Thread.java:613)
Caused by: java.net.SocketException: Broken pipe
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
at
org.apache.coyote.http11.InternalOutputBuffer.realWriteBytes(InternalOutputBuffer.java:746)
at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:433)
at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:348)
at
org.apache.coyote.http11.InternalOutputBuffer$OutputStreamOutputBuffer.doWrite(InternalOutputBuffer.java:769)
at
org.apache.coyote.http11.filters.IdentityOutputFilter.doWrite(IdentityOutputFilter.java:117)
at
org.apache.coyote.http11.InternalOutputBuffer.doWrite(InternalOutputBuffer.java:579)
at org.apache.coyote.Response.doWrite(Response.java:559)
at
org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:361)
... 22 more
But the funny thing is, this does not happen always, something must be
going badly wrong in the resource loader, which is code I have
absolutely no clue about (sorry have not touched it so far)
My personal assumption is, that the ie to my knowledge chokes on
resources if you do not serve the filelength upfront, under certain
conditions. I have no clue why I am getting this and others
like cagatay under similar conditions do not get it, and why I only
get it at certain controls!
Can anyone who hase more insight into the resource loader look into the
problem?
I can remember something along those lines already once was in there
and has been fixed, but now it is here again (oh joy)
Werner
Werner Punz schrieb:
> Catalin Kormos schrieb:
>> Hi,
>>
>> Any of you experiencing problems using Dojo based components on IE, like
>> modalDialog or inputSuggestAjax? i keep getting this kind of messages,
>> and only on IE:
>>
>> Jan 29, 2007 9:48:13 PM
>> org.apache.myfaces.renderkit.html.util.MyFacesResourceLoader serveResource
>> SEVERE: Unable to find resource src/widget.js for component
>> dojo.DojoResourceLoader. Check that this file is available in the
>> classpath in sub-directory /resource of the package-directory.
>>
>> It works perfectly fine on Firefox, and it did worked on IE too, a few
>> days ago. I'm using the latest 1.1.5 snapshots that i built from the SVN
>> with facelets.
>>
> Ok I filed a bugreport on this one, I will start to investigate into it
> tonight.
>
>
Re: Dojo widgets not working on IE
Posted by Werner Punz <we...@gmx.at>.
Catalin Kormos schrieb:
> Hi,
>
> Any of you experiencing problems using Dojo based components on IE, like
> modalDialog or inputSuggestAjax? i keep getting this kind of messages,
> and only on IE:
>
> Jan 29, 2007 9:48:13 PM
> org.apache.myfaces.renderkit.html.util.MyFacesResourceLoader serveResource
> SEVERE: Unable to find resource src/widget.js for component
> dojo.DojoResourceLoader. Check that this file is available in the
> classpath in sub-directory /resource of the package-directory.
>
> It works perfectly fine on Firefox, and it did worked on IE too, a few
> days ago. I'm using the latest 1.1.5 snapshots that i built from the SVN
> with facelets.
>
Ok I filed a bugreport on this one, I will start to investigate into it
tonight.
Re: Dojo widgets not working on IE
Posted by Werner Punz <we...@gmx.at>.
Werner Punz schrieb:
> I am aware of one single issue
> if you use xhmtl in conjunction with ie 6 and you have a simple <base
> href=... /> tag instead of <base ..></base>
> the ie starts to choke, this is a known issue in dojo-
> But this is hardly the problem catalin faces.
>
Ok I rechecked the sandbox on a build I did yesterday.
Dojo generally works, but the fisheye for me is broken (probably
an error which I introduced yesterday night by fixing
a few other issues)
the ajax autocomplete also is broken, probably a timing issue because
onload is used (this always is inherently evil), I or Gerald who
programmed the control have to look into that.
but all other controls utilizing dojo seem to work on me, so far.
The table suggest, the ppr, the split pane etc...
Catalin you can do a check here:
http://wuerg.kicks-ass.net:8080/tomahawk-sandbox-examples/
this is my private machine running on a yesterday night build of the
sandbox.
Re: Dojo widgets not working on IE
Posted by Werner Punz <we...@gmx.at>.
Gerald Müllan schrieb:
> Hi Catalin,
>
> are you sure that this is not a local problem? I have tried the latest
> Irian examples on IE, and the dojo corresponding stuff worked fine to
> me.
>
> And I don`t think that this is facelets related. (because examples are
> in jsp)
>
> cheers,
>
> Gerald
>
I am aware of one single issue
if you use xhmtl in conjunction with ie 6 and you have a simple <base
href=... /> tag instead of <base ..></base>
the ie starts to choke, this is a known issue in dojo-
But this is hardly the problem catalin faces.
Re: Dojo widgets not working on IE
Posted by Gerald Müllan <bi...@gmail.com>.
Hi Catalin,
are you sure that this is not a local problem? I have tried the latest
Irian examples on IE, and the dojo corresponding stuff worked fine to
me.
And I don`t think that this is facelets related. (because examples are in jsp)
cheers,
Gerald
On 1/29/07, Catalin Kormos <ca...@gmail.com> wrote:
> Hi,
>
> Any of you experiencing problems using Dojo based components on IE, like
> modalDialog or inputSuggestAjax? i keep getting this kind of messages, and
> only on IE:
>
> Jan 29, 2007 9:48:13 PM
> org.apache.myfaces.renderkit.html.util.MyFacesResourceLoader
> serveResource
> SEVERE: Unable to find resource src/widget.js for component
> dojo.DojoResourceLoader. Check that this file is available in the classpath
> in sub-directory /resource of the package-directory.
>
> It works perfectly fine on Firefox, and it did worked on IE too, a few days
> ago. I'm using the latest 1.1.5 snapshots that i built from the SVN with
> facelets.
>
> Thanks,
> Catalin
>
--
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
Re: Dojo widgets not working on IE
Posted by Werner Punz <we...@gmx.at>.
Catalin Kormos schrieb:
> Hi,
>
> I just tryied the sandbox examples app, after a fresh update from the
> SVN. The dojo based components don't work there neither, in IE. Is this
> a known issue? any ideea would be greatly appreciated.
>
Hi Catalin, not really a known issue...
since when has it been broken for you?
Re: Dojo widgets not working on IE
Posted by Catalin Kormos <ca...@gmail.com>.
Hi,
I just tryied the sandbox examples app, after a fresh update from the SVN.
The dojo based components don't work there neither, in IE. Is this a known
issue? any ideea would be greatly appreciated.
Thanks for your time,
Catalin
On 1/29/07, Catalin Kormos <ca...@gmail.com> wrote:
>
> Hi,
>
> Any of you experiencing problems using Dojo based components on IE, like
> modalDialog or inputSuggestAjax? i keep getting this kind of messages, and
> only on IE:
>
> Jan 29, 2007 9:48:13 PM
> org.apache.myfaces.renderkit.html.util.MyFacesResourceLoader serveResource
> SEVERE: Unable to find resource src/widget.js for component
> dojo.DojoResourceLoader. Check that this file is available in the
> classpath in sub-directory /resource of the package-directory.
>
> It works perfectly fine on Firefox, and it did worked on IE too, a few
> days ago. I'm using the latest 1.1.5 snapshots that i built from the SVN
> with facelets.
>
> Thanks,
> Catalin
>