Clarrification about JSF and JBoss Seam

Hi ,
i have just started a couple of hours ago reading about JSF and JBoss Seam and it seems interesting ......
here is my question :
i have a form ( registration form ) written in jsp and a congratulation page (jsp page too)
is right what i am saying ?
JSF form ( input values) are sent to Seam to be validated under hibernate rules and then it( Seam ) responses to the JSF the entity bean .
again JSF form asks Seam to resolve the variable Register ( the value of the submit button in the form) and Seam returns the RegisterACtion
After that the same jsp page invoke the register method of the RegisterAction stateless session beam .inside the register method it redirect the user to congratulation jsp page .
do you think its correct
sorry folks for my english
Best reagrds
yacine fandi

or maybe if you can give a link of a good tutorial I�ll be greatfull
cheers yacine
Message was edited by:
fandi_yacine

Similar Messages

EJB annotations are not documented , versus Hibernate and JBoss seam do

I have an application that contains EJB3 annotations, Hibernate Annotations and JBoss Seam annotations in the java code.
When I generate the javadoc, the Hibernate and JBoss Seam annotations show by the side of the members and methods who has them, like, for example
@Name(value="authenticator")
@Scope(value=SESSION)
@AutoCreate
public class AuthenticatorImpl
<dt>extends java.lang.Object </dt><dt>implements </dt>
or, another example,
h3. facesContext{noformat}@In(value="org.jboss.seam.faces.facesContext",
create=true)
private javax.faces.context.FacesContext facesContext{noformat}
However, none of the EJB3 annotations included in the code are being dieplayed in the javadocs.
Does someone knows if there is any reason why this should happen?
This is my javadoc command:
javadoc -version -d doc2 -sourcepath src\model;src\action -classpath "lib/core.jar;lib/jboss-embedded-api.jar;lib/jsr250-api.jar;classes/test;lib/hibernate.jar;lib/log4j.jar;lib/testng.jar;lib/ojdbc14.jar;lib/hibernate-commons-annotations.jar;lib/hibernate-search.jar;lib/hibernate-entitymanager.jar;lib/drools-compiler.jar;lib/richfaces-impl.jar;lib/jboss-cache.jar;lib/jboss-seam.jar;lib/janino.jar;lib/hibernate-annotations.jar;lib/richfaces-api.jar;lib/ejb-api.jar;lib/mvel14.jar;lib/jbosssx.jar;bootstrap;lib/jbpm-jpdl.jar;lib/commons-beanutils.jar;lib/lucene-core.jar;lib/jgroups.jar;lib/jsf-api.jar;lib/jboss-el.jar;lib/el-api.jar;lib/antlr-runtime.jar;lib/jstl.jar;classes/model;lib/antlr.jar;lib/persistence-api.jar;lib/jsf-facelets.jar;classes/action;lib/richfaces-ui.jar;lib/mail.jar;lib/drools-core.jar;lib/jboss-seam-debug.jar;lib/hibernate-validator.jar;lib/servlet-api.jar;lib/jta.jar" -private mil.navy.med.rota.model mil.navy.med.rota.security mil.navy.med.rota.action.util mil.navy.med.rota.action.util.mpd mil.navy.med.rota.action.mpd mil.navy.med.rota.action.referrals mil.navy.med.rota.model.referrals mil.navy.med.rota.action.trainman mil.navy.med.rota.model.trainman -use -version -author -splitindex
The version of javadoc used is
Standard Doclet 1.6.0.0_3
Aticipated thanks!

Nevermind, the issue was that my persistence.xml did not contain the following property:
<property name="hibernate.hbm2ddl.auto" value="create-drop"/>
Therefore, the tables were not being created upon deployment.
Still, I would expect to see entity beans listed in the WebLogic console.

[ANNOUNCE] Exadel's Max Katz talks about JSF and AJAX

