[JBoss Portal] - How to keep portlet from resetting (losing state) when minim
by MicahWedemeyer
First, the specs:
JBoss Portal Version - v 2.4.1
Did you get Portal from CVS? or download it? - Downloaded bundle with JBoss AS
JBoss AS Version - Whatever comes as part of the bundle
Database Vendor and Version - Whatever comes as part of the bundle (HSQL?)
JDBC Connector and Version - Whatever comes as part of the bundle.
OS Platform - Fedora Core 6
Perhaps this is a simple configuration setting, but it is very frustrating for me (a new user). How can I keep the current portlet view from resetting when I minimize or maximize the portlet? For example, using the URL portlet, I can select one of the colors (red, white, blue) and see the result. However, as soon as I minimize or maximize, the display resets.
In the previous example, it's no big deal. However, if someone is editing a document, and decides to maximize the window, and all their work disappears, that is a huge deal.
Does anyone have any help with this?
Thanks,
Micah
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4013837#4013837
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4013837
19Â years, 2Â months
[JBoss Seam] - Re: Seam ICEFaces
by tony.herstellï¼ gmail.com
This is an good endorsement!
anonymous wrote :
| My impression is that icefaces is great technology, superior to other Ajax solutions out there
|
cross-post on Icefaces Forum
http://www.icefaces.org/JForum/posts/list/3676.page
>From MY experience (with Seam):
# Text Entry works ok as long as you don't move too quickly between the fields on a multi field form with partial submit "on" as this causes some sort of error in the back end and causes either:
**Too many xxxx queued up at the blocking bean (or something like this) from IceFaces
or
**No Long Running Conversation exception from SEAM.
(I have turned off partial-submit, for now, on all text entry fields due to this)
Note: A feature of using partial submit is that you have to leave a field for it to be validated... which is, initially, quite weired when you are sat with your cursor in the last field on a form and are waiting for it to fail validation!!!... also makes it really hard to disable the submit button based on "all" the fields being valid as again you are sat staring at the cursor in the last field wondering why the submit button is not enabled (for now I took this code out and never disable the submit button)!
Note:Hitting "enter" from a field to get the form to submit is non-trivial. There are few examples on the forum but it has not appeared in the IceFaces documentation yet.
# Selection works ok.
# Buttons and Links work ok.
# AutoComplete - Not Used Yet.
# Drag and Drop - Not used yet.
# Calendar now works with very latest build.
# Tree - Not used yet (but will be very very soon!)
# Menu Bar works ok (hard coded.. I think I may know how to make it dynamic now I have figured out about what "bindings" are.)
# Effects seem to work ok. (not sure how to do these dynamically)
# Table work great, paged, can filter by header etc. Still not managed to clear a defect where you are on page 3 and re-filter so only have 2 pages but are left looking at an empty page 3 - even after help in the forums... cant get the "binding" code to work.
# File Upload not working yet (so don't know about progress bar yet).
# Charts - Not used yet.
# The Stacking Panel Layout has worked so far (used twice).
Regardless to all this; you get these random errors
**Too many xxxx queued up at the blocking bean (or something like this) from IceFaces
or
**No Long Running Conversation exception from SEAM.
**Conversations just disappearing!
I hope this helps.
Please remember that IceFaces team and Seam Team are meeting this week to resolve issues. Expect great results!
Also, I may have my libraries set up incorrectly; have too many/few conflicting libraries etc... or my code may be a pile of poo!
Seam doc is excellent (but not for using iceFaces).
IceFaces doc is good, but spread over the Web Site (tutorials, tag library, component showcase + text that goes with them), but especially useful: http://www.icefaces.org/main/resources/tutorials.iface
:/
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4013836#4013836
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4013836
19Â years, 2Â months
[JBossCache] - Re: Should Fqns only contain String elements?
by genman
Non-String in FQN reasons:
1. I work with a lot of numbers and ranges. Converting from numeric to string and back again is inefficient and annoying.
2. Strings are bulky objects compared to Integer, especially in huge numbers.
3. Most CacheLoaders could support them. Admittedly this would require some work or restrictions.
For example, in the FileCacheLoader, you could simply use a PropertyEditor to convert the object to text and use this as the directory name. Store the PE used in the data file. Then, use a PropertyManager to convert the directory name back to an Object.
For BDB, convert the FQN to a byte array using serialization.
4. I would be nice to use package-private objects in FQN that would be invisible to the user to restrict data access. This is better than crafting strings that look like __HIDDEN_DATA_DO_NOT_TOUCH_PLEASE__ .
Allowing null in FQN does suck and there are probably some bugs in JBC handling them. That's a different thread perhaps.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4013825#4013825
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4013825
19Â years, 2Â months