formatted values in param
Hi all,
I wondered how to store formatted values in a parameter. Say I would like to set a formatted date as a message property...
Something like this:
//---//
h:outputFormat value=#{messages['searchresults.lastModified']}
f:param value=#{searchObject.lastModified}
f:convertDateTime pattern=d MMM locale=nl_NL /
/f:param
/h:outputFormat
//---//
this doesn't work since the param tag doesn't allow body content... and it doesn't seem to have support for using converters
Is it possible to temporarely store the results of a conversion into a reusable variable?
-P
changing the style of the formfield with invalid arguments
Hi all,is it possible to change the style of an input field if validation fails (i.e. to add a red border)? I can figure out how to do this using a custom validator... but that would imply customizing ALL validators -P
Re: validation and custom messages
O.k. good to know!I'll have a look at what is there, and since it will save us the time of writing custom validators/convertors for each custom message I think we can put some time in extending the tomahowk and sandbox convertors; and submit them back to the community...
-POn 12/16/05, Mike Kienenberger [EMAIL PROTECTED] wrote:
Peter,I don't this is possible without writing your own custom validator yet.It might be addressed in the final version of JSF 1.2 viarequiredMessage and validatorMessage per-component attributes, or it
may have to wait until JSF 2.0.However, for tomahawk and sandbox validators and converters, we'reinterested in supporting a message attribute which allows end-usersto manually override a specific converter instance. It's already
there for the sandbox compareTo validator, but someone needs to takethe initiative and create similar attributes for our other validatorsand converters.Please feel free to open a JIRA issue and submit patches to move this
process along.-MikeOn 12/16/05, Peter Maas [EMAIL PROTECTED] wrote: Hi all, maybe I'm missing the obvious, but... is it possible to specify WHICH
errormessage to show if a specific valitor fails? say I have: t:inputText id=postcodeField value=#{ searchAddressBean.postcode} required=true
t:validateRegExpr pattern='\d{4}[a-zA-Z]{2}' / /t:inputText t:message id=postcodeFieldError for=""
styleClass=error / What I don't want to do is override the default errormessage used by the RegExpr validator, this would change its' behaviour througout the entire
application, I just want to say: if this specific validation fails, display THIS message... is it possible? -P
validation and custom messages
Hi all,maybe I'm missing the obvious, but... is it possible to specify WHICH errormessage to show if a specific valitor fails?say I have: t:inputText id=postcodeField value=#{
searchAddressBean.postcode} required=true t:validateRegExpr pattern='\d{4}[a-zA-Z]{2}' / /t:inputText t:message id=postcodeFieldError for="" styleClass=error /
What I don't want to do is override the default errormessage used by the RegExpr validator, this would change its' behaviour througout the entire application, I just want to say: if this specific validation fails, display THIS message...
is it possible?-P
myfaces in weblogic
Hi all,I'm trying to get a basic myfaces application to run on weblogic 8.1 but without any luck yet. I googled arround a bit and found some contradicting bits on form but no 'THIS is how to to it, THIS is why'. The problem I'm running into seems to be related to context initialisation:java.lang.ExceptionInInitializerError. at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java :822) at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:3236) at weblogic.servlet.internal.WebAppServletContext.preloadServlets(WebAppServletContext.java:3181) at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:3154) at weblogic.servlet.internal.HttpServer.preloadResources(HttpServer.java:654) at weblogic.servlet.internal.WebService.preloadResources (WebService.java:483) at weblogic.servlet.internal.ServletInitService.resume(ServletInitService.java:30) at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131) at weblogic.t3.srvr.T3Srvr.resume (T3Srvr.java:964) at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:359) at weblogic.Server.main(Server.java:32)A forum on the sun site recommends the use of a specific listener, which is not included in the myfaces distribution... another post on yet another forum recommended the use of a different servlet ( net.sourceforge.myfaces.webapp.MyFacesServlet) which is no part at of the myfaces distribution either?any help appriciated!-P
Re: myfaces in weblogic
wl version 8.11, so SP1... and I don't have the option to install additional service packs... hopefully this is not mandatory?-POn 12/6/05, Udo Schnurpfeil [EMAIL PROTECTED] wrote: Which service pack?UdoPeter Maas wrote: Hi all, I'm trying to get a basic myfaces application to run on weblogic 8.1 but without any luck yet. I googled arround a bit and found some contradicting bits on form but no 'THIS is how to to it, THIS is why'. The problem I'm running into seems to be related to context initialisation: java.lang.ExceptionInInitializerError . at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java :822) at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java :3236) at weblogic.servlet.internal.WebAppServletContext.preloadServlets(WebAppServletContext.java:3181) at weblogic.servlet.internal.WebAppServletContext.preloadResources (WebAppServletContext.java:3154) at weblogic.servlet.internal.HttpServer.preloadResources(HttpServer.java:654) at weblogic.servlet.internal.WebService.preloadResources (WebService.java :483) at weblogic.servlet.internal.ServletInitService.resume(ServletInitService.java:30) at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131) at weblogic.t3.srvr.T3Srvr.resume (T3Srvr.java:964) at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:359) at weblogic.Server.main(Server.java:32) A forum on the sun site recommends the use of a specific listener, which is not included in the myfaces distribution... another post on yet another forum recommended the use of a different servlet ( net.sourceforge.myfaces.webapp.MyFacesServlet) which is no part at of the myfaces distribution either? any help appriciated! -P
Re: myfaces in weblogic
Ah! O.k.I think I already tried this, but I'll give it a go. Supposively this jsp-api.jar needs to be jsp2.0 and is needed for the web.xml dtd?-POn 12/6/05, rosalba bochicchio [EMAIL PROTECTED] wrote: Hi Peter,I had your same problem and finally solved itincluding the file jsp-api.jar in the libdirectory of my project.Hope it helps,Rosalba--- Peter Maas [EMAIL PROTECTED] wrote: wl version 8.11, so SP1... and I don't have the option to install additional service packs... hopefully this is not mandatory? -P On 12/6/05, Udo Schnurpfeil [EMAIL PROTECTED] wrote: Which service pack? Udo Peter Maas wrote: Hi all, I'm trying to get a basic myfaces application to run on weblogic 8.1 but without any luck yet. I googled arround a bit and found some contradicting bits on form but no 'THIS is how to to it, THIS is why'. The problem I'm running into seems to be related to context initialisation: java.lang.ExceptionInInitializerError. at weblogic.servlet.internal.ServletStubImpl.prepareServlet ( ServletStubImpl.java :822) at weblogic.servlet.internal.WebAppServletContext.preloadServlet( WebAppServletContext.java:3236) at weblogic.servlet.internal.WebAppServletContext.preloadServlets( WebAppServletContext.java:3181) at weblogic.servlet.internal.WebAppServletContext.preloadResources( WebAppServletContext.java:3154) at weblogic.servlet.internal.HttpServer.preloadResources (HttpServer.java :654) atweblogic.servlet.internal.WebService.preloadResources (WebService.java:483) at weblogic.servlet.internal.ServletInitService.resume( ServletInitService.java:30) at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131) at weblogic.t3.srvr.T3Srvr.resume (T3Srvr.java:964) at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:359) at weblogic.Server.main(Server.java :32) A forum on the sun site recommends the use of a specific listener, which is not included in the myfaces distribution... another post on yet another forum recommended the use of a different servlet ( net.sourceforge.myfaces.webapp.MyFacesServlet) which is no part at of the myfaces distribution either? any help appriciated! -P __Yahoo! DSL – Something to write home about. Just $16.99/mo. or less.dsl.yahoo.com
Re: myfaces in weblogic
Hmmm,after installing SP4 the myfaces blank application works... adding the jsp2.0 jar didn't seem to help to much!-POn 12/6/05, rosalba bochicchio [EMAIL PROTECTED] wrote:yes,I think so. Let mi know if it works! --- Peter Maas [EMAIL PROTECTED] wrote: Ah! O.k. I think I already tried this, but I'll give it a go. Supposively this jsp-api.jar needs to be jsp2.0 and is needed for the web.xml dtd? -P On 12/6/05, rosalba bochicchio [EMAIL PROTECTED] wrote: Hi Peter, I had your same problem and finally solved it including the file jsp-api.jar in the lib directory of my project. Hope it helps, Rosalba --- Peter Maas [EMAIL PROTECTED] wrote:wl version 8.11, so SP1... and I don't have the option to install additional service packs... hopefully this is not mandatory? -P On 12/6/05, Udo Schnurpfeil [EMAIL PROTECTED] wrote: Which service pack? Udo Peter Maas wrote: Hi all, I'm trying to get a basic myfaces application to run on weblogic 8.1 but without any luck yet. I googled arround a bit and found some contradicting bits on form but no 'THIS is how to to it, THIS is why'. The problem I'm running into seems to be related to context initialisation: java.lang.ExceptionInInitializerError. at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java :822) at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:3236) at weblogic.servlet.internal.WebAppServletContext.preloadServlets(WebAppServletContext.java:3181) at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:3154) at weblogic.servlet.internal.HttpServer.preloadResources(HttpServer.java:654) at weblogic.servlet.internal.WebService.preloadResources (WebService.java:483) at weblogic.servlet.internal.ServletInitService.resume(ServletInitService.java:30) at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131) at weblogic.t3.srvr.T3Srvr.resume (T3Srvr.java:964) at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:359) at weblogic.Server.main(Server.java:32) A forum on the sun site recommends the use of a specific listener, which is not included in the myfaces distribution... another post on yet another forum recommended the use of a different servlet ( net.sourceforge.myfaces.webapp.MyFacesServlet) which is no part at of the myfaces distribution either? any help appriciated! -P __ Yahoo! DSL – Something to write home about. Just $16.99/mo. or less. dsl.yahoo.com __Yahoo! DSL – Something to write home about.Just $16.99/mo. or less. dsl.yahoo.com
Re: How to use a navigationMenuItem to call a HTML?
I've not tried this, but I think je could just put a simple a href="" in your menu pointing to the html page you are trying to link? Otherwise I would just rename it jsp... and put in in je navigation context... no backing bean required. On 11/24/05, Rafael Nami [EMAIL PROTECTED] wrote: Hi everyone. We're trying to call a .html from our navigationMenuItem, but it isn't working. If we try to declare it as a Action in the faces-config.xml, it will treat the html as a .faces, throwing a Exception. We're trying now to call a method from the backing bean that uses the facesContext to send a redirect to the html. Is this the only reasonable approach? Thanks and Best Regards Rafael Mauricio Nami
inheritance and
Hi all,
I'm probably missing something obvious, but how can I 'detect' the
existence of a property on a bean? I have a managed bean return a list
of users, which might can be a plain user or an extended 'customer'
class User{
String firstname;
String lastname;
String email;
// getters and setters
}
class Customer extends User{
String address;
// etc.
}
Now if I want to mix those objects in one single dataTable I cannot find a way to display properties from
customer objects the code will break on plain user objects, and complains about missing properties.
I tried using jstl inside the table, but I'm not sure how the 'test'
properties of iterated items in the dataTable... a simple
${!empty user.address} doesn't work.
Actually, I would prefer to NOT use jstl. but stick to JSF is it possible with the existing tags?
regards,
Peter
Re: How to use a navigationMenuItem to call a HTML?
Hmmm, did some testing... easiest way to do it seems to use the onclick handler of the commandNavication tag: t:commandNavigation2 value=google href="">http://www.google.com');/ works for me! -P On 11/24/05, Peter Maas [EMAIL PROTECTED] wrote: I've not tried this, but I think je could just put a simple a href="" in your menu pointing to the html page you are trying to link? Otherwise I would just rename it jsp... and put in in je navigation context... no backing bean required. On 11/24/05, Rafael Nami [EMAIL PROTECTED] wrote: Hi everyone. We're trying to call a .html from our navigationMenuItem, but it isn't working. If we try to declare it as a Action in the faces-config.xml, it will treat the html as a .faces, throwing a Exception. We're trying now to call a method from the backing bean that uses the facesContext to send a redirect to the html. Is this the only reasonable approach? Thanks and Best Regards Rafael Mauricio Nami
Re: inheritance and
I understand that this is possible, but how can I test this within a tableGrid component without jstl?On 11/24/05, Marius Kreis
[EMAIL PROTECTED] wrote:Hi Peter.Perhaps you can check for the class of the object with
user.class.nameI think this should query user.getClass().getName() and then youcan compare it to User or CustomerPeter Maas wrote: Hi all,
I'm probably missing something obvious, but how can I 'detect' the existence of a property on a bean? I have a managed bean return a list of users, which might can be a plain user or an extended 'customer'
class User{ String firstname; String lastname; String email; // getters and setters } class Customer extends User{ String address;
// etc. } Now if I want to mix those objects in one single dataTable I cannot find a way to display properties from customer objects the code will break on plain user objects,and
complains about missing properties. I tried using jstl inside the table, but I'm not sure how the 'test' properties of iterated items in the dataTable...a simple ${!empty user.address
} doesn'twork. Actually, I would prefer to NOT use jstl. but stick to JSF is it possible with the existing tags? regards, Peter
Re: inheritance and
Yep,
allready tried that errors on the fact the the specific object
doesn't have the requested property maybe I'll need to add an
additional domain object have ALL the methods and convert the
underlying objects on the backingbean... On 11/24/05, Marius Kreis [EMAIL PROTECTED] wrote:
Good point. You could useh:outputText value=#{user.address} rendered=#{
user.class.name eqCustomer}But I doubt that it works... I think the _expression_ wil be evaluatedfirst and then throw an exception... sorry.Peter Maas wrote:
I understand that this is possible, but how can I test this within a tableGrid component without jstl? On 11/24/05, *Marius Kreis* [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote: Hi Peter. Perhaps you can check for the class of the object with
user.class.name http://user.class.name I think this should query user.getClass().getName() and then you can compare it to User or Customer
Peter Maas wrote: Hi all, I'm probably missing something obvious, but how can I 'detect' the existence of a property on a bean? I have a managed bean return a
list of users, which might can be a plain user or an extended 'customer' class User{ String firstname; String lastname;
String email; // getters and setters } class Customer extends User{ String address; // etc.
} Now if I want to mix those objects in one single dataTable I cannot find a way to display properties from customer objects the code will break on plain user objects,and
complains about missing properties. I tried using jstl inside the table, but I'm not sure how the 'test' properties of iterated items in the dataTable...a simple ${!empty
user.address } doesn'twork. Actually, I would prefer to NOT use jstl. but stick to JSF is it possible with the existing tags?
regards, Peter
Re: inheritance and
I'm fully aware of the introspection/reflection api's in the sdk, but
this is not what I want, at least I hoped some support for
OO/Inheritance would be availlable in JSF
in plain java the problem wouldn't even need reflection/introspection!
I would be able to just use the instanceof operator in an if-statement
and cast the object to the needed type
in jstl this is also not a problem either:
${!empty bean.method}
will not fail is the bean doesn't have the requested property, this
counts as 'empty'
So, in your opinion, the only way to solve this problem would be:
write a custom component for rendering text which encapsulates the
exeption thrown by invocating a non-existent method (or tests if the
method is callable or not, which in most cases would be less
efficient) ?
regards,
Peter
On 11/24/05, Craig McClanahan [EMAIL PROTECTED] wrote:
On 11/24/05, Peter Maas [EMAIL PROTECTED] wrote:
Yep,
allready tried that errors on the fact the the specific object doesn't
have the requested property maybe I'll need to add an additional domain
object have ALL the methods and convert the underlying objects on the
backingbean...
Peter,
The APIs you are looking at to introspect properties in a class are the
same ones that a JSF implementation uses as it is processing value binding
expressions ... the bean introspection APIs that are built in to the JDK.
The APIs are all documented in the JavaBeans specification (for more
information start at
http://java.sun.com/products/javabeans/), but it goes
something like this:
BeanInfo beanInfo = Introspector.getBeanInfo(Customer.class);
PropertyDescriptor props[] = beanInfo.getPropertyDescriptors();
This gives you an array of descriptors for all the JavaBean properties
defined in this class, including Method objects pointing at the getter and
setter methods so you can use reflection APIs to call them dynamically.
If this is all a bit low level for your taste, you can also explore the
APIs in Commons BeanUtils
(http://jakarta.apache.org/commons/beanutils), which is a
dependency of both the MyFaces and RI JSF implementations (so you'll have it
available in your apps already).
Craig
On 11/24/05, Marius Kreis [EMAIL PROTECTED] wrote:
Good point. You could use
h:outputText value=#{user.address} rendered=#{ user.class.name eq
Customer}
But I doubt that it works... I think the expression wil be evaluated
first and then throw an exception... sorry.
Peter Maas wrote:
I understand that this is possible, but how can I test this within a
tableGrid component without jstl?
On 11/24/05, *Marius Kreis* [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Hi Peter.
Perhaps you can check for the class of the object with
user.class.name http://user.class.name
I think this should query user.getClass().getName() and then
you
can compare it to User or Customer
Peter Maas wrote:
Hi all,
I'm probably missing something obvious, but how can I 'detect'
the
existence of a property on a bean? I have a managed bean return
a
list
of users, which might can be a plain user or an extended
'customer'
class User{
String firstname;
String lastname;
String email;
// getters and setters
}
class Customer extends User{
String address;
// etc.
}
Now if I want to mix those objects in one single dataTable I
cannot find
a way to display properties from
customer objects the code will break on plain user objects,
and
complains about missing properties.
I tried using jstl inside the table, but I'm not sure how the
'test'
properties of iterated items in the dataTable... a simple
${!empty
user.address } doesn't work.
Actually, I would prefer to NOT use jstl. but stick to
JSF is it
possible with the existing tags?
regards,
Peter
application scope / singleton behaviour
Hi all, I tried to figure out if it is possible to share bean instances between different request. Currently the beans I have configured to be in application scope are instantiated for each request... is this the way it should work or am I doing something wrong? regards, Peter
Re: Rendered Property: Simple Test ( Try Again! )
Eeuhm,
i think 'renderMe' does not qualify as a typical javabean method. I think you should stick to the get/set/is paradigm:
public class TestBean{
String a = test;
public String getA(){
return(a);
}
public boolean getRenderMe(){
return(true);
}
}
and after this access the values using:
#{testBean.renderMe} or #{testBean.a}
of coarse the name of the bean you are referring to needs to be defined in the faces config.
regards,
-P
the methodOn 11/21/05, Elam Daly [EMAIL PROTECTED] wrote:
Howdy all,I'm trying to do
something very simple. I have an outputText component set
as outputText value=Here I am
rendered=#{TestBean.renderMe} /
The TestBean is simple as well:
public class TestBean { int i = 0; public boolean renderMe() { if( i%2 == 0 ) return true; else return false; }}I'm just trying to set the render state programmaticly, yet Tomcat keeps throwing this:
javax.faces.FacesException: Bean: com.whiteware.beans.TestBean, property: rendStatus org.apache.myfaces.context.servlet.ServletExternalContextImpl.dispatch(ServletExternalContextImpl.java:422) org.apache.myfaces.application.jsp.JspViewHandlerImpl.renderView
(JspViewHandlerImpl.java:234) org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:373) javax.faces.webapp.FacesServlet.service(FacesServlet.java:107) org.apache.myfaces.component.html.util.ExtensionsFilter.doFilter
(ExtensionsFilter.java:123)In fact, if I try to use any bean method at all, it always fails. Even something as simple as 'return true' etc.Any help would be appreciated,Elam
Re: application scope / singleton behaviour
The bean should acts as a central service locator for my jsf beans, and
apart from the per request initializations is works as a shine.
Logging info written in the beans' constructor shows that the bean is
instantiated every time over. The constructors are public, so the bean
is not a singleton; should it be?
the bean is injected into other managed beans like this:
managed-bean
description
Service locator of the business services
/description
managed-bean-nameserviceLocatorBean/managed-bean-name
managed-bean-class
com.dp.jsf.ServiceLocatorBean
/managed-bean-class
managed-bean-scopeapplication/managed-bean-scope
/managed-bean
managed-bean
managed-bean-nameCardsListBean/managed-bean-name
managed-bean-classcom.dp.jsf.CardListBean/managed-bean-class
managed-bean-scoperequest/managed-bean-scope
managed-property
property-nameserviceLocator/property-name
value#{serviceLocatorBean}/value
/managed-property
/managed-bean
Every time the CardsListBean is accessed, I see logging info from the
service locator constructor. Is the way I inject the locator into the
target bean correct or is this what causes the strange behaviour?
kind regards,
Peter
On 11/21/05, Bruno Aranda [EMAIL PROTECTED] wrote:
Something wrong may be happening. A bean in application scope shouldonly initialize one time and you can use it as long as yourapplication is alive without being initialized again... How are youchecking the initialization of that bean?
Bruno2005/11/21, Peter Maas [EMAIL PROTECTED]: Hi all,I tried to figure out if it is possible to share bean instances between different request. Currently the beans I have configured to be in
application scope are instantiated for each request... is this the way it should work or am I doing something wrong?regards,Peter
Re: application scope / singleton behaviour
It helped me in going over the sources to find other locations where
the bean might be used and I found a generic servlet which also
uses the bean... it is however jsf unaware... is it possible to
retrieve to bean from the jsf context from a generic servlet in the
same webapp?
On 11/21/05, Bruno Aranda [EMAIL PROTECTED] wrote:
Peter, I've just tried with a simple application to reproduce yourproblem and it works ok to me, so there must be something wrongthere... this is my code:[APP_BEAN]public class AppBacking{
private String time;public AppBacking() {System.out.println(APP backing initializing);time = new Date().toString();}public String getTime(){
return time;}public void setTime(String time){this.time = time;}}[REQUEST_BEAN]public class ReqBacking{private AppBacking appBacking;
public ReqBacking() {System.out.println(REQUEST initializing);}public AppBacking getAppBacking(){return appBacking;}public void setAppBacking(AppBacking appBacking)
{this.appBacking = appBacking;}}[/REQ_BEAN][JSP]h:form id=formh:panelGrid id=grid columns=2h:outputText value=#{
reqBack.appBacking.time}/h:commandButton value=test action="">/h:panelGrid/h:form[/JSP][CONFIG]managed-bean
managed-bean-nameappBack/managed-bean-namemanaged-bean-classorg.apache.myfaces.blank.AppBacking/managed-bean-classmanaged-bean-scopeapplication/managed-bean-scope
/managed-beanmanaged-beanmanaged-bean-namereqBack/managed-bean-namemanaged-bean-classorg.apache.myfaces.blank.ReqBacking/managed-bean-class
managed-bean-scoperequest/managed-bean-scopemanaged-propertyproperty-nameappBacking/property-namevalue#{appBack}/value
/managed-property/managed-bean[/CONFIG]And the output I am getting, while clicking the button:REQUEST initializingAPP backing initializingREQUEST initializing
REQUEST initializingREQUEST initializing...So you can see that everything is working as expected. It is not thecase, but if you were setting a bean with shorter lifespan to anotherbean (a request managed bean into an application managed bean, for
instance) an exception would be thrown.Hope that helps,Bruno2005/11/21, Peter Maas [EMAIL PROTECTED]: The bean should acts as a central service locator for my jsf beans, and
apart from the per request initializations is works as a shine.Logging info written in the beans' constructor shows that the bean is instantiated every time over. The constructors are public, so the bean is
not a singleton; should it be?the bean is injected into other managed beans like this:managed-beandescriptionService locator of the business services
/description managed-bean-nameserviceLocatorBean/managed-bean-namemanaged-bean-classcom.dp.jsf.ServiceLocatorBean
/managed-bean-class managed-bean-scopeapplication/managed-bean-scope/managed-beanmanaged-bean managed-bean-nameCardsListBean/managed-bean-name
managed-bean-classcom.dp.jsf.CardListBean/managed-bean-classmanaged-bean-scoperequest/managed-bean-scopemanaged-propertyproperty-nameserviceLocator/property-name
value#{serviceLocatorBean}/value/managed-property/managed-beanEvery time the CardsListBean is accessed, I see logging info from the
service locator constructor. Is the way I inject the locator into the target bean correct or is this what causes the strange behaviour?kind regards,Peter
On 11/21/05, Bruno Aranda [EMAIL PROTECTED] wrote: Something wrong may be happening. A bean in application scope should only initialize one time and you can use it as long as your
application is alive without being initialized again... How are you checking the initialization of that bean? Bruno 2005/11/21, Peter Maas
[EMAIL PROTECTED]: Hi all,I tried to figure out if it is possible to share bean instances between different request. Currently the beans I have configured to be in
application scope are instantiated for each request... is this the way it should work or am I doing something wrong?regards,
Peter