Hello,
I'm pleased to announce that JSF Central has just published an interview with Exadel senior systems engineer Max Katz. In the interview, Max talks about the key value and benefits of JSF, how it compares to other frameworks, why it is such a good fit for AJAX, and support for JSF technology at Exadel.
Here's a quote:
KM: What do you think is the key value of JSF?
MK: It's definitely the component-based approach to building web applications, and that it's a standard. JSF has introduced a new paradigm to web application development�building applications out of components. It allows developers to concentrate on application business logic rather than on little details of HTML and other plumbing that is common to all web applications.
Being a standard is very important for the community, and it helps vendors like Exadel create advanced visual tools. The component-based approach also gave rise to vendors building web components, which also benefits developers. Instead of spending two weeks on integrating a calendar feature into your application, you can now get a calendar component and concentrate on the business problem you're trying to solve.
KM: Let's talk about AJAX for a moment. What do you think makes JSF such a good fit for AJAX?
MK: It's the component approach that makes AJAX such a good fit for JSF. You develop your application out of JSF components that provide AJAX functionality. This approach hides all the complexity of JavaScript and XML. Developers don't need to work with error-prone JavaScript making sure it works in all browsers. The AJAX JSF components are tested, ready-to-use components. From the developer perspective, there is really no difference between using the commandButton standard component and using the JSF AJAX drag-and-drop components. The AJAX component is simply a lot more sophisticated in what it does. You can add AJAX functionality in a matter of minutes by using such components. It's very powerful.
To see the rest of the article, visit
http://www.jsfcentral.com/articles/katz-06-16-06.html.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Kito D. Mann
Author, JavaServer Faces in Action
http://www.virtua.com - JSF/Java EE consulting, training, and mentoring http://www.JSFCentral.com - JavaServer Faces FAQ, news, and info

The posted link led to a *404*.
I think I found the podcast and transcript under [article on JSFCentral.com|http://www.jsfcentral.com/listings/R2925?link] . Kito: is this the correct location?

About jsf and tiles

Good days , the following exception is happening:
javax.faces.FacesException
at de.mindmatters.faces.lifecycle.RenderResponsePhase.executePhase(RenderResponsePhase.java:53)
at de.mindmatters.faces.lifecycle.AbstractPhase.execute(AbstractPhase.java:37)
at de.mindmatters.faces.lifecycle.LifecycleImpl.executePhase(LifecycleImpl.java:166)
at de.mindmatters.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:226)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:138)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:363)
at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:712)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:406)
at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:211)
at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
at org.mortbay.jetty.Server.handle(Server.java:313)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:506)
at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:830)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:514)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:211)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:381)
at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:396)
at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442)
Caused by: java.lang.NullPointerException
at org.apache.myfaces.tomahawk.application.jsp.JspTilesViewHandlerImpl.renderView(JspTilesViewHandlerImpl.java:168)
at org.ajax4jsf.framework.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:101)
at org.ajax4jsf.framework.ajax.AjaxViewHandler.renderView(AjaxViewHandler.java:221)
at de.mindmatters.faces.lifecycle.RenderResponsePhase.executePhase(RenderResponsePhase.java:45)
... 21 more
my web.xml
<?xml version="1.0" encoding="UTF-8"?>
<web-app version="2.4" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
<context-param>
<param-name>contextConfigLocation</param-name>
<param-value>/WEB-INF/applicationContext.xml</param-value>
</context-param>
<context-param>
<param-name>com.sun.faces.verifyObjects</param-name>
<param-value>true</param-value>
<description>
Set this flag to true if you want the JSF
Reference Implementation to verify that all of the application
objects you have configured (components, converters,
renderers, and validators) can be successfully created.
Default value is false.
Poner a false cuando se ponga en produccion.
</description>
</context-param>
<context-param>
<param-name>com.sun.faces.validateXml</param-name>
<param-value>true</param-value>
<description>
Set this flag to true if you want the JSF
Reference Implementation to validate the XML in your
faces-config.xml resources against the DTD. Default
value is false.
Poner a false cuando se ponga en produccion.
</description>
</context-param>
<context-param>
<param-name>javax.faces.STATE_SAVING_METHOD</param-name>
<param-value>client</param-value>
<description>
Indica donde queremos guardar el estado de la aplicacion.
Poner a server cuando se ponga en produccion. antes probarlo!
</description>
</context-param>
<context-param>
<param-name>org.apache.myfaces.ALLOW_JAVASCRIPT</param-name>
<param-value>true</param-value>
<description>
Este parametro le dice a MyFaces si se va a permitir renderizar javascript.
Default: "true"
</description>
</context-param>
<context-param>
<param-name>org.apache.myfaces.PRETTY_HTML</param-name>
<param-value>true</param-value>
<description>
si es verdadero, el renderizado html estara formateado, permitiendo que se pueda leer
bien. En la fase de desarrollo, estara a true, cuando este en produccion, estara a false.
</description>
</context-param>
<session-config>
<session-timeout>
30
</session-timeout>
</session-config>
<welcome-file-list>
<welcome-file>
index.jsp
</welcome-file>
</welcome-file-list>

