[Design of JBoss Portal] - Re: JBOSS Portal, JSF, XHTML and AJAX !!!finally!!! :-)
by jacote
Excuse my probably stupid question, i don't know all portal specification but why is not possible to integrate an ajax library like ajax4jsf ? i tried many configuration but there is togheter an exception with the ajax4jsf Filter. There are difference between the boot process of a normal jsf application (togheter in jboss) and a jsf portlet application ? Because when i start the webapp stanadlone (also using myfaces from jbossweb and not bundled with my app) works fine, when i deploy within jboss-portal i've got this :
| Exception starting filter ajax4jsf
| java.lang.IllegalStateException: No Factories configured for this Application - typically this is because a context listener is not setup in your web.xml.
| A typical config looks like this;
| <listener>
| <listener-class>org.apache.myfaces.webapp.StartupServletContextListener</listener-class>
| </listener>
|
| at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:84)
| at org.ajax4jsf.framework.resource.InternetResourceService.init(InternetResourceService.java:58)
| at org.ajax4jsf.framework.ajax.xmlfilter.BaseFilter.init(BaseFilter.java:121)
| at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:223)
| at org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:304)
| at org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterConfig.java:77)
| at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3600)
|
I use jboss-as 4.0.4 and jboss-portal 2.4.
Thanks to all
bye
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3975703#3975703
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3975703
19 years, 3 months
[Design of JBoss ESB] - Re: GpListener reload config - new instance of listeners?
by mark.little@jboss.com
"jokum" wrote : Hi,
|
| Reinitialising all the listeners even when nothing is changed in the config can't be done I think. This even means the listeners are down for the time the reinit process takes.
|
| In my opinion we should be able to check whether the config has changed for a certain listener. Is yes we reinitialise this listener. If not we don't do anything.
|
There may be good reasons why the old listener thread has to die and a new one be started that aren't just related to whether or not the config has changed. However, in general I agree: I'd like to see if we can make this configurable and not just restart them all.
anonymous wrote :
| Regarding the threading. Every message coming to a listener results in spawning a new thread to be usedto execute the action. We should implement a thread pool using the concurrancy features in JDK 1.5(Executors).
|
| I think we should have a threadpool for each listener. If so we can tune the pool per listener. Listeners/actions taking lot of time to execute can get a bigger threadpool than others.
|
| I think this is not that much work.
|
We should definitely have a pool. Maybe when you've finished the Http client/server ..?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3975611#3975611
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3975611
19 years, 3 months