voyent
Compatibility with Blueprint (or other Ajax) components???  XML
Forum Index -> Tools
Author Message
burferd

Joined: 04/May/2006 00:00:00
Messages: 381
Offline


Does the 1.5.1 release resolve any of the compatibility issues with Ajax type components like Blueprint.

In particular, I need to integrate the Blueprint Google Map component with my application. I was unsuccessful with CE 1.0.1 and 1.5.0

I asked this question a while back and was lead to believe that 1.5.0 may have resolved these problems.

Have I missed something, or is there still a compatiblilty issue?

What I experience is that the Ajax Javascript is duplicated in the final page that is written to the browser. That, apparently renders the component useless.

I have posted this Javascript problem before and have not recieved any answer as to how to resolve the issue.

I see no point in attempting to update to any newer releases of ICEfaces until this issue is resolved.

Does anyone else have this problem, or am I doing something wrong?????????????

The lack of response to my previous posts is defining...
philip.breau


Joined: 08/May/2006 00:00:00
Messages: 2989
Offline


Hi,

This is in an inherent incompatiblitiy with the JavaScript. We have made a lot of progress in 1.5.x ICEfaces for integrating 3rd party components, but there will always be a problem with getting around JavaScript conflicts. I don't think there's anyway around this, unfortunately. As you found out, this is especially troublesome for JavaScript-heavy components like the Blueprint AJAX components.

Thanks,
Philip

.
steve31337

Joined: 17/Nov/2006 00:00:00
Messages: 7
Offline


Would using just-ice.jar work?
burferd

Joined: 04/May/2006 00:00:00
Messages: 381
Offline


I do not understand why there would be an incompatibility with JavaScript.

JavaScript has been so heavily used in web pages since Day One.

It seems like you have created a situation that gives developers a choice of either using JavaScript and Ajax type components or ICEfaces.

This should be a BIG asterisk when claiming JSF compatibility, since JSF allows JavaScript.

philip.breau


Joined: 08/May/2006 00:00:00
Messages: 2989
Offline


Hi,

Sorry, perhaps I wasn't clear in my last post. It's not that there's any inherent incompatibility with using external JavaScript in an ICEfaces context, but only that any external script that you put on the page has to play nicely with our own JavaScript. As I mentioned in the reply to your post about having a problem with the Sun AJAX Blueprints components, we just have to take a look at this and see if there's anything we can do. It might be possible for us to write wrappers for these components and get them working. Any external components that cause JS errors when used with ICEfaces will have to be looked at individually in the same way.

Thanks,
Philip

.
burferd

Joined: 04/May/2006 00:00:00
Messages: 381
Offline


The JavaScript problem that I encounter is fairly well defined and repeatable.

I have a JavaScript calendar that I use in my application.
That application needs to have a setup function within the jsp page to define the JSF button and text field components that are passed to the JavaScript component.

The problem is that when I have ANY Javascript in the jsp page, it does not work if the project is ICEfaces compatible. It does work if it is just standard JSF.

When I look at the html code generated for the page that is displayed, the javascript section in the page is duplicated.
 
Forum Index -> Tools
Go to:   
Powered by JForum 2.1.7ice © JForum Team