<listener>
<listener-class>org.springframework.web.context.request.RequestContextListener</listener-class>
</listener>
<listener>
<listener-class>org.springframework.web.context.ContextLoaderListener</listener-class>
</listener>
<servlet>
<servlet-name>Faces Servlet</servlet-name>
<servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
<load-on-startup>1</load-on-startup>
</servlet>

<servlet>
<servlet-name>TilesServet</servlet-name>
<servlet-class>org.apache.struts.tiles.TilesServlet</servlet-class>
<init-param>
<param-name>definitions-config</param-name>
<param-value>/WEB-INF/tiles-defs.xml</param-value>
</init-param>
<load-on-startup>2</load-on-startup>
</servlet>
<servlet-mapping>
<servlet-name>Faces Servlet</servlet-name>
<url-pattern>*.jsf</url-pattern>
</servlet-mapping>
<filter>
<filter-name>MyFacesExtensionsFilter</filter-name>
<filter-class>org.apache.myfaces.webapp.filter.ExtensionsFilter</filter-class>
</filter>
</web-app>
tiles-defs.xml
<?xml version="1.0" encoding="ISO-8859-1" ?>
<!DOCTYPE tiles-definitions PUBLIC
"-//Apache Software Foundation//DTD Tiles Configuration 1.1//EN"
"http://jakarta.apache.org/struts/dtds/tiles-config_1_1.dtd">
<tiles-definitions>
<definition name="Base" path="/paginas/plantillaBasica.jsp">
<put name="titulo" value="Base" type="string"/>
<put name="cabecera" value="/cabecera.jsp" type="page"/>
<put name="cuerpo" value="base" type="page"/>
<put name="pie" value="base" type="page"/>
</definition>
<definition name="/busquedaDosCajas.tiles" extends="Base">
<put name="titulo" value="Busqueda con dos cajas" type="string"/>
<put name="cuerpo" value="/paginas/cuerpoDosCajas.jsp" type="page"/>
</definition>
</tiles-definitions>
faces-config.xml
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE faces-config PUBLIC
"-//Sun Microsystems, Inc.//DTD JavaServer Faces Config 1.1//EN"
"http://java.sun.com/dtd/web-facesconfig_1_1.dtd">

<faces-config>
<application>
<view-handler>org.apache.myfaces.tomahawk.application.jsp.JspTilesViewHandlerImpl</view-handler>
</application>

<application>
<variable-resolver>
org.springframework.web.jsf.DelegatingVariableResolver
</variable-resolver>
</application>

<application>
<locale-config>
<default-locale>es</default-locale>
</locale-config>
</application>

<navigation-rule>
<from-view-id>*</from-view-id>
<navigation-case>
<from-outcome>succesNoJS</from-outcome>
<to-view-id>/paginas/listado.jsp</to-view-id>
</navigation-case>
<navigation-case>
<from-outcome>error</from-outcome>
<to-view-id>error.jsp</to-view-id>
</navigation-case>
</navigation-rule>
</faces-config>
index.jsp
<%@ page session="false"%>
<%
response.sendRedirect("busquedaDosCajas.jsf");
%>
anybody could help me? i dont know whats happening
regards a lot

