How do I set ajax4jsf forceparser to false with Seam 2.0?
There used to be ajax4jsf filter but not anymore.
I want to disable ajax4jsf tidying up output on each request.
With older Seam version I could do this...
| + filter
| + display-nameAjax4jsf Filter/display-name
| +
@mgrouch:
How do you cache JNDI lookups?
I only have this in my components.xml. What would I have to add? Thanks!
core:init
| jndi-pattern=nmp/#{ejbName}/local
| debug=true/
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4067174#4067174
Reply to
Look at web-2.0.xsd
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4067176#4067176
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4067176
___
jboss-user mailing list
What are your config values for Ajax4Jsf's 'forceparse' in web.xml and Seam
'debug' in components.xml: core:init debug=false ?
I believe that by default, every request is routed through a Tidy filter, even
for non-Ajax pages. forceparse = false will ensure that only Ajax requests go
through
Can you change JSF setting to 'server' side state saving (in web.xml) and try
the tests again? With myfaces and these suggestions
http://wiki.apache.org/myfaces/Performance
it had dramatic effect.
I haven't tried with Sun's JSF 1.2, but client side state saving should have
negative impact on
Another thing:
JSF doesn't (in base components) let you to define a variable on a page.
So people quite often would write something like
#{hashMapBean[key].prop}
in many places on the page, which in fact leads to looking up hashMap many
times + using reflection to access property.
JSF also
And in your case you should migrate to MyFaces 1.1.5 and Tomahawk 1.1.6.
MyFaces 1.1.3 is too broken anyway to be used in production.
It would be interesting to compare Myfaces 1.1.5 performance
vs Sun's JSF 1.2 (with server side state for both) and see who wins...
View the original post :
Thanks for your reply. I am using server side states saving, and we don't have
hashmap lookup in our pages.
We can't migrate to MyFaces 1.1.5 and Tomahawk 1.1.6 due to compatibility
problem with seam 1.2.1. Also, MyFaces 1.1.5 doesn't work well with Seam 1.3.
So basically we can't change our
Try using one transaction per page load (preferably with one EJB call in case
of CMT). You might have to use wrapper transfer objects (which are considered
not necessary nowadays) to wrap entities of different types.
This made big difference in my case. Do not forget to cache JNDI lookups.
See
And local EJB interfaces vs remote ones to reduce serialization.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4057131#4057131
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4057131
Have you trieed Sun's JSF 1.2? Seam 1.3.0.A is pretty good and 1.3.0 should be
out soon... You also should use facelets instead of JSPs.
Tomahawk immediate=true helps a bit too on forms where you do not need
validation. Hibernate caching should be used. Reduce number of complicated
EL
And more ideas: Native IO on app server, JRockit JVM. Give JVM higher memory
settings. Use factories for stateless objects such as DAOs (so they are created
once and not repeteadly created/destroyed).
View the original post :
I think you would want to run your app with a profiler and find out,
empirically, where your app is spending its time. I think most commercial
profilers have trial versions, and there are a variety of ways to do this.
Your app design based on Seam/JSF is no doubt quite different than it was
mgrouch wrote : Use factories for stateless objects such as DAOs (so they
are created once and not repeteadly created/destroyed).
|
| ...
| Do not forget to cache JNDI lookups.
|
Again, you can certainly spend time doing this kind of stuff on the off chance
that it will improve
14 matches
Mail list logo
