Please help - OldJquery error with the screen using Richface

[aish]

Hi,

Can any one please help me with it. I have been waiting for some help on this. I have a page that has two calendar components (From Date and To Date) on it. When I launch the page. I get 'OldJquery undefined' error message.

I am using Richfaces 3.1.3. Can you please kindly help me with this. I have been banging my head against the wall for the last few days.

Thanks
Aish

[supernovasoftware.com]

Why would you be using 3.1.3 when 3.1.6 is out? Upgrade and you might get more help.

In fact if you can use JSF 1.2 then upgrade to 3.2.1.

Giving the fact that this is free software the developers are focused on new versions. Besides the fact that many bugs were fixed between 3.1.3 and 3.1.6.

[aish]

Hi Jason,

Thank you very much for responding.

I have IBM RAD 7 IDE for our development. That supports only JSF 1.1. Hence I could not upgrade to any version later than Richfaces 3.1.3.


I am having problem with the Calendar (oldJQuery undefined error), etc. Is there any work around or I should upgrade?

Please let me know

Thanks
Aish

[supernovasoftware.com]

Maybe I am wrong, but I was under the impression that 3.1.6 supported JSF 1.1.

Am I wrong?

[aish]

Hi Jason,

Thanks again for responding.

After looking at your first reply, I downloaded 3.1.6 and referred to the Richfaces_reference.pdf included in 3.1.6. Under Section 2 titled "Technical Requirements" it says "This is what you need to start working with RichFaces 3.1.0:" it does not refer to version 3.1.6.

I remember seeing in some other place that version 3.1.4 and above requires JSF 1.2 . I could not locate that information right now.

If you could confirm the requirements to use 3.1.6, I would be glad to upgragde it.

I am really having hard time getting to work few of the things and hence I could not roll out the application. I really like Rich Faces and have implemented them in my poject. But due to the small glitches in some places, I could not roll out. Can you please help me with them?

Thanks
Aish

[supernovasoftware.com]

If you cannot find the reference just try the jars. :)

[aish]

Hi Jason,

As you have suggested, I tried replacing my 3.1.3. jars with 3.1.6 jars. I get the same 'OldJQuery undefined' error message as soon as I open the page with the rich:calendar functionality.

I also split the page into pieces and tried loading each component separately to identify which component is causing this 'OldJquery undefined' message. It is the rich:calendar that is causing the error. As soon as I include the calendar component, I get the OldJQuery message.

Please help me to get over with this error message. Any help is greatly appreciated.

Thanks Aish

[supernovasoftware.com]

Try clearing your browser cache.

Try deleting the tmp and work directories if you are using JBoss.

Other than that I do not know what the problem is. Doing either of the following has helped me in the past, but I have not seen your specific error.

I am using Trindad and Richfaces together with Seam. I use the latest GA versions.

Maybe you have some other library that uses jQuery and there is a version conflict.

[aish]

Hi Jason,

As you have suggested, I cleared the browser history, temp files and cache. I am running WebLogic 9.2 server. I looked for the tmp folder to clear them but I did see some .war files, etc in it. I was not sure if it is ok to delete them. So I left it as it is.

After clearing the browser, I still get the OldJQuery error. I have 3 pages with calendar in it. It happens only for the first page open.

If I send the war file to you, would you be able to take a look at it and let me know your suggestions. If I am asking for much, please apologize me

Thanks a lot for responding
Aish

[achildress]

I too see this error occasionally, and have found no resolution for the problem. Did you? I have found though that although the error is thrown, the calendar seems to work just fine afterwards. Like I said, it only happens once in a while, so as long as our clients don't have debugging turned on in the browser (which they shouldn't) I don't believe it will be a problem. It is quite ugly though.