first make sure you are using Tiles stand-alone (in Struts Sandbox)
add the follwoing servlet to your web.xml
<servlet>
<servlet-name>Tiles Servlet</servlet-name>
<servlet-class>org.apache.tiles.servlet.TilesServlet</servlet-class>
<load-on-startup>1</load-on-startup>
</servlet>
add the following context-param to your web.xml
<context-param>
<param-name>tiles-definitions</param-name>
<param-value>/WEB-INF/tiles.xml</param-value>
</context-param>
add the following to your faces-config.xml
<view-handler>org.apache.shale.tiles.TilesViewHandler</view-handler>
add the following dependency to your pom.xml
<dependency>
<groupId>org.apache.shale</groupId>
<artifactId>shale-tiles</artifactId>
<version>1.0.3</version>
</dependency>
that should be it.
Khaled

[ANN] JSF and ADF Faces Q&A online session today

Join us for an online discussion and ask your questions about JSF and ADF Faces. Today (Thu) at 10:00am PST (California time).
http://www.oracle.com/technology/tech/java/newsletter/seminars.html

Great here are a few IF there is time:
1. How round trips will JSF and ADF Faces take upon initial page load? In other words, does the initial page load come with data already populated? This makes a difference for those of us who have data heavy pages with lots of lag. Currently with ADF - UIX it seems as though the page is loaded and then round trips are taken to populate the data in the page.
2. Is a JSF and ADF faces project in future versions of JDeveloper more easily/efficiently source controlled than current ADF/UIX projects?
3. What is the extent of the involvement of the struts framework in JSF and ADF Faces?
Thanks very much Shay.
-brian

Jsf and Seam

Hi,
I have a JSF project and would like to add a Captcha on the new user page.
I see several examples with Seam.
http://www.digitalsanctuary.com/tech-blog/java/jboss/seam/captcha-with-seam-in-three-minutes.html
http://thelabdude.blogspot.com/2009/05/user-registration-solution-using-jboss.html
1) What do I need to add Seam to my app? Is it worth it from Captcha?
http://livedemo.exadel.com/richfaces-demo/richfaces/paint2D.jsf?s=glassX
I copied this into my app to test and get several errors. I did not see the problem?
I see a NullPointer error..but dont know where to set it.
SEVERE: Servlet.service() for servlet Faces Servlet threw exception
javax.faces.FacesException: Error send image
        at org.richfaces.renderkit.html.Paint2DResource.send(Paint2DResource.java:192)
        at org.ajax4jsf.resource.ResourceLifecycle.sendResource(ResourceLifecycle.java:221)
        at org.ajax4jsf.resource.ResourceLifecycle.send(ResourceLifecycle.java:146)
        at org.ajax4jsf.resource.InternetResourceService.serviceResource(InternetResourceService.java:225)
        at org.ajax4jsf.resource.InternetResourceService.serviceResource(InternetResourceService.java:141)
        at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:496)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
        at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
        at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
        at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
        at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
        at java.lang.Thread.run(Unknown Source)
Caused by: javax.faces.el.EvaluationException: org.apache.jasper.el.JspELException: /loginTest.jsp(62,2) '#{paintBean.paint}' java.lang.NullPointerException
        at org.richfaces.webapp.taglib.MethodBindingMethodExpressionAdaptor.invoke(MethodBindingMethodExpressionAdaptor.java:56)
        at org.richfaces.renderkit.html.Paint2DResource.send(Paint2DResource.java:182)
        ... 17 more
Caused by: org.apache.jasper.el.JspELException: /loginTest.jsp(62,2) '#{paintBean.paint}' java.lang.NullPointerException
        at org.apache.jasper.el.JspMethodExpression.invoke(JspMethodExpression.java:77)
        at org.richfaces.webapp.taglib.MethodBindingMethodExpressionAdaptor.invoke(MethodBindingMethodExpressionAdaptor.java:52)
        ... 18 more
