[Testimonials] - complete convertion to Jboss SEAM
by goose-dog
I've completely converted an online community previously done is a proprietary framework to JBoss SEAM. The core functions of the site has been done within 1 week learning SEAM from scratch. I'd have to say it's by far the smoothest transitions I've had in the past.
I supposed it's not really just because of SEAM, it's the fact that all the goodies are starting to come together at this time, EJB 3 being much eaiser to deal with than its previous version known night mare plagued with repetitive code, JSF being much more mature than it used to be with many more extentions such as tomahawk and ASF, and SEAM just ties all these things together without needing to write an extra 20 XML files just to make things work.
Here is the site I've used as a pilot for my first SEAM project http://vnl-online.com
By the way. There wouldn't happen to be a good book on SEAM yet is there? The docs are great but not quite as detail as I'd like.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3961786#3961786
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3961786
20 years, 1 month
[JBoss Portal] - Re: User Input Req for 2.6 Usability and UI enhancements
by Antoine_h
I don't know if this is a bug, but I saw nothing related to this in Jira.
In management portlet :
when an instance is not well defined in the descriptor (as an example, the portlet is not found because the name has an error).
when you call the instance "screen", you get an exception and nothing in the portlet (the error is given, but no more list of instances).
then you can't do anything on any instances.
=> in case of error on one instance object, allow to still have the list of instance, and may be the wrong instance also shown in the list (with error message for only this one).
also : since 2.4, it seems that the "<if-exists>overwrite</if-exists>" is not working anymore.
<deployment>
| <if-exists>overwrite</if-exists>
| <instance>
| <instance-id>MyPletInstance</instance-id>
| <portlet-ref>MyPortlet</portlet-ref>
| </instance>
| </deployment>
so if there is an error in the portlet-instances.xml definition ("MyPtlet" instead of "MyPortlet"), the instance is set in a wrong way in the database, and it is impossible to get the management portlet to show the instances.
It is not possible to suppress this instance in the management portlet, to have the new descriptor (corrected) used again.
what I did : stop jboss, suppress all the table in the database, correct the portlet-instances.xml, restart jboss....
not great...
I've just realized I could have suppress the whole portal in the management portlet, and then restart JBoss, but even... it is not really nice...
Many thanks,
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3961784#3961784
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3961784
20 years, 1 month