ICEsoft.org Forums: ICEfaces, ICEmobile, ICEpdf

One more for you, so the first tab in my portal application which loads a ton of icefaces portlets seemed fine (though I'm not sure my table row selector is working quite right, though the table row highlight for row selection seems to be working now), until I switched to a different table and then back to the first tab. At that point I get these errors rapidly again:

[window.dcev#34.async-connection] receive broadcast failed TypeError: _355.contentAsDOM() has no properties message=_355.contentAsDOM() has no properties

this is still on 4.3.4, I guess it doesn't seem to matter which version of liferay, I'll go back to DR2 and verify that's working as I would expect just in case.

Some additional information, I was using Liferay 4.3.5 when I got all the errors. When I switch to liferay 4.3.4, then I don't seem to get the errors but, it's making calls to the server at an extremely rapid pace (the reason when I get probably about 1000 errors a minute in the previous post). I'm probably now getting at least a 1000 posts a minute now without errors.

Clicking a tab to go to a page with a portlet that has the collapsible panels and a tabset on it, I get this error:

$A is not defined
(no name)()icefaces-d2d.js (line 153)
[Break on this error] return _29.apply(_2b,_2a.concat($A(arguments)));

I see this message a lot as well:

[window.dcev#30.async-connection.ui] [5213840] : connection closed

Hmmm, I'm also noticing that fonts seem to change on the collapsible panel that includes a table inside each collapsible pane (only on tables that have a row selector though).

Hmmm.. this isn't looking too good for the portal and DR3... I don't think anything could have been changed that would have affected icefaces like this.

At least it is with the firebug plugin, due to a huge number of errors that happen repeatedly when running my portlets (doesn't happen with DR2).

Here is the info (if I can make it before firefox hangs):

Firebug says:
file: "http://localhost:8084/swniosweb/xmlhttp/1199115619515/icefaces-d2d.js"

line number: 2990

message: "_355.contentAsDOM() has no properties"

name: "TypeError"

stack: "([object Object])@http://localhost:8084/swniosweb/xmlhttp/1199115619515/icefaces-d2d.js:2990\n((funct..."

Firebug is now showing 2900 errors in a matter of about 2 minutes or so....

Is there something that could be fixed for this? DR3 seems to fix some problems that were in DR2 and I would love to be able to use DR3.

Ohhh gotcha, thanks for clearing that up. I figured it had to be something silly.

I realized that what it is is because the session really has expired, and when this happens if it doesn't go away, then you need to restart your browser. Something is cached in the browser that will only be fixed if you restart. I've tried clearing the cache and everything else, but it never seems to work unless you restart the browser, then it's fine.

This problem isn't easily reproducible because ConcurrentModificationException problems are usually caused by a race condition or improper development in a multithreaded environment. If it doesn't happen all the time, then it probably is a race condition due to two requests coming in at the same time and operating on a shared collection between the two request threads (review the javadocs or articles on java Collections). This is more than likely a programming error and has nothing to do with icefaces. You have to code carefully in a server environmment because multiple threads will need to be handled. This problem won't go away by switching from icefaces.

You simply need to use a proper business logic tier to fix this problem, if you don't want to use a filter. If you are running into this problem, then it means you are letting code from your DAO layer seep into your application logic which isn't the best thing to do. This I believe is why hibernate works that way. You really need to implement a proper business logic tier, otherwise you have no choice but to dumb down functionality in your application so that you can lazily load objects. There isn't a "fix" for your problem because the problem is your implementation of hibernate, since hibernate works that way by design. This really doesn't have anything to do with icefaces.

If you were going to do this with maven2, you wouldn't "handle" the jsf dependencies, you should simply mark them as provided. That's up to the user's responsibility to include which ones they need, because a jsf implementation is expected to be choosen and provided for icefaces (not for icefaces to choose or assume for you). Using profiles would be making too many assumptions and too much maintenance.

As for icefaces in general in a maven 2 repo, that's really simple. There isn't anything complex you need. I can have the libraries for icefaces imported into my into my local network repository within a minute or two. If they change, I can update that extremely quickly as well. It would be convenient if they did, but it's easy enough once to do it yourself. Once you import the libraries, it will create a pom for you and you can add the distributed dependencies yourself (they aren't going to change often). I figure, you're getting a pretty cool library for free, what's a couple minutes of maintenance at most every couple of weeks?

I think you won't see icesoft do this though, because they lose the ability to track who is downloading and using their product. Even though the product is open source, they are still a business.

Can anyone point to in the right direction towards my goal of having an effect triggered when a new row is added to a datatable from a server initiated render? I may end up styling it differently as well but I'm thinking that might be more trouble than it's worth, so I'm thinking at least applying an effect, but I'm not sure how you can apply something like that when the server initiates a render? Is this even feasible to attempt? I'm thinking you'd maybe have to create the control yourself in your bean and use a binding in order to get this sort of control?

No problem, wasn't sure if I was doing something wrong. I'm surprised the liferay environment would somehow break that of all things.

I've been doing some comparing between the component-showcase example that works for the GMap component and what is in the portlet for the GMap component. I noticed that none of the google javascripts are referenced like they are in the component showcase... is there something in liferay that prevents from initializing properly? Is there something that would case the javascripts to not be initialized or will I need to wait for DR3 before I can play with the GMap component?

Thanks!

I tried it with a simple example and I always get javascript errors about components not being able to be found:

"GClientGeocoder is not defined"

This is the main part of the portlet:

<ice:form>
<ice:outputStyle href="./xmlhttp/css/xp/xp-portlet.css" />
<ice:messages errorClass="portlet-msg-error" fatalClass="portlet-msg-error" globalOnly="true" infoClass="portlet-msg-info" layout="table" warnClass="portlet-msg-warn" />
<ice:panelGrid id="gmapDemo" columns="1">
<ice:outputText value="The ice:gMap component with a default location set in the address attribute."/>
<ice:panelGroup styleClass="formBorderHighlight">
<ice:gMap address="New York City"/>
</ice:panelGroup>
</ice:panelGrid>
</ice:form>

Never mind, I see now that there is a bug report open for it.

Has anyone used the connection status indicator in a portal? I'm curious about how one could be used since you aren't supposed to have multiple ones on a page, but you could have an indeterminate number of portlets on a page.. there isn't really a way to link them all to a single one is there?

So I guess this message actually comes about I'm noticing because the session really has expired from icefaces point of view. The problem is that once the session expires with icefaces, if it has been idle long enough, there doesn't appear to be any way to get a new one without restarting your browser. You can logout and relogin with Liferay, but as soon as you hit an icefaces portlet, then it'll give you that message.

Is this is a known problem, or does this mean that I've got tomcat configured wrong? Is there anyway to restore normal application state without restarting your browser?