Caused by: java.lang.NullPointerException
        at com.netfixup.java.PaintBean.paint(Unknown Source)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
        at java.lang.reflect.Method.invoke(Unknown Source)Anyone out there have and easy quick way to do Captcha with just JSF ? or should I go with Seam?
Thanks
Phil
Edited by: nohacks on Aug 20, 2009 4:08 AM

Going to seam might not be the answer to your problems. For one seam is not easy to get running on anything but a JBoss server (it is possible, but not easy). Secondly Seam is aimed at bringing JSF and EJBs closer together, among other things. Since you are running on Tomcat, I don't think you are using EJBs and therefore the use of Seam degrades greatly.
The root of the problem is easy enough to spot:
/loginTest.jsp(62,2) '#{paintBean.paint}'So what is this paintBean doing? If you have access to the code, you could check out the method that gives the error:
com.netfixup.java.PaintBean.paintto try and figure out what is null. SOMETHING is apparently not initialized properly, but unless the server logs can give you a hint what that something is, it is hard to help you further.

About numbering and section options... I need section numbers (1.1,1.2,1.3) that will automatically update as I remove ort add a page. Seams complicated. Could someone HELP me? Thanks

About numbering and section options... I need section numbers (1.1,1.2,1.3) that will automatically update as I remove ort add a page. Seams complicated. Could someone HELP me? Thanks

INDESIGN
I finally found it. Took me couple of hours. It is OK now
2014-11-18 11:05 GMT-05:00 kglad <[email protected]>:
About numbering and section options... I need section numbers
(1.1,1.2,1.3) that will automatically update as I remove ort add a page.
Seams complicated. Could someone HELP me? Thanks created by kglad
<https://forums.adobe.com/people/kglad> in Adobe Creative Cloud - View
the full discussion <https://forums.adobe.com/message/6940603#6940603>

Very big problem with JSF about FORM and "id=" for HTML form's elements and

