managed-bean

I'd wrote a session scoped managed bean to cache the sesion user specific info in a domino xpages application,just like the following codes: public class NBUserInfo { private String fullUserName; private String commonUserName; private String displayName; private String mailAddress; private String themeType; private String themeData; private Session _session; private Database _dbnames; private Name _dominoName; public NBUserInfo(){ System.out.println("初始化Managed Bean:NBUserInfo..."); _session = ExtLibUtil.getCurrentSession(); try { System.out.println(_session.getEffectiveUserName()); _dbnames =

In a simple demo web app using JSF 2 and Ajax, there is a method in the ManagedBean which receives messages from a JMS queue: @ManagedBean public class Bean { @Resource(mappedName = "jms/HabariConnectionFactory") private ConnectionFactory connectionFactory; @Resource(mappedName = "jms/TOOL.DEFAULT") private Queue queue; public String getMessage() { String result = "no message"; try { Connection connection = connectionFactory.createConnection(); connection.start(); Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE); MessageConsumer consumer = session.createConsumer

I'm using a hierarchy of classes and what I would optimally try to do is have @ManagedBean 's that inherit a class that have @ManagedProperty members and @PostConstruct methods. Specifically, will this work? : public class A { @ManagedProperty private C c; @PostConstruct public void init() { // Do some initialization stuff } public C getC() { return c; } public void setC(C c) { this.c = c; } } @ManagedBean @SessionScoped public class B extends A { // Content... } Thanks in Advance! The @ManagedProperty is inherited and will just work that way. The @PostConstruct will also be inherited,

I have a JSF Beans structure of this sort: @ManagedBean @ViewScoped public class ViewBeany implements Serializable { .... @ManagedProperty(value='#{sessionBeany}) transient private SessionBeany sessionBeany; ... public getSessionBeany() { ... }; public setSessionBeany(SessionBeany sessionBeany) { ... }; } The reason for the transient is that the session bean has some non-Serializable members and cannot be made Serializable. Will this work? If not, How can I solve the problem of not being able to serialize SesionBeany but having to keep it as a managed property under a view scoped bean? Thanks!

I've read a number of excellent posts and articles about dynamically binding fields in a custom control, but they have all assumed a document data source. I want to allow the possibility of a managed bean data source. I tried setting the property type to com.ibm.xsp.model.DataSource or com.ibm.xsp.extlib.model.ObjectDataSource and neither of those work with the following xml: <xp:inputText id="input" value="${compositeData.dsn[compositeData.fieldName]}" > </xp:inputText> Where the control is used I have passed in custom data like so: <xc:input dsn="#{issue}" fieldName="Database" > </xc:input>