JSF managed beans and xmlbeans

Hi,
I am having a jsf application,where I get data from a back end configuration service,which returns data in the form of xml,for which we already have compiled xmlbeans.At our side we recieve the response and parse it to get back the response.My question is- Is it advisable to use these xmlbeans within the jsf managed beans,or do we need to create pojos from the xmlbeans,before sending them to mbeans.Why I am asking such a question is-xmlbeans have a tight coupling with the backend
Thanks
-Bibin

I would suggest have pojo's. Below are my points
1) You man not need everything from the XMLBean always. Most of the times, you may need very little from the XMLBean. You can transfer the required information to the POJO. This would also save you from network overhead in case the backend is running on a separate machine.
2) Any changes to the backend code will not have any impact on your UI code.

Similar Messages

Invoking Web Service from JSF Managed Bean

Hi all,
I am trying to invoke a webservice from Managed Bean and getting an exception.
Server : WAS 6.1.0.2
Version :JSF 1.2
Type of WS Invocation : JAX-WS web services
IDE : RAD 7.0.0
I have set up the class path correctly and added relevant WS Client in EAR ....
Following is the exception am receiving :
[8/31/11 7:59:25:335 EDT] 0000002d WebApp E [Servlet Error]-[Faces Servlet]: javax.faces.el.EvaluationException: java.lang.NoClassDefFoundError: org.example.www.Sample_PortType
at com.sun.faces.el.ValueBindingImpl.getValue(ValueBindingImpl.java:170)
at com.sun.faces.el.ValueBindingImpl.getValue(ValueBindingImpl.java:123)
at javax.faces.component.UIOutput.getValue(UIOutput.java:147)
at com.sun.faces.renderkit.html_basic.HtmlBasicInputRenderer.getValue(HtmlBasicInputRenderer.java:84)
at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.getCurrentValue(HtmlBasicRenderer.java:204)
at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeEnd(HtmlBasicRenderer.java:171)
at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:754)
at javax.faces.webapp.UIComponentTag.encodeEnd(UIComponentTag.java:627)
at javax.faces.webapp.UIComponentTag.doEndTag(UIComponentTag.java:550)
at com.sun.faces.taglib.html_basic.InputTextareaTag.doEndTag(InputTextareaTag.java:651)
at com.ibm._jsp._sample._jspx_meth_h_inputTextarea_0(_sample.java:107)
at com.ibm._jsp._sample._jspx_meth_h_form_0(_sample.java:149)
at com.ibm._jsp._sample._jspx_meth_f_view_0(_sample.java:180)
at com.ibm._jsp._sample._jspService(_sample.java:77)
at com.ibm.ws.jsp.runtime.HttpJspBase.service(HttpJspBase.java:85)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:972)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:478)
at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:463)
at com.ibm.wsspi.webcontainer.servlet.GenericServletWrapper.handleRequest(GenericServletWrapper.java:115)
at com.ibm.ws.jsp.webcontainerext.AbstractJSPExtensionServletWrapper.handleRequest(AbstractJSPExtensionServletWrapper.java:168)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:308)
at com.sun.faces.context.ExternalContextImpl.dispatch(ExternalContextImpl.java:325)
at com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:249)
at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:87)
at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:239)
at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:118)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:198)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:972)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:478)
at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:463)
at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3129)
at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:238)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:811)
at com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContainer.java:1433)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:93)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:465)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:394)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:274)
at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminators(NewConnectionInitialReadCallback.java:214)
at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:113)
at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:152)
at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:213)
at com.ibm.io.async.AbstractAsyncFuture.fireCompletionActions(AbstractAsyncFuture.java:195)
at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:136)
at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:194)
at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:741)
at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:863)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1510)
Caused by: java.lang.NoClassDefFoundError: org.example.www.Sample_PortType
at java.lang.J9VMInternals.verifyImpl(Native Method)
at java.lang.J9VMInternals.verify(J9VMInternals.java:59)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:120)
at java.lang.Class.newInstanceImpl(Native Method)
at java.lang.Class.newInstance(Class.java:1263)
at java.beans.Beans.instantiate(Beans.java:219)
at java.beans.Beans.instantiate(Beans.java:63)
at com.sun.faces.config.ManagedBeanFactory.newInstance(ManagedBeanFactory.java:226)
at com.sun.faces.application.ApplicationAssociate.createAndMaybeStoreManagedBeans(ApplicationAssociate.java:291)
at com.sun.faces.el.VariableResolverImpl.resolveVariable(VariableResolverImpl.java:81)
at com.sun.faces.el.impl.NamedValue.evaluate(NamedValue.java:125)
at com.sun.faces.el.impl.ComplexValue.evaluate(ComplexValue.java:146)
at com.sun.faces.el.impl.ExpressionEvaluatorImpl.evaluate(ExpressionEvaluatorImpl.java:249)
at com.sun.faces.el.ValueBindingImpl.getValue(ValueBindingImpl.java:140)
Thanks in advance ..
Steve Bob