I have discovered a very big problem with JSF about FORM and "id=" for HTML form's elements and java instruction "request.getParameterNames()".
Suppose you have something like this, to render some datas form a Java Beans :
<h:dataTable value="#{TablesDb2Bean.myDataDb2ListSelection}" var="current" border="2" width="50%" cellpadding="2" cellspacing="2" style="text-align: center">
<h:column>
<f:facet name="header">
<h:outputText value="Name"/>
</f:facet>
<h:outputText id="nameTableDb2" value="#{current.db2_name_table}"/>
</h:column>
</h:dataTable>
Everything works fine...
Suppose you want to get the name/value pairs for id="nameTableDb2" and #{current.db2_name_table} to process them in a servlet. Here is the HTML generated :
<td>id="j_id_jsp_1715189495_22:0:nameTableDb2">my-table-db2-xxxxx</td>
You think you can use the java instructions :
Enumeration NamesParam = request.getParameterNames();
while (NomsParam.hasMoreElements()) {
String NameParam = (String) NamesParam.nextElement();
out.println("<h4>"++NameParam+ "+</h4>);
YOU ARE WRONG : request.getParameterNames() wants the syntax *name="nameTableDb2" but JSF must use id="nameTableDb2" for "<h:outputText"... So, you can't process datas in a FORM generated with JSF in a Servlet ! Perhaps I have made an error, but really, I wonder which ?
Edited by: ungars on Jul 18, 2010 12:43 AM
Edited by: ungars on Jul 18, 2010 12:45 AM

While I certainly appreciate ejb's helpful responses, this thread shows up a difference in perspective between how I read the forum and how others do. Author ejb is correct in advising you to stay inside JSF for form processing if form processing is what you want to do.
However, I detect another aspect to this post which reminds me of something Marc Andreesen once said when he was trying to get Netscape off the ground: "there's no such thing as bad HTML."
In this case, I interpret ungar's request as a new feature request. Can I phrase it like this?
"Wouldn't it be nice if I could render my nice form with JSF but, in certain cases, when I REALLY know what I'm doing" just post out to a separate servlet? I know that in this case I'll be missing out on all the nice validation, conversion, l10n, i18n, ajax, portlet and other features provided by JSF".
If this is the case, because it really misses the point of JSF, we don't allow it, but we do have an issue filed for it
https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=127
If you can't wait for it to be fixed, you could decorate the FormRenderer to fix what you want.
I have an example in my JSF book that shows how to do this decoration. http://bit.ly/edburnsjsf2
Ed

Can i use ICE Faces and JBoss RichFaces combinely in JSF

hi
I can use ICE Faces and JBoss RichFaces in Jsf.But my requirement is that can i use both(ICE Faces&JBoss RichFaces) components in single .jspx page.is that possible
plz tell me
regards
niranjan

thanks for your reply
plz clarify what it means "JSF Implemetation".i.e for example can i place an Rich Face Component In ICEFaces Form
<ice:form>
<rfc:inputText/>
</ice:form>
because we have some components in IFaces and some in JBoss Rich Faces which are needed for our application.
Thanks & regards
nsanagari

Jboss seam setting problems...

1.ANT_HOME :C:\eclipse\plugins\org.apache.ant_1.6.5
2.JAVA_HOME:C:\jdk1.5.0_05
3.C:\jboss-jdk5-seam-403RC2
4.C:\jboss-seam beta 1.0
5.for EJB 3.0 :
i copy all files from jboss-EJB-3.0_RC2/lib to
C:\jboss-jdk5-seam-403RC2\server\default\deploy
5.build.properties :jboss.home = C:\jboss-jdk5-seam-403RC2\bin
6.i starting run.bat from C:\jboss-jdk5-seam-403RC2\bin
7.i building C:\jboss-seam beta 1.0\examples\booking build.xml the files from eclipse ant
this messsage;
Buildfile: C:\jboss-seam beta 1.0\examples\booking\build.xml
init:
[echo] Build Seam Booking Example 1.0
compile:
ejb3:
war:
ear:
deploy:
Seam.deploy:
[echo] Don't forget to set the path of jboss.home to JBoss AS 4.0.3!
[copy] Copying 1 file to C:\jboss-jdk5-seam-403RC2bin\server\default\deploy
[copy] Copying 1 file to C:\jboss-jdk5-seam-403RC2bin\server\default\deploy
BUILD SUCCESSFUL
Total time: 3 seconds
8.my http link;
http://localhost:8080/seam-booking or
http://localhost:8080/seam-registration/register.jsf
But:HTTP Status 404 - /seam-booking or seam-registration/register.jsf
What is the Problem?i not understand.
good lifes....!
fatih

This is the J2EE SDK support forum - and this looks like a JBoss product being deployed on JBoss itself. Thus, I'd say it's a little more likely to be a JBoss forum issue rather than a J2EE SDK forum post.
Did the JBoss deployment for the seam application run? Is it installed to the right context? The JBoss logs would tell you more about all this.

Problem logging on to the managed RAS using JBoss Seam

The app I am currently working on is using JBoss Seam. The sample jsp files you guys created were excellent. As a simple test I first tried to logon and export a report thru a different app using JSP and Tomcat and had no problems. I then copied the same code to my Seam application. I placed the logon and export report code into an Action class. I had to place the crystal jars into the seam/lib directory in order for seam to compile without errors. I now have seam running successfully, but get a runtime exception every time I try to logon to the RAS server.This codeenterpriseSession = sm.logon(username, password, cms, auth);causes this exception2006-11-20 12:00:49,551 ERROR [com.crystaldecisions.sdk.occa.pluginmgr.internal.PluginMgr] (getPlugins:292): unexpected exception java.lang.ClassCastException: com.crystaldecisions.sdk.plugin.desktop.pdf.internal.PDFFactoryAny ideas on how to correct this?Thanks in advance,Dave

Hi DaveI wasn't familiar with JBoss Seam before you mentioned it in your post. Looks like yet another application framework like Struts or JSF. The logon error shouldn't cause any kind of ClassCastException with a PDF factory. Have you tried commenting out all code except for the login. My only guess is that Seam changes the way that the code is executed so it appears that the error has to do with the login call. I really don't think this is possible.Start off real simple and uncomment the code as you go to see where the error is coming from. Rob Horne <a href="/blog/10">Rob's blog - http://diamond.businessobjects.com/blog/10</a>

How to integrate Jboss seam frame work with Jdeveloper 11

hi
Really i don't know how to integrate Jboss seam frame work with JDeveloper, actually my current project implementation was started with Netbeans, but i am planning to suggest my customer , use JDeveloper.
please provide the solution are any information, how to integrate the JBoss Seam frame work.
Thanks
Lakshmi

Hi,
JDeveloper 11 does not yet provide documentation about the integration with Seam (not only the technology but also the documentation is in early preview stage). However, this is an interesting question you ask and I'll follow up to see if we can get some document out in short term.
Frank

JBoss Seam

Hello,
i want use JSF and EJB and I have jboss-seam-1.0.1.GA.zip file, but I don't know what i have to do with this file. I can see the booking example, but i don't know how i can do a new application.
I use eclipse, jboss and myeclipse.
can you help me, please?

Hey your core exception root is related with naming server. Is there any setup to use InitialContext or name binding?

Simple question about JSF configuration

I am using Tomcat 5.0 in Windows XP SP2. When I create a web application with JSF and put it into {tomcat_home}\webapps\, everything works perfect. But when I add a context path in Tomcat's server.xml such like
<Context docBase="C:\works\java_projects\jsf_test" path="/jsf_test" reloadable="true" debug="0"/>
And then I put same web application into this context path and try the url like http://machinename:8080/jsf_test/test.faces, it gives me exception as follow
I wonder if anyone knows about that? Thanks a lot!!
type Exception report
message
description The server encountered an internal error () that prevented it from fulfilling this request.
exception
javax.servlet.ServletException: Servlet.init() for servlet Faces Servlet threw exception
 org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:462)
 org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118)
 org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
 org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799)
 org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705)
 org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577)
 org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)
 java.lang.Thread.run(Thread.java:595)
root cause
java.lang.NullPointerException
 javax.faces.webapp.FacesServlet.init(FacesServlet.java:144)
 org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:462)
 org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118)
 org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
 org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799)
 org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705)
 org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577)
 org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)
 java.lang.Thread.run(Thread.java:595)
note The full stack trace of the root cause is available in the Apache Tomcat/5.0.28 logs.
:

FacesServlet.init() processes only the followings: facesContextFactory = FactoryFinder.getFactory(FACES_CONTEXT_FACTORY);
applicationFactory = FactoryFinder.getFactory(APPLICATION_FACTORY);
application = applicationFactory.getApplication();
lifecycleFactory = FactoryFinder.getFactory(LIFECYCLE_FACTORY);
lifecycle = lifecycleFactory.getLifecycle(lifecycleId);NPE occurrs at the third line when it can't find ApplicationFactory.
Check how your container loads the class.

Is there an idiots guide to JSF and scope somewhere?

I am getting very confused with scope and JSF.
I have a page that just displays customer details (from CustomerBean extends Customer) with a button that should allow the user to change the customer details. Both pages use the same backing bean (is that recommended?).
customerDetail.jsp --> editCustomer.jsp
If I set the scope of CustomerBean to session, editCustomer sees the same customer as customerDetail. It seems to me that I shouldn't really be using session scope as I don't want a particular customer to hang around once I have finished with him. So what should I be doing?
Should customerBean be request scoped? If so how does editCustomer see it?
Or should I somehow destroy the session scoped customerBean when I have finished with it?
I also notice that some example jsps out there have a hidden field for the ID - should I simply look up the customer again from the database in editCustomer?
I also tried to add a <h:inputHidden value="#{customerBean}"/> but that broke my jsp.
I have bought and read the J2EE tutorial but I am still confused as to what the recommended way to drag the same Object through two jsp pages.
It's probably very simple but it's doing my head in ;-)
- David