No you haven't, because
Caused by: java.lang.NoClassDefFoundError: org.example.www.Sample_PortType a relevant class can still not be found and Java really is not going to lie to you; this class is not on your application's classpath so it is either missing or put in the wrong place. Note that missing classes can be caused by you forgetting to properly redeploying your application - its usually something silly like that. Figure out what you did wrong and correct your mistake.
The fact that you have to mention that you "setup the classpath" is questionable; in web applications you don't touch the classpath at all. So what exactly did you do?

How can i get the realpath of my web application in jsf manage bean

in jsp, i can use application.getRealPath("/")
but in jsf how can i get the realpath in manage bean and initializean variable.
thanks

FacesContext aFacesContext = FacesContext.getCurrentInstance();
ServletContext context = (ServletContext)aFacesContext.getExternalContext().getContext();
String rootpath = context.getRealPath("/");
i use the code like that ,it can work , but when i click a button in my web page and call a function of java bean to read a file in "rootpath" , only odd number click it do well , even number click it do nothing and navigate to a blank page.
how can i do that ,.
my english is too pool ,sorry.

@EJB annotation in JSF managed beans not working

Hi all,
I've been trying to get the @EJB annotation to work in a JSF manged bean without success.
The EJB interface is extremely simple:
package model;
import javax.ejb.Local;
@Local
public interface myEJBLocal {
String getHelloWorld();
void setHelloWorld(String helloWorld);
and the bean code is simply:
package model;
import javax.ejb.Stateless;
@Stateless
public class myEJBBean implements myEJBLocal {
public String helloWorld;
public myEJBBean() {
setHelloWorld("Hello World from myEJBBean!");
public String getHelloWorld() {
return helloWorld;
public void setHelloWorld(String helloWorld) {
this.helloWorld = helloWorld;
When I try to use the above EJB in a managed bean, I only get a NullPointerException when oc4j tries to instantiate my managed bean. The managed bean looks like:
package view.backing;
import javax.ejb.EJB;
import model.myEJBLocal;
import model.myEJBBean;
public class Hello {
@EJB
private static myEJBLocal myBean;
private String helloWorld;
private String helloWorldFromBean;
public Hello() {
helloWorld = "Hello from view.backing.Hello!";
helloWorldFromBean = myBean.getHelloWorld();
public String getHelloWorld() {
return helloWorld;
public void setHelloWorld(String helloWorld) {
this.helloWorld = helloWorld;
public String getHelloWorldFromBean() {
return helloWorldFromBean;
Am I missing something fundamentally here? Aren't you supposed to be able to use an EJB from a JSF managed bean?
Thanks,
Erik

Well, the more I research this issue, the more confused I get. There have been a couple of threads discussing this already, and in this one Debu Panda states that:
"Support of injection in JSF managed bean is part of JSF 1.1 and OC4J 10.1.3.1 does not support JSF 1.1"
10.1.3.1 Looking up a session EJB with DI from the Web tier
But if you look in the release notes for Oracle Application Server 10g R3, it is explicitly stated that JSF 1.1. is supported. So I'm not sure what to believe.
I've also tried changing the version in web.xml as described here:
http://forums.java.net/jive/thread.jspa?threadID=2117
but that didn't help either.
I've filed a SR on Metalink for this, but haven't got any response yet.
Regards,
Erik

JSF managed beans Vs Enterprise beans

Hi friends,
what are the advantages/disadvantages of using enterprise beans/ JSF managed beans over JSF managed beans/Enterprise beans
regards
san

The primary difference between managed bean and enterprise bean is : enterprise bean will avail all the services provided by EJB container. where as managed bean cant avail all these.

Jsf managed beans

I am new to jsf so i want to know difference between managed bean and Back end bean. and when jsf creates instance of these beans.
how JSF read faces- config.xml file

@cbonneau
First, I must admit I didn't fully understand you.
Now, as for your question, managed beans are used to execute some business logic, like methods that you want to run when a form is submitted, or to hold some data that your page needs to access etc.
Model beans represent a domain object from your domain model. If you make an application used by a car rental agency, you'd probably have a model bean that represents a car.
And controller beans... well... I have no idea what could you mean by that :)
As for the MVC pattern, JSF more-or-less forces you to comply with it, so not much for you to do there.
And if you want a sample application, google a bit, you'll find plenty.

Problems integrating JSF managed bean with Session EJB with JDeveloper

HI All,
I am developeing a JSF-EJB application using Jdeveloper11g. On deploying the application I am getting the following errors on deployment.
<19/08/2010 2:53:49 PM EST> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1282193629318' for task '17'. Error is: 'weblogic.application.ModuleException: Could not setup environment'
weblogic.application.ModuleException: Could not setup environment
     at weblogic.servlet.internal.WebAppModule.activateContexts(WebAppModule.java:1499)
     at weblogic.servlet.internal.WebAppModule.activate(WebAppModule.java:442)
     at weblogic.application.internal.flow.ModuleStateDriver$2.next(ModuleStateDriver.java:375)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
     at weblogic.application.internal.flow.ModuleStateDriver.activate(ModuleStateDriver.java:95)
     Truncated. see log file for complete stacktrace
Caused By: weblogic.deployment.EnvironmentException: [J2EE:160101]Error: The ejb-link 'MetaDataBean' declared in the ejb-ref or ejb-local-ref 'MetaData' in the application module 'ViewControllerWebApp.war' could not be resolved. The target EJB for the ejb-ref could not be found. Please ensure the link is correct.
     at weblogic.deployment.BaseEnvironmentBuilder.addEJBLinkRef(BaseEnvironmentBuilder.java:453)
     at weblogic.deployment.EnvironmentBuilder.addEJBReferences(EnvironmentBuilder.java:485)
     at weblogic.servlet.internal.CompEnv.activate(CompEnv.java:157)
     at weblogic.servlet.internal.WebAppServletContext.activate(WebAppServletContext.java:3117)
     at weblogic.servlet.internal.WebAppModule.activateContexts(WebAppModule.java:1497)
     Truncated. see log file for complete stacktrace
>
<19/08/2010 2:53:49 PM EST> <Error> <Deployer> <BEA-149202> <Encountered an exception while attempting to commit the 1 task for the application 'data-catalog'.>
<19/08/2010 2:53:49 PM EST> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application 'data-catalog'.>
<19/08/2010 2:53:49 PM EST> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
weblogic.application.ModuleException: Could not setup environment
     at weblogic.servlet.internal.WebAppModule.activateContexts(WebAppModule.java:1499)
     at weblogic.servlet.internal.WebAppModule.activate(WebAppModule.java:442)
     at weblogic.application.internal.flow.ModuleStateDriver$2.next(ModuleStateDriver.java:375)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
     at weblogic.application.internal.flow.ModuleStateDriver.activate(ModuleStateDriver.java:95)
     Truncated. see log file for complete stacktrace
Caused By: weblogic.deployment.EnvironmentException: [J2EE:160101]Error: The ejb-link 'MetaDataBean' declared in the ejb-ref or ejb-local-ref 'MetaData' in the application module 'ViewControllerWebApp.war' could not be resolved. The target EJB for the ejb-ref could not be found. Please ensure the link is correct.
     at weblogic.deployment.BaseEnvironmentBuilder.addEJBLinkRef(BaseEnvironmentBuilder.java:453)
     at weblogic.deployment.EnvironmentBuilder.addEJBReferences(EnvironmentBuilder.java:485)
     at weblogic.servlet.internal.CompEnv.activate(CompEnv.java:157)
     at weblogic.servlet.internal.WebAppServletContext.activate(WebAppServletContext.java:3117)
     at weblogic.servlet.internal.WebAppModule.activateContexts(WebAppModule.java:1497)
     Truncated. see log file for complete stacktrace
Thanks
Edited by: user5108636 on 18/08/2010 22:46

Please find attached the source code of JSF managed bean, local business interface, session bean and web.xml
MANAGED BEAN_
package view.backing;
import java.util.List;
import javax.ejb.EJB;
import javax.faces.component.UISelectItems;
import javax.faces.component.html.HtmlSelectManyListbox;
import model.ejb.session.MetaDataBean;
public class SearchMetaDataBean {
@EJB MetaDataBean metaDataService;
private List<String> tables;
private List<String> columns;
private HtmlSelectManyListbox selectManyListbox1;
private UISelectItems selectItems1;
public void setTables(List<String> tables) {
this.tables = tables;
public List<String> getTables() {
return metaDataService.getTables();
public void setColumns(List<String> columns) {
this.columns = columns;
public List<String> getColumns() {
return columns;
public void setSelectManyListbox1(HtmlSelectManyListbox selectManyListbox1) {
this.selectManyListbox1 = selectManyListbox1;
public HtmlSelectManyListbox getSelectManyListbox1() {
return selectManyListbox1;
public void setSelectItems1(UISelectItems selectItems1) {
this.selectItems1 = selectItems1;
public UISelectItems getSelectItems1() {
return selectItems1;
LOCAL INTERFACE_
package model.ejb.session;
import java.util.List;
import javax.ejb.Local;
@Local
public interface MetaDataLocal {
public List<String> getTables();
public List<String> getColumns(String tableName);
SESSION BEAN_
package model.ejb.session;
import javax.ejb.Local;
import java.sql.Connection;
import java.sql.DatabaseMetaData;
import java.sql.ResultSet;
import java.sql.SQLException;
import java.util.ArrayList;
import java.util.List;
import javax.annotation.PostConstruct;
import javax.annotation.Resource;
import javax.ejb.Stateless;
import javax.sql.DataSource;
@Stateless(name="MetaData")
@Local
public class MetaDataBean implements MetaDataLocal{
@Resource(name="jdbc/DWDS")
private DataSource dataSource;
private Connection connection;
private List<String> tables = new ArrayList<String>();
private List<String> columns = new ArrayList<String>();
private DatabaseMetaData dmd;
@PostConstruct
public void initialize(){
try{
connection = dataSource.getConnection();
DatabaseMetaData dmd;
dmd = connection.getMetaData();
}catch(SQLException sqle){
sqle.printStackTrace();
public MetaDataBean() {
public List<String> getTables(){
try{
if (dmd ==null){
//System.out.println("Database meta data not available");
tables.add("None");
}else{
ResultSet rs = dmd.getSchemas();
ResultSet rs1 = null;
while(rs.next()) {
if (rs.getString(1).equalsIgnoreCase("AV_DATA")){
rs1 = dmd.getTables(null,rs.getString(1),"%",null);
while(rs1.next()) {
tables.add(rs1.getString(3));
}catch (SQLException sqle){
sqle.printStackTrace();
return tables;
public List<String> getColumns(String tableName){
try{
ResultSet rsColumns = dmd.getColumns("", "AV_DATA", tableName, null);
while(rsColumns.next()){
columns.add(rsColumns.getString(4));
}catch (SQLException sqle){
sqle.printStackTrace();
return columns;
WEB.XML_
<?xml version = '1.0' encoding = 'windows-1252'?>
<web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd"
version="2.5" xmlns="http://java.sun.com/xml/ns/javaee">
<servlet>
<servlet-name>Faces Servlet</servlet-name>
<servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
<load-on-startup>1</load-on-startup>
</servlet>
<servlet-mapping>
<servlet-name>Faces Servlet</servlet-name>
<url-pattern>/faces/*</url-pattern>
</servlet-mapping>
<ejb-local-ref>
<ejb-ref-name>MetaData</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<local>model.ejb.session.MetaDataLocal</local>
<ejb-link>MetaDataBean</ejb-link>
</ejb-local-ref>
</web-app>
Edited by: user5108636 on 18/08/2010 22:45
Edited by: user5108636 on 18/08/2010 22:46

Managed Beans and Data Access Object

I have a question / need help understanding how to configure backing bean and model objects so that memory and object creation/deletion is done as efficiently as possible.
1. I have a .jsf page with a form and a commandbutton that submits the form inputs to a backing bean (enrollispbean is backing bean)
<h:commandButton value="Enter" action="#{enrollispbean.insert}"/>
2. The backing bean is used for form handling - the insert() method is used to read the data fields from the form and create a SQL string that will be submitted to a model object, DbInsert, that is used as a generic data access object that connects to the database and insert the SQL string:
public class EnrollIspBean {
private String beanvar1="";
private String beanvar2= "";
// DbInsert is data access object
private DbInsert dbinsert = new DbInsert();
public String insert (){
String sqlstmt;
sqlstmt = "INSERT INTO ispmain VALUES(beanvar1, beanvar2,..)"
dbinsert.insert(sqlstmt);
return "success"; }
3. DbInsert is the data access object that contains a method, insert(), that accepts a sql string to insert into the database. This method contains the code to obtain a connection from the database connection pool and then execute the sql statement (note: error checking code not shown):
public class DbInsert {
public void insert(String sqlstmt) throws SQLException {
Connection conn = null;
GetDBConnection getdbconnection = new GetDBConnection();
PreparedStatement stmt = null;
conn = getdbconnection.getdbconn();
stmt = conn.prepareStatement(sqlstmt);
stmt.executeUpdate();
stmt.close();
conn.close();
return;
Where I need help understanding is how to set up the scope for the managed beans and data access object. Currently, I have the backing bean within the session scope (using the facesconfig.xml file). My main question is how to set up the scope for the Data Access Object - currently I do not have it as a managed bean within facesconfig.xml. Instead I am creating a new instance within the backing bean:
private DbInsert dbinsert = new DbInsert();
Is this the best way to do this? Will the DBInsert object now be tied to the session scope of the backing bean (i.e., when backing bean is deleted, the DbInsert object will be deleted from session scope as well.)
Ideally I would like the data access object to be available as a shared object throughout the life of the application. When I was programming using a servlet approach, I would have created a servlet to load on startup. Now that I'm using java server faces, I'm confused about the scope / how to efficiently set up a data access object that I want to be available to all backing beans in the application.
tnanks for any help understanding this.
Tom

I was thinking about setting the data access object as application scope so that it can be used by an backing bean to execute sql statements.
If I do set it as application scope, however, if I do this, do I still need to declare a new instance of the object from within each bean that uses the object?
For example do I need to declare a new instance of the data access object from within the bean? or, should I assume that there is always an instance of the bean available in the application scope, and if so, how do I reference it from within the bean?
Bean Code:
public class EnrollIspBean {
// DbInsert is data access object
private DbInsert dbinsert = new DbInsert();
Finally, I understand performance may be an issue if I have one instance of the data access object available in the application scope - is there a way to make multiple instances available in the application scope?
thanks

Difference between a Managed Bean and Backing Bean

hi
i am new to JSF made my 1st appl today ...
couldnt clearly understand difference between a Managed Bean and Backing Bean , anybody know the difference?
Regards
dsdsf

These are two terms that means the same .... A backing bean is a normal web term, in JSF specifically it is termed as managed bean as this' backing bean' configurations in faces-config.xml are termed within 'managed-bean ' tags.
Cutting the long story short its a bean class . period :)

What is difference between Managed Bean and Backing Bean?

What is difference between Managed Bean and Backing Bean? Please guide me how to create them and when to use them?
Please post sample for both beans.

Hi,
managed beans and backing beans are quite the same in that the Java object is managed by the JavaServer Faces framework. Manage in this respect means instantiation. The difference is that backing beans contain component "binding" references, which managed beans usually don't. Do backing beans are page specific versions of managed beans.
Managed beans are configured either in the faces-config.xml file, or using ADF Faces and ADFc, in the adfc-config.xml file
Frank
Edited by: Frank Nimphius on Jan 31, 2011 8:49 AM

Manipulate a payload inside a JSF Managed Bean

Hello guys,
Does someone know how can I consume programatically a human task payload inside a JSF Managed Bean?
Let we say that I need to extract some information from a payload to consume a service... After that, depending on the result, I update the payload with some data from the service to show to the user. Is that possible?
Any help would be greatly appreciated.
Thanks guys!!!

Out of the box now? No. Could something be added? I'm not sure it can.
Best bet, in my opinion, are code reviews. :)

Pageless Managed beans and operation bindings, design question

Hi,
I am using ADF Faces and ADF BC and JDev 10.1.3.
I want to declaratively execute an operation binding from a managed bean which does not have a page definition.
How can I create a page definition for a managed bean which will allow me to define and call operation bindings in the same way that you can in a backing bean?
In the past I have used the binding layer to get references to the AM and then execute the client methods directly.
How can I do this declaratively from a managed bean?
regards,
Brenden

Hi Steve,
a good example would be a managed bean which is used by many pages for provide dynamic page forwarding (using global forwards).
The page forwarding is based on what data the user has selected and the entry tasklist will have pages added and removed based on the users entered information.
At the moment I use references in the managed bean which get the binding context by evaluating #{data} to get a reference to the AM and directly call an client method, which calls a PL/SQL procedure and returns a global forward string. The AM is imported into the managed bean and methods called directly.
This is just one example, but probably the best I can come up with for now.
In a backing bean I can use an operation binding to call a method and get a result declaratively like this:
        BindingContainer bindings = getBindings();
        OperationBinding operation = bindings.getOperationBinding("getUserByEmail");
        operation.getParamsMap().put("email", email);
        String userName = (String)operation.execute();whereas in a managed bean I have to get direct references to the AM to call the method directly.
if there is a way to do this in the same way as backing beans it would seem a more abstracted and cleaner approach?
regards,
Brenden

How to use remote managed bean and JPA in JSF

Hi All,
I am familiar with referencing backing-beans and JPA properties where Glassfish and MySQL is running locally. However, is it possible to lookup these same properties using JNDI if they reside on remote servers? If so, what change is needed?
I would like to distribute the J2EE 5 application load including database by running Glassfish, MySQL on separate servers. This will put on the JSF (presentation-tier) components on it's own server while a secondary system will handle the middle tier processing and leaving the database activities to be carried out on another server. Not sure whether this is the right approach though. These hardware would run on both Solaris and Windows platforms.
Unfortunately, buying faster hardware is not an option.
Any assistance would be appreciated,
Jack

Hi Faissal,
Is your suggestion below:
//Lookup an EJB and use it
   YourRemoteBean bean = (YourRemoteBean ) ServiceLocator.findRemoteObject(jndiName); // ServiceLocator is a class that lookup
                                                                                                                                       // the remote objectis equivalent to the following lines:
Properties props = new Properties();
    props.setProperty("java.naming.factory.initial", "com.sun.enterprise.naming.SerialInitContextFactory");
            props.setProperty("java.naming.factory.url.pkgs", "com.sun.enterprise.naming");
            props.setProperty("java.naming.factory.state", "com.sun.corba.ee.impl.presentation.rmi.JNDIStateFactoryImpl");
            // optional. Defaults to localhost. Only needed if web server is running
            // on a different host than the appserver
            // props.setProperty("org.omg.CORBA.ORBInitialHost", "localhost");
            props.setProperty("org.omg.CORBA.ORBInitialHost", "remoteServer");
            // optional. Defaults to 3700. Only needed if target orb port is not 3700.
            // props.setProperty("org.omg.CORBA.ORBInitialPort", "3700");
            InitialContext jndiContext = new InitialContext(props);
            InitialContext jndiContext = new InitialContext();
            YourRemoteBean bean = (YourRemoteBean) jndiContext.lookup("ejb.YourRemoteBean");Thanks,
Jack

Share stateful session bean in JSF managed beans with different scope

Hi,
I have a JSF application and I want to try to use of stateful session beans.
So I created a new stateful session bean and its local interface.
@Stateful
public class StatefulSessionBean implements StatefulSessionBeanLocalInterface{
private String name;
@Local
public interface StatefulSessionBeanLocalInterface {
...In my JSF application I have a mananed bean with session context which registers the new interface by
this annotation
@EJB(name="sessionbeanref", beanInterface=StatefulSessionBeanLocalInterface.class) and set the name to something.
Now I want to fetch this name in another managed bean with request scope. So I looked up the bean and tried to get the name.
StatefulSessionBeanLocalInterface = (StatefulSessionBeanLocalInterface) new InitialContext().lookup("java:comp/env/sessionbeanref");
System.out.println(currentmailingbean.getName());but the name is null.
Why?

The xsd was created via the netbeans J2EE enterprise application dialog and I think its the most recent.
<?xml version="1.0" encoding="UTF-8"?>
<web-app version="2.5" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd">All other annotations seem to work.
Wouldnt the lookup completely fail if the deployment process thought that it is version 1.4 ?

JSF - Managed Beans instantiate Beans?

Hi, I�m new in JSF. I�d like to know if there is any way to configure in faces-config.xml a way to make a bean to be instantiate within do it explicity in the managed bean class.
Let me explain better, I have a form with two fields, login and password. I have a Bean called "User", with this two attributes and others. When I click on the commandButton, a method in the managed ben is called. What a wanna know is: do I have to declare the same bean�s attributes in the managed bean, generating gets and setters methods or there is a way to do this in the faces-config.xml?
Thanks.

I guess what you want to do is something like as follows:
(jsp file)<h:inputText value="#{managedBean.user.login}"/>(faces-config.xml)    <managed-bean>
        <managed-bean-name>managedBean</managed-bean-name>
        <managed-bean-class>ManagedBean</managed-bean-class>
        <managed-bean-scope>session</managed-bean-scope>
        <managed-property>
            <property-name>user</property-name>
            <value>#{userBean}</value>
        </managed-property>
    </managed-bean>
    <managed-bean>
        <managed-bean-name>userBean</managed-bean-name>
        <managed-bean-class>User</managed-bean-class>
        <managed-bean-scope>none</managed-bean-scope>
    </managed-bean>

JSF managed beans and xmlbeans

Similar Messages

Maybe you are looking for