Yeah, forming a model in your head to explain something can be painful, sometimes. This question has come up before, including where I work, and I've never really seen a comprehensive answer, so I'll just write one. :)
This is kind of a basic servlet concept, so I'll talk mostly about servlets. JSF is just flavor on top of this.
The lifetime of the request is: from the time the user hits "submit" until the time the response is fully rendered, whatever page that is.
So, you have a form the user has filled out and he/she hits "submit".
The HTTP POST request goes to the server (open port 80, write some "key: value" headers to satisfy the HTTP protocol requirements, followed by a stream of text that represents the users' form field values, wait for a response) which then proceeds to process it by parsing the incoming data and making a bunch of subroutine calls. The last set of subroutine calls basically involves a bunch of println() calls to write HTML into an output stream, which is the response the requesting browser is listening for. When that stream is done, the browser displays the html.
There's nothing that says the html that's displayed is the same as the html that originally held the form the user submitted. The first page is essentially garbage that somehow generated some form fields. The server could care less what it was, all it wants is the key=value pairs.
You could, if you were so inclined, code all those println()s yourself. That's straight servlet programming. It's totally under your control. You could code println( "<html><body>Hi, Mom!</body></html>"); and be done.
Or, you could write a JSP that, when compiled, turns into essentially a subroutine chock full o' println()s, and you could call that subroutine.
You do that with RequestDispatcher.forward(). It's just a subroutine call. (But don't do any more scribbling on the output stream after it returns, 'cause the stream's essentially been closed.)
It's all a big call tree with one thread of execution, single entry, single exit. One of the nice things about servlets is that the infrastructure makes available to you, in a contextual sorta way, the original request parameters plus whatever attributes you choose to attach to the request as your proceed w/your processing, kind of like charms on a charm bracelet (via ServletRequest.setAttribute()). (When I say "contextual", I mean the ServletRequest is passed in as a parameter to Servlet.service() so you can sling it around in your call tree.) Attributes you choose to attach while processing incoming form data are available later (for instance... in the subroutine that has all those println()s you so carefully coded up or allowed the JSP compiler to generate for you).
When the call tree is done (you've finally printed "</html>", marked the output stream "done" somehow and shipped all that HTML back out to the browser), the ServletRequest object that held the incoming form parameters plus whatever attribute cruft it accumulated is garbage collected. (I could write something poetic about Elysium and gamboling among daisies, but... nah.) So, the lifetime of that data associated w/the ServletRequest is the duration of that request-processing call tree.
JSF gives you a nice bunch of automatically-generated request attributes, corresponding to your request-scoped managed beans. It even very kindly transfers (via the value bindings) incoming form parameters into properties of beans which are attributed onto your ServletRequest, automagically.
So, if, in your JSP, you bind your form data to request-scoped bean properties (not the bean itself, but the bean's properties), those exact same bean properties will be visible on whatever JSP you eventually wind up on and it will be available to whatever intervening logic you code up ("Invoke Application" phase), and when the request is done, it all vanishes into thin air.
To be more specific to your question: yes, I believe it is recommended to have the same bean between pages. That's kind of the whole point. If you find yourself at the end of a request trying to destroy session data that was created at the beginning of that request, you should probably be using request scoping, not session.
I could be wrong, but I don't think you can bind an entire bean to an html element value. You bind bean properties. Of course, there's nothing to say that a bean property couldn't be... another bean!
In your particular case, I guess you have a bunch of display-only strings that come from your customer bean, plus a hidden "key" field somewhere. You could bind that hidden field to the customer.key property and Customer.setKey() would do whatever's necessary to get the rest of the data into the bean. That could be a d/b lookup or a map or array (cache) fetch. Or you could have a "current customer" in your session (that would have to be session-scoped, because you paint the detail screen w/one request and then paint the "edit" screen w/the same customer but in a different request). That "current customer" concept might cause you some problems later when you go multi-window or multi-frame in your webapp (truuuuuuuust me).
Also, I'm not sure why you need a CustomerBean separate from Customer. Can you just make Customer a bean and be done with it?
Holy cow, what an essay this turned out to be.
John Lusk.

Clarrification about JSF and JBoss Seam

Similar Messages

Maybe you are looking for