Beehive & JSF

I saw on the beehive news groups that they are planning to release a service pack ( bug fix release ) at the end of this month
Is that going to be part of next Technology preview?
If it is not part of the next technology preview, can I safely replace the current jars with new beehive jars once they released it on beehive website?
Are you going to add myfaces as JSF implementation?
The code completion feature is not available for the JSF tags in Tech Preview 1 . Is it going to be part of Tech preview 2
Is there going to be Design View for JSP and JSF pages?

We are going to use the SUN RI and add myFaces from Apache post GA.
In theory you should be able to get one implementation out and plug the other one it, but we are not going to be able to test it all in time.
--alex

Similar Messages

JSF, JPF, Struts, SDO小探

一直对这几个概念不是非常清楚，一直对学习JPF心存疑虑。这几天，花了一点时间，大致上看了一下这几个东西的文档，有了一点收获，和大家探讨一下。
Struts：不用多说，大家都非常熟悉了。
Service Data Object(SDO)是JSR235讨论的一种简化数据访问的结构。在Web应用中，可以使数据源对开发人员透明。
J2EE标准的Java Server Faces(JSF)，BEA的JPF，都是基于Struts的，那么有一些什么区别呢？
JSF更多的是关注于页面的表现，很多结构和Struts非常相似。事实上，JSF的操刀者正是Struts的作者。可以在JSF中非常明显地看到，设计思路是在Struts上的提高和完善。比如，在Struts中，ActionForm事实上就是一个Bean，储存了数据。在JSF中，直接引入了Managed-Bean的概念，这些储存有数据的Bean可以直接放到页面上，这些Bean由程序员完成，美工只是直接把BEAN拖放到页面上，这样，进一步分割了Model和View，简化了开发过程，更加便于协作开发。
BEA的JPF更多地注重页面和数据的绑定。事实上，绝大多数的动态Web页都涉及到数据的读取和存储，JPF封装了大量的数据绑定功能，也简化了这一类的开发。
从IBM的红皮书上可以看到，现在IBM的所有涉及到JSF的例子，都用了WDO(WebSphere Data Object)。我的理解，这是SDO的一种。事实上，SDO还只
是处于JSR状态下，IBM实现了部分的SDO规范的功能。在IBM的例子中，可以看到，通过JSF和WDO/SDO，页面可以很容易地绑定数据，显示数据。
这一点，和BEA的JPF有异曲同工之妙。巧合的是，JSR235 SDO规范专家组的领头人正是BEA和IBM。
由此，我得出如如下的结论：
1、JPF是基于Struts的，将来会基于JSF
2、JPF和Struts/JSF不是一个层面的东西，JPF是比后两者更高级的框架
3、JPF在某种程度上，是BEA的SDO实现，将来的SDO正是规范中，必将有JPF的影子
4、虽然IBM现在在热推JSF，但是其红皮书中承认，JSF目前还是非常新的技术，并不完善，还有待于得到广泛的支持。Apache正在开发JSF-Struts库，
以便于Struts到JSF的迁移。所以，现在不必急追JSF，有了扎实的Struts知识，迁移到JSF不会太困难
5、学习JPF是安全的，（这和我以前的观点不同，以前对于JPF了解不深刻，向BEA致歉），将来的SDO会有JPF的影子。
欢迎大家讨论。

都劳动高人了，荣幸荣幸。
在JPF刚出现的时候，就得知BEA非正式地提供了可以迁移到Tomcat的工具。凭借BEA的实力，我毫不怀疑，将来的Java Control和JPF等，都可以顺利地移植到Tomcat或者WAS上运行，甚至连运行库都不需要，直接翻译成标准的Servlet代码。这是完全可行的。
我前面所说的都是从程序员开发的角度谈，不涉及运行时兼容的问题。Beehive把Workshop Runtime开源了，大家都可以来研究了，非常有利于Workshop的推广。但是，并不是开源的东西一定可以成为标准，承认吗？Tapestry也很不错，也是开源的，但是偏偏Struts最为市场接受，成为了事实上的标准。
我们是不是不能排除这样一种可能，Beehive开源了，也在一定程度上被广泛接受了，但是就是没有成为标准。成为标准的是JSF+SDO，假设这样。那么，作为程序员，我就有风险了。我花了时间精力，学习了Workshop Framework，也很精通Java Controls了。我毫不怀疑，我写的程序，可以被deploy到任何J2EE兼容的App Server上去。
另一方面，移植的过程是很复杂的，谁都不能保证移植的程序100%可运行。但是客户的平台是多样化的，出于以后维护的考虑，比如客户是小公司，一直运行Tomcat，他的维护工程师只懂JSP/Servlet/Struts，不懂JPF，那么为了维护，他也希望我用他懂得技术开发。即使我的JPF应用顺利部署到他的Tomcat上，他对今后他将面对的维护也会有畏惧。我总不能强迫他学JPF吧。
而且客户，都有一种惯性。用惯了.NET的，你向他推荐J2EE都很困难；同理，如果向他推荐非常先进的JPF，客户未必接受。
我，作为程序员，有交流的问题。比如说，JSP/Servlet，只要是J2EE程序员，大家都懂。无论在Team内部，还是到dev2dev，developerWorks, TSS上，大家都用同样的语言，JSP/Servlet规范和相关的术语。同样的道理，Struts由于是事实上的标准，也是可以被无障碍交流的，大家都懂ActionForm, ActionServlet。但是，只要Workshop一天没有成为标准，就有可能成为一种外语。我在BBS上跟人讲，NetUI:XXXX，不是人人都懂，我讲JCS,JPF，别人就未必懂。我只能到dev2dev,找你Hilaser请教。
其实，我认为，标准的含义对我而言，就是方便与人交流。UML语言诞生的初衷也是为了交流。虽然，大家都知道，JPF的底层就是Struts，但是偏偏封装后，名字改了，虽然都是巧克力，但是你说它叫“朱古力”，可我只知道他叫“巧克力”怎么办？那就要求我必须同时懂得Struts和JPF，自己给自己翻译了。或者用工具，把JPF转换成Struts，然后拿着机器生成的Struts代码和人讨论？
谈到这里，所有问题的根出现了，那就是
* BEA是否有足够的实力，把自己的专有技术推广成标准 ? *
是要所有的人都接受，成为标准；而不仅仅是开源。
这里有太多的非技术因素。且不说BEA的股价，庞然大物如IBM或者Oracle的态度。作为客户，他是否愿意押宝在BEA身上，明确BEA的JPF等技术就是将来的J2EE规范呢？恐怕比较难。即使庞大如IBM，客户也不会下这种赌注。客户一般都喜欢用成熟的技术。EJB2.0的规范出现是在哪一年？看看EJB2.0开始广泛运用又是在哪一年？
这也是，WebLogic这么多年来备受青睐的原因，因为他的技术最标准。所以，我的建议是，在JPF明确成为事实上的标准前，还是持观望态度比较合适。因为JPF和基于J2EE规范的不同Implementation不同，JPF的API是独特的，事实上一个程序员如果只精通JPF，而不懂Struts和JPF的关系的话，那他就真的被绑在BEA上了。对于Struts、JSP/Servlet群来说，他是一个外星人。那么用漂亮的Workshop开发JPF的人，又有多少会想到去了解底层的Struts呢？
其实，BEA为什么要重新搞一套特殊的API呢？Struts的不足，可以在保留Struts API的基础上，进行扩展，没有必要全部改头换面。保留Struts API的TAG要省多少事啊，再加上BEA的扩展，不一样可以吗。为什么全部换掉呢？
JPF的技术真的不错，但是，我只了解大致原理，我不去看具体的语法API，我等它成为标准。

Problem with JSF Beehive Page Flow

Hi
I created a JSF Beehive Page Flow and if i prove it outside a portal it works fine. The problem begins when I create a page flow portlet and put it in a portal. With debuging i saw that the begin method of the pageflow is executed and the oncreate of the JSF backing bean too, but the page is not displayed.
The begin method looks some like this:
     @Jpf.Action(forwards = {
@Jpf.Forward(name="success", path="/Index.faces")
     protected Forward begin() {
          return new Forward("success");
If anyone has any suggestions or working samples, they would be greatly appreciated.
Thanks.

If you created the portlet from pageflow, it won't work.
But you can try create portlet from "new->portlet->JSF portlet" and give the beginning faces page to the content path, (for your case "/Index.faces"). It will work. I have tried this way, it works on WLP 10
Jiameng Yu

Application not working with JSF 1.2

I am new to JSF. I am trying to create a sample application with JSF 1.2. I am using weblogic 10.0. I have followed the instructions give in the whitepaper to configure JSF 1.2.
http://download.oracle.com/technology/products/weblogic/portal/weblogic-portal-jsf-whitepaper.pdf
Deployment descriptor contains following content.
<?xml version="1.0" encoding="UTF-8"?>
<web-app id="WebApp_ID" 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">
<display-name>AlfaInsPortalWebApp</display-name>
<context-param>
<param-name>javax.faces.STATE_SAVING_METHOD</param-name>
<param-value>server</param-value>

</context-param>
<listener>
<listener-class>com.sun.faces.config.ConfigureListener</listener-class>
</listener>
<servlet>
<servlet-name>faces</servlet-name>
<servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>faces</servlet-name>
<url-pattern>*.jsf</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>faces</servlet-name>
<url-pattern>*.faces</url-pattern>
</servlet-mapping>
<welcome-file-list>
<welcome-file>index.jsf</welcome-file>
<welcome-file>index.faces</welcome-file>
<welcome-file>index.html</welcome-file>
<welcome-file>index.htm</welcome-file>
<welcome-file>index.jsp</welcome-file>
<welcome-file>default.html</welcome-file>
<welcome-file>default.htm</welcome-file>
<welcome-file>default.jsp</welcome-file>
</welcome-file-list>
     <session-config>
     <session-timeout>30</session-timeout>
     </session-config>
</web-app>
Weblogic.xml contains reference to following libraries
<?xml version="1.0" encoding="UTF-8"?>
<wls:weblogic-web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wls="http://www.bea.com/ns/weblogic/90" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd http://www.bea.com/ns/weblogic/90 http://www.bea.com/ns/weblogic/90/weblogic-web-app.xsd">
     <wls:container-descriptor>
          <wls:prefer-web-inf-classes>true</wls:prefer-web-inf-classes>
     </wls:container-descriptor>
<wls:context-root>AlfaInsPortalWebApp</wls:context-root>
<wls:library-ref>
<wls:library-name>jstl</wls:library-name>
<wls:specification-version>1.2</wls:specification-version>
<wls:exact-match>true</wls:exact-match>
</wls:library-ref>
<wls:library-ref>
<wls:library-name>wlp-tools-visitor-web-lib</wls:library-name>
<wls:specification-version>10.2.0</wls:specification-version>
<wls:implementation-version>10.2.0</wls:implementation-version>
</wls:library-ref>
<wls:library-ref>
<wls:library-name>wlp-tools-framework-web-lib</wls:library-name>
<wls:specification-version>10.2.0</wls:specification-version>
<wls:implementation-version>10.2.0</wls:implementation-version>
</wls:library-ref>
<wls:library-ref>
<wls:library-name>wlp-commonui-web-lib</wls:library-name>
<wls:specification-version>10.2.0</wls:specification-version>
<wls:implementation-version>10.2.0</wls:implementation-version>
</wls:library-ref>
<wls:library-ref>
<wls:library-name>wlp-framework-full-web-lib</wls:library-name>
<wls:specification-version>10.2.0</wls:specification-version>
<wls:implementation-version>10.2.0</wls:implementation-version>
</wls:library-ref>
<wls:library-ref>
<wls:library-name>wlp-clipper-web-lib</wls:library-name>
<wls:specification-version>10.2.0</wls:specification-version>
<wls:implementation-version>10.2.0</wls:implementation-version>
</wls:library-ref>
<wls:library-ref>
<wls:library-name>wlp-lookandfeel-web-lib</wls:library-name>
<wls:specification-version>10.2.0</wls:specification-version>
<wls:implementation-version>10.2.0</wls:implementation-version>
</wls:library-ref>
<wls:library-ref>
<wls:library-name>wlp-rest-full-web-lib</wls:library-name>
<wls:specification-version>10.2.0</wls:specification-version>
<wls:implementation-version>10.2.0</wls:implementation-version>
</wls:library-ref>
<wls:library-ref>
<wls:library-name>wlp-framework-rest-web-lib</wls:library-name>
<wls:specification-version>10.2.0</wls:specification-version>
<wls:implementation-version>10.2.0</wls:implementation-version>
</wls:library-ref>
<wls:library-ref>
<wls:library-name>wlp-rest-web-lib</wls:library-name>
<wls:specification-version>10.2.0</wls:specification-version>
<wls:implementation-version>10.2.0</wls:implementation-version>
</wls:library-ref>
<wls:library-ref>
<wls:library-name>wlp-light-web-lib</wls:library-name>
<wls:specification-version>10.2.0</wls:specification-version>
<wls:implementation-version>10.2.0</wls:implementation-version>
</wls:library-ref>
<wls:library-ref>
<wls:library-name>wlp-wsrp-producer-web-lib</wls:library-name>
<wls:specification-version>10.2.0</wls:specification-version>
<wls:implementation-version>10.2.0</wls:implementation-version>
</wls:library-ref>
<wls:library-ref>
<wls:library-name>wlp-framework-common-web-lib</wls:library-name>
<wls:specification-version>10.2.0</wls:specification-version>
<wls:implementation-version>10.2.0</wls:implementation-version>
</wls:library-ref>
<wls:library-ref>
<wls:library-name>wlp-framework-struts-1.2-web-lib</wls:library-name>
<wls:specification-version>10.2.0</wls:specification-version>
<wls:implementation-version>10.2.0</wls:implementation-version>
</wls:library-ref>
<wls:library-ref>
<wls:library-name>struts-1.2</wls:library-name>
<wls:specification-version>1.2</wls:specification-version>
<wls:exact-match>true</wls:exact-match>
</wls:library-ref>
<wls:library-ref>
<wls:library-name>wlp-services-web-lib</wls:library-name>
<wls:specification-version>10.2.0</wls:specification-version>
<wls:implementation-version>10.2.0</wls:implementation-version>
</wls:library-ref>
<wls:library-ref>
<wls:library-name>content-management-web-lib</wls:library-name>
<wls:specification-version>10.2.0</wls:specification-version>
<wls:implementation-version>10.2.0</wls:implementation-version>
</wls:library-ref>
<wls:library-ref>
<wls:library-name>beehive-netui-1.0.1-10.0</wls:library-name>
<wls:specification-version>1.0</wls:specification-version>
<wls:exact-match>true</wls:exact-match>
</wls:library-ref>
<wls:library-ref>
<wls:library-name>beehive-netui-resources-1.0.1-10.0</wls:library-name>
<wls:specification-version>1.0</wls:specification-version>
<wls:exact-match>true</wls:exact-match>
</wls:library-ref>
<wls:library-ref>
<wls:library-name>p13n-web-lib</wls:library-name>
<wls:specification-version>10.2.0</wls:specification-version>
<wls:implementation-version>10.2.0</wls:implementation-version>
</wls:library-ref>
<wls:library-ref>
<wls:library-name>jsf</wls:library-name>
<wls:specification-version>1.2</wls:specification-version>
<wls:implementation-version>1.2.3.1</wls:implementation-version>
</wls:library-ref>
</wls:weblogic-web-app>
When i start the application server following logs were obtained
Apr 9, 2010 7:09:32 AM com.sun.faces.config.ConfigureListener contextInitialized
INFO: Initializing Sun's JavaServer Faces implementation (1.2_03-b04-FCS) for context '/SampleJSF'
Apr 9, 2010 7:09:33 AM com.sun.faces.config.ConfigureListener contextInitialized
INFO: Completed initializing Sun's JavaServer Faces implementation (1.2_03-b04-FCS) for context '/SampleJSF'
Apr 9, 2010 7:09:33 AM com.sun.faces.config.ConfigureListener contextInitialized
INFO: Initializing Sun's JavaServer Faces implementation (1.2_03-b04-FCS) for context '/SampleJSF'
Apr 9, 2010 7:09:33 AM com.sun.faces.config.ConfigureListener contextInitialized
INFO: Completed initializing Sun's JavaServer Faces implementation (1.2_03-b04-FCS) for context '/SampleJSF'
When i invoke the application I get the following error.
java.lang.NoSuchMethodError: initView
     at com.sun.faces.lifecycle.RestoreViewPhase.execute(RestoreViewPhase.java:92)
     at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:248)
     at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117)
     at javax.faces.webapp.FacesServlet.service(FacesServlet.java:197)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
     at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
     at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:26)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3393)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(Unknown Source)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2140)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2046)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1366)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
Please help me in configuring JSF 1.2.

If you are new to JSF, then I'd try and simplify the environment in which you are working as the first step to achieving a successful outcome.
JSF 1.2 is a certified and well tested component of WLS, so we know it works. I'm not sure of the effect of all those additional modules you are adding in there -- it appears as if you have gotten a Faces implementation instantiated, but there could be some form of version difference/conflict since it can't find a method its looking for.
Using Oracle Enterprise Pack for Eclipse (http://www.oracle.com/technology/software/products/oepe/oepe_11115.html) you can build yourself out a pretty simple JSF application to get started from and deploy it to a WLS server. This would remove all the additional libraries you currently have, provide you with a bundled applicaton to deploy and give you a pretty good environment from which you can learn and experiment with JSF.
-steve-

JSF in Weblogic Portal

Hello Friends,
I am using first time JSF portlets in weblogic portal 10.2
I created jsf page and generated portlet based on it.
I added the portlet to my first page.
When I try to access the portal app I get below error.
I spent almost 3days on this but still not able to get it working. Some forums say that this issue is becaz of having sun jsf and my faces in the project class path. My project class path has none of them. Is there any other place I need to look for them.
I tried commenting jsf-ri in weblogic.xml and C:\bea\user_projects\domains\my_domain\config\config.xml.. BUT STILL NO LUCK :-)
Any help is greatly appreciated.
java.lang.UnsupportedOperationException
at javax.faces.context.FacesContext.getELContext(FacesContext.java:136)
at javax.faces.component.UIViewRoot.setLocale(UIViewRoot.java:888)
at org.apache.myfaces.application.jsp.JspViewHandlerImpl.createView(JspViewHandlerImpl.java:130)
at com.bea.portlet.adapter.faces.application.ViewHandlerImpl.createView(ViewHandlerImpl.java:47)
at org.apache.beehive.netui.pageflow.faces.internal.PageFlowViewHandler.createView(PageFlowViewHandler.java:174)
at org.apache.myfaces.lifecycle.LifecycleImpl.restoreView(LifecycleImpl.java:144)
at org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:66)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:244)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)........
Thanks for the help..

hello friends,
sorry i took long time to reply. i was on vacation for a month and then i forgot the pwd :-) I currently use default myfaces that comes with weblogic portal10.2.
I think the problem I mentioned in my first thread was becaz the project was originally started on wlp10 using weblogic workshop & sun jsf ri. So when I started using the inital project setup in wlp10.2 and weblogic workspace studio1.1 I ended up with that issue. To resolve the issue I followed the below steps..
1. recreated the project in wlp10.2 using weblogic workspace studio 1.1
2. while creating portal war i selected myfaces as my jsf implementation
It's hard to say what the excat problem was but doing this I could able to solve it.
Nag

Announcing: Developing JSF Portlets with WebLogic Portal Whitepaper

Just Released: Developing JSF Portlets with WebLogic Portal Whitepaper
A supplemental developer's guide has been published to help guide WLP 10.x customers that wish to use JSF as the web framework for building portlets on WebLogic Portal. This is a sizable document (150 pages) that covers a large number of topics. It also coaches developers on best practices and common pitfalls.
Important: It also clarifies the supported configuration of JSF within Portal Web Projects. Workshop for WebLogic by default configures a web project in a configuration that is not supported by WebLogic Portal. The guide explains how to address this:
* Change from the unsupported MyFaces JSF implementation to the supported Sun Reference Implementation (RI)
* Change from the unsupported "client" STATE_SAVING_METHOD to the supported "server"
The guide can be downloaded here:
http://download.oracle.com/technology/products/weblogic/portal/weblogic-portal-jsf-whitepaper.pdf
To help internet searches locate this document, the table of contents is reproduced below:
Introduction
1.1. Prerequisites...................................................................... 8
1.2. Applicable Versions............................................................ 8
1.3. Native Portlet Bridges and Standard Portlet Bridges .......... 8
1.4. JSF Portlet Support Roadmap ........................................... 9
1.5. Whitepaper Structure ....................................................... 10
1.6. Look Before You Leap ..................................................... 10
1.7. For More Information........................................................ 10
Part 1: Converting JSF Applications into Portlets
2. IDE Support for JSF Portlets Chapter ...................................... 12
2.1. Workshop for WebLogic – WebLogic Portal's Supported IDE 12
2.2. Workshop Features for JSF Support in WebLogic Portal.. 12
3. Introduction to JSF Portlets Chapter ........................................ 18
3.1. Creating Your First JSF Portlet......................................... 18
3.2. Essentials of JSF Portlet Views........................................ 21
3.3. WebLogic Portal Artifacts................................................. 22
4. Configuring JSF within WebLogic Portal Chapter..................... 24
4.1. JSF Library Modules in WebLogic Server ........................ 24
4.2. Installing the JSF Libraries into a Portal Web Project ....... 25
4.3. JSF Configuration Settings............................................... 27
4.4. Configuring JSF 1.2 ......................................................... 29
4.5. Building an Unsupported JSF Implementation Library Module 31
4.6. Faces Configuration is Web Application Scoped.............. 31
5. Navigation within a JSF Portlet Chapter................................... 33
5.1. Navigating within a Portlet with the JSF Controller ........... 33
5.2. Redirects.......................................................................... 34
6. Namespacing Chapter ............................................................. 35
6.1. Namespacing Managed Bean Names.............................. 35
6.2. Client ID Namespacing with the View and Subview Components 35
6.3. Client ID Namespacing with the WLP NamingContainer .. 36
7. Logging, Iterative Development, and Debugging Chapter ........ 39
7.1. Logging............................................................................ 39
7.2. Iterative Development ...................................................... 39
7.3. Debugging ....................................................................... 40
8. Custom JavaScript Chapter ..................................................... 42
8.1. DOM Manipulation within a JSF ....................................... 42
8.2. Form Validation within a JSF Portlet ................................ 45
9. Preparing JSF Portlets for Production Chapter ........................ 46
9.1. Configuration.................................................................... 46
9.2. Performance and Scalability............................................. 47
9.3. Security............................................................................ 49
9.4. Localization...................................................................... 50
Part 2: Interacting with the Portal Environment
10. Native Bridge Architecture Chapter ...................................... 54
10.1. Container Architecture Overview.................................. 54
10.2. Container Architecture.................................................. 54
10.3. Container Interactions .................................................. 55
11. Interportlet Communication Chapter .................................... 56
11.1. Using Session and Request Attributes for IPC (Anti-pattern) 56
11.2. Using the WLP Event Facility for IPC with JSF Portlets 56
11.3. Notifications ................................................................. 60
11.4. Comparison of the IPC Approaches ............................. 60
12. Scopes Chapter ................................................................... 62
12.1. Conceptual Scopes for Standard JSF Applications ...... 62
12.2. Conceptual Scopes for Portal Applications................... 63
12.3. Implementation Patterns for Portal Scopes .................. 63
13. State Sharing Patterns Chapter ........................................... 66
13.1. State Sharing Concepts ............................................... 66
13.2. HttpSession Versus HttpServletRequest ...................... 66
13.3. Base Code for HttpSession Patterns ............................ 67
13.4. Single Portlet Pattern ................................................... 68
13.5. Multiple Portlet Patterns ............................................... 69
14. Rendering Lifecycles Chapter .............................................. 77
14.1. WLP and JSF Lifecycles .............................................. 77
14.2. Invocation Order of WLP and JSF Lifecycle Methods... 77
14.3. Accessing WLP Context Objects from JSF Managed Beans 78
15. Portal Navigation Chapter .................................................... 80
15.1. Programmatically Constructing JSF Portlet URLs ........ 80
15.2. Changing the Active Portal Page.................................. 80
15.3. Redirects within a Portal............................................... 83
16. Ajax Enablement Chapter .................................................... 85
16.1. Ajax in JSF Portlets...................................................... 85
16.2. Partial Page Rendering Pattern.................................... 85
16.3. Stateless API Request Pattern ..................................... 86
16.4. Portlet Aware API Request Pattern .............................. 87
16.5. Controlling the WLP Ajax Framework........................... 91
17. Additional WLP Features Chapter........................................ 93
17.2. Portlet Container Features ........................................... 93
17.3. Portal Container Features ............................................ 98
18. Example: Implementing a Login Portlet Chapter .................. 99
18.1. Login Portlet Motivation................................................ 99
18.2. Login Portlet Design..................................................... 99
18.3. Login Portlet Implementation...................................... 101
Part 3: Integrating Third Party Libraries
19. Integration Overview Chapter............................................. 111
19.1. Types of Libraries....................................................... 111
19.2. Roadmap for MyFaces Trinidad and ADF Faces Rich Client 111
20. Using the Facelets View Technology Chapter.................... 113
20.1. Introduction to Facelets .............................................. 113
20.2. Configuring Facelets Support ..................................... 113
21. Using the Apache MyFaces Tomahawk Component Library Chapter 115
21.1. What is Apache MyFaces Tomahawk? ...................... 115
21.2. Support for Tomahawk in WLP................................... 115
21.3. Tomahawk Component List........................................ 116
21.4. Installing and Configuring Tomahawk......................... 119
21.5. Resolving the Duplicate ID Issue................................ 120
21.6. Referring to Resources .............................................. 120
21.7. forceId Attribute.......................................................... 124
21.8. File Upload................................................................. 125
22. Using the Apache Beehive Navigation Controller Chapter . 126
22.1. Apache Beehive Page Flow ....................................... 126
22.2. JSF and Page Flows .................................................. 126
22.3. Configuring the JSF Integration with Page Flows ....... 127
Appendices
23. Appendix 1: Consolidated List of Best Practices ................ 130
24. Appendix 2: Known Issues and Workarounds.................... 132
24.1. CR383659, CR383662 Inconsistent failures with JSF portlets 132
24.2. CR342124: IllegalStateException due to duplicate client-id 132
24.3. CR384916: IllegalStateException due to duplicate client-id when using certain components such as Tomahawk and Trinidad...... 133
24.4. CR361477 Problems with the integration of JSF portlets with Apache Beehive Page Flows.................................................................. 133
24.5. CR377945 JSF 1.2 suffers from a memory leak during iterative development .............................................................................. 134
25. Appendix 3: The JSFPortletHelper Class ........................... 135
26. Appendix 4: The CleanupPhaseListener Class .................. 147

Hi Peter!
First, I wish to thank you for the great work.
We followed your whitepaper and managed to deploy a JSF portlet on WLS.
But we are not able to register it (consume it) as remote portlet in Oracle Portal 10.1.4. The error log is as follows:
An error occurred while trying to refresh the provider. (WWC-43190)
An error occurred during the call to the WSRP Provider:
java.rmi.RemoteException: serialization error: serialization error:
unexpected null value for literal data; nested exception is:
serialization error: serialization error: unexpected null value for literal data
com.sun.xml.rpc.encoding.SerializationException: serialization error:
serialization error: unexpected null value for literal data
com.sun.xml.rpc.encoding.SerializationException: serialization error:
unexpected null value for literal data
Java stack trace from root exception:
unexpected null value for literal data
at
oracle.webdb.wsrp.RegistrationContext_LiteralSerializer.doSerialize(RegistrationContext_LiteralSerializer.java:107)
at
com.sun.xml.rpc.encoding.literal.LiteralObjectSerializerBase.internalSerialize(LiteralObjectSerializerBase.java:119)
at
com.sun.xml.rpc.encoding.literal.LiteralObjectSerializerBase.serialize(LiteralObjectSerializerBase.java:70)
at
oracle.webdb.wsrp.GetServiceDescription_LiteralSerializer.doSerialize(GetServiceDescription_LiteralSerializer.java:88)
at
com.sun.xml.rpc.encoding.literal.LiteralObjectSerializerBase.internalSerialize(LiteralObjectSerializerBase.java:119)
at
com.sun.xml.rpc.encoding.literal.LiteralObjectSerializerBase.serialize(LiteralObjectSerializerBase.java:70)
at
com.sun.xml.rpc.client.StreamingSender._writeRequest(StreamingSender.java:473)
at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:62)
at
oracle.webdb.wsrp.WSRP_v1_ServiceDescription_PortType_Stub.getServiceDescription(WSRP_v1_ServiceDescription_PortType_Stub.java:63)
at
oracle.webdb.wsrp.client.design.v1.OraWSRP_v1_ServiceDescription_PortType.getServiceDescription(Unknown
Source)Do you have any idea why this happens? Or you can provide some useful links to WLP -Oracle Portal federation?
Thank you and best regards,
PaKo

JSF actionListeners only work for first requestor?

Good morning! I'm working on a project where I've built a custom JSF panel that contains 3 buttons. Each button is bound to an action listener method in a form bean. One method takes the value from the text box on the form and adds it as a selectItem to one selectOne object, the second button adds the text box content to a second selectOne object and the third clears both selectOne object and restores them to their default state.
This all works well as long as you are the first person to press a button after a server re-start. For anyone else that requests this page after that, nothing happens (the page doesn't even seem to refresh, but I can't verify that). I know through the use of breakpoints and debugging that the action listener method is never entered.
I'm using Weblogic Workshop 9.1 for development (the server is the same version) and using the version of JSF/Beehive that comes with workshop. Any suggestions as to what might be happening to prevent anyone but the first user to fire the listeners would be greatly appreciated!
Thank you in advance,
Chris

There are a couple things you should do:
1. Implement a debugging phase listener. This is just a simple phase listener for all phases that just prints a debug line at each phase entry/exit.
2. Add the "messages" tag to show all messages.
Adding these two may help you discover that you are hitting a validation error.

JSF portlet: namingContainer - duplicate id error

Hi Experts,
I am developing a JSF portlets having only a click button. When I click the button, it throws duplicate id exception. If I don't use namingContainer tag, it runs well. Here is the JSP code and exception:
JSP:
<%@ page language="java" contentType="text/html;charset=UTF-8"%>
<%@ taglib uri="http://java.sun.com/jsf/html" prefix="h"%>
<%@ taglib uri="http://java.sun.com/jsf/core" prefix="f"%>
<%@ taglib uri="http://bea.com/faces/adapter/tags-naming" prefix="netuix"%>
<f:view>
     <netuix:namingContainer id="simpleJsfContainer">
          <h:outputText value="Simplest JSF Portlet" />
          <h:form>
               <h:commandButton id="postbackButton" value="Click here" />
          </h:form>
     </netuix:namingContainer>
</f:view>
Exception
opening /simplejsf/simpleJsf.faces.
The source of this error is:
java.lang.IllegalStateException: Client-id : simpleJsf_1 is duplicated in the faces tree. Component : simpleJsf_1, path: {Component-Path : [Class: javax.faces.component.UIViewRoot,ViewId: /simplejsf/simpleJsf.jsp][Class: com.bea.portlet.adapter.faces.component.naming.NamingContainerComponent,Id: simpleJsf_1]}
     at org.apache.myfaces.application.jsp.JspStateManagerImpl.checkForDuplicateIds(JspStateManagerImpl.java:350)
     at org.apache.myfaces.application.jsp.JspStateManagerImpl.checkForDuplicateIds(JspStateManagerImpl.java:365)
     at org.apache.myfaces.application.jsp.JspStateManagerImpl.saveSerializedView(JspStateManagerImpl.java:305)
     at org.apache.myfaces.taglib.core.ViewTag.doAfterBody(ViewTag.java:122)
     at jsp_servlet._simplejsf.__simplejsf._jsp__tag0(__simplejsf.java:133)
     at jsp_servlet._simplejsf.__simplejsf._jspService(__simplejsf.java:91)
     at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
     at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
     at org.apache.beehive.netui.pageflow.PageFlowPageFilter.continueChainNoWrapper(PageFlowPageFilter.java:455)
     at org.apache.beehive.netui.pageflow.PageFlowPageFilter.runPage(PageFlowPageFilter.java:432)
     at org.apache.beehive.netui.pageflow.PageFlowPageFilter.doFilter(PageFlowPageFilter.java:284)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
     at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:503)
     at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:432)
     at com.bea.portlet.adapter.faces.context.ExternalContextImpl.dispatch(ExternalContextImpl.java:110)
     at org.apache.myfaces.application.jsp.JspViewHandlerImpl.renderView(JspViewHandlerImpl.java:234)
     at com.bea.portlet.adapter.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:77)
     at org.apache.beehive.netui.pageflow.faces.internal.PageFlowViewHandler.renderView(PageFlowViewHandler.java:203)
     at org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:384)
     at com.bea.portlet.adapter.faces.FacesContentStubImpl.render(FacesContentStubImpl.java:354)
     at com.bea.netuix.servlets.controls.content.FacesContent.beginRender(FacesContent.java:420)
     at com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:485)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:518)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
     at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:220)
     at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:395)
     at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361)
     at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:352)
     at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:326)
     at com.bea.netuix.nf.UIControl.render(UIControl.java:582)
     at com.bea.netuix.servlets.controls.PresentationContext.render(PresentationContext.java:486)
     at com.bea.netuix.servlets.util.RenderToolkit.renderChild(RenderToolkit.java:146)
     at com.bea.netuix.servlets.jsp.taglib.skeleton.Child.doTag(Child.java:63)
     at jsp_servlet._framework._skeletons._bighorn.__flowlayout._jspService(__flowlayout.java:175)
     at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
     at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:505)
     at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:432)
     at com.bea.netuix.servlets.controls.application.laf.JspTools.renderJsp(JspTools.java:130)
     at com.bea.netuix.servlets.controls.application.laf.JspControlRenderer.beginRender(JspControlRenderer.java:72)
     at com.bea.netuix.servlets.controls.application.laf.PresentationControlRenderer.beginRender(PresentationControlRenderer.java:65)
     at com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:481)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:518)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
     at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:220)
     at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:395)
     at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361)
     at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:352)
     at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:326)
     at com.bea.netuix.nf.UIControl.render(UIControl.java:582)
     at com.bea.netuix.servlets.controls.PresentationContext.render(PresentationContext.java:486)
     at com.bea.netuix.servlets.util.RenderToolkit.renderChild(RenderToolkit.java:146)
     at com.bea.netuix.servlets.jsp.taglib.skeleton.Child.doTag(Child.java:63)
     at jsp_servlet._framework._skeletons._bighorn.__gridlayout._jspService(__gridlayout.java:219)
     at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
     at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:505)
     at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:432)
     at com.bea.netuix.servlets.controls.application.laf.JspTools.renderJsp(JspTools.java:130)
     at com.bea.netuix.servlets.controls.application.laf.JspControlRenderer.beginRender(JspControlRenderer.java:72)
     at com.bea.netuix.servlets.controls.application.laf.PresentationControlRenderer.beginRender(PresentationControlRenderer.java:65)
     at com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:481)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:518)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
     at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:220)
     at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:395)
     at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361)
     at com.bea.netuix.nf.Lifecycle.runOutbound(Lifecycle.java:208)
     at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:162)
     at com.bea.netuix.servlets.manager.UIServlet.runLifecycle(UIServlet.java:388)
     at com.bea.netuix.servlets.manager.UIServlet.doPost(UIServlet.java:258)
     at com.bea.netuix.servlets.manager.UIServlet.service(UIServlet.java:199)
     at com.bea.netuix.servlets.manager.SingleFileServlet.service(SingleFileServlet.java:251) at com.bea.netuix.servlets.manager.PortalServlet.service(PortalServlet.java:686) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292) at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42) at com.bea.portal.tools.servlet.http.HttpContextFilter.doFilter(HttpContextFilter.java:60) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42) at com.bea.p13n.servlets.PortalServletFilter.doFilter(PortalServletFilter.java:336) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3502) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(Unknown Source) at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2186) at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2092) at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1406) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Could you please tell me what's the problem?
Thanks
Tridib
Edited by: Tridib on 12-Feb-2010 08:48

Alright. I found it! I changed JSF implementation from MyFaces to Sun Reference implementation 1.1 and it worked! For details about how to set sun implementation as JSF implementation in portal project refer to section 2.2 in [White Paper|http://blogs.oracle.com/tridib_samanta/weblogic-portal-jsf-whitepaper.pdf] .
Edited by: Tridib on 16-Feb-2010 06:32

Removing NetUI Facets and Upgrading JSF

Even though 11g has promoted the use of JSF and talked of deprecating the NetUI, the facets and frameworks for 10gR3 are littered with NetUI dependencies.
Creating a Web Portal Project gives you the capabilities to use JSF 1.2, but doing this requires you to select JSTL 1.2 and Dynamic Web Modules 2.5, but deselect WebLogic Control Extensions, Beehive NetUI, Beehive Controls, Portal Customizations Framework, Portal Framework, Portal Visitor Tools, and WSRP Producer. Not sure why upgrading to the newer (obviously not the newest version of the API), requires removing all these dependent frameworks.
How will disabling all these project facets effect my Portal project? Are the specific things that I will not be able to take advantage of?
It just doesn't make sense to use a product like WebLogic Portal 10gR3 (released within this year) and then downgrade JSF to version 1.1 just so I can use NetUI...that sounds totally backward thinking.
Thanks...jay

The forthcoming 11g version of the WLP product will include better support for JSF 1.2 in portal web projects, and remove the hard dependency on Beehive Netui and Controls.
In WLP 10gR3 (10.3.0), you can use JSF 1.2 -- it just requires a bit of manual setup. Please see http://download.oracle.com/technology/products/weblogic/portal/weblogic-portal-jsf-whitepaper.pdf. There are instructions (Section 4.4) on how to setup your project in Workshop to utilize JSF 1.2 in a portal-enabled web project.
Greg

JSF Portlet w/o PageFlow?

I've run through a tutorial on JSF with PageFlow (Beehive) and I just don't see the value of it. Native JSF is what suits my project the best. It seems like the JSF Portlet is assuming you're going to be using PageFlows, because it puts the PageFlowApplicationFactory in the faces-config.xml. Its easy enough to comment out and have JSF stuff working 'natively', but I was wondering if PageFlows are mandatory for JSF Portlets, and if not, why there isn't an option to 'turn off PageFlow' support from the JSF Portlet wizard? Should I expect any side effects if I don't use PageFlows with the JSF Portlet option?

Alright. I found it! I changed JSF implementation from MyFaces to Sun Reference implementation 1.1 and it worked! For details about how to set sun implementation as JSF implementation in portal project refer to section 2.2 in [White Paper|http://blogs.oracle.com/tridib_samanta/weblogic-portal-jsf-whitepaper.pdf] .
Edited by: Tridib on 16-Feb-2010 06:32

WLP10.3.1 Any similar feature JSF portlets like refreshAction in PF Portlet

Is there is any similar feature in JSF portlets like refreshAction in PageFlow(beehive) Portlets?
Thanks in advance.
Edited by: mnp on Jul 1, 2010 7:29 AM

Does JDev support portlet development for non-OracleAS java containers?
Portlets developed in JDeveloper may be deployed to another application server that supports portlets.
Are the Web Center Suite / Portlet Development tools a plug-in for Jdeveloper?
The WebCenter extension for JDeveloper is pre-configured in JDeveloper.
Currently I use JDeveloper ADF BC / JSF and deploy to Tomcat; I'd like to include portlets in our web application.
Embedding Portlets in JSF pages -http://www.oracle.com/technology/products/jdev/viewlets/1013/jsfwithportlets_viewlet_swf.html?
Creating Portlets from JSF pages -
http://www.oracle.com/technology/products/jdev/viewlets/1013/portletize_jsf_pages_viewlet_swf.html?

Problem with JSF AJAX portlets

I am seeing the following issues with JSF portlets
1) When you AJAX enable the portlet, they will not work. There are some javascript errors on the component we are using. They work fine if we don't AJAX enable them
2) I had 2 portlets. 1 JSF and 1 pageflow portlet. If I click on a link in pageflow portlet and after the page gets refreshed, nothing will work in JSF potlet. Again javacript errors
If we had only 1 portlet on the page, JSF portlet works fine
Do you think the prototype javacript library used in the portal causing any issues?

I tried with <naming:namingContainer> immediatly after the f:view tag , but still getting same errors
I am psoting the generated html and javascript error
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html>
     <head>
<title>New Portal Desktop</title><meta name="bea-portal-meta-skeleton" content="/framework/skeletons/default"><meta name="bea-portal-meta-skin" content="/framework/skins/default"><meta name="bea-portal-meta-skin-images" content="/framework/skins/default/images"><link rel="stylesheet" type="text/css" href="/sampleWeb/framework/skins/default/css/body.css"><link type="text/css" href="/sampleWeb/framework/skins/default/css/button.css" rel="stylesheet"><link href="/sampleWeb/framework/skins/default/alert/css/window-alert.css" rel="stylesheet" type="text/css"><link href="/sampleWeb/framework/skins/default/css/window.css" rel="stylesheet" type="text/css"><link type="text/css" rel="stylesheet" href="/sampleWeb/framework/skins/default/plain/css/window-plain.css"><link type="text/css" rel="stylesheet" href="/sampleWeb/framework/skins/default/css/portlet.css"><link type="text/css" rel="stylesheet" href="/sampleWeb/framework/skins/default/css/book.css"><link type="text/css" rel="stylesheet" href="/sampleWeb/framework/skins/default/css/layout.css"><link href="/sampleWeb/framework/skins/default/css/form.css" rel="stylesheet" type="text/css"><script src="/sampleWeb/framework/skins/shared/js/console.js" type="text/javascript"></script><script src="/sampleWeb/framework/skins/shared/js/cookies.js" type="text/javascript"></script><script src="/sampleWeb/framework/skins/shared/js/state.js" type="text/javascript"></script><script src="/sampleWeb/framework/skins/default/js/util.js" type="text/javascript"></script><script type="text/javascript" src="/sampleWeb/framework/skins/default/js/skin.js"></script><script src="/sampleWeb/framework/skins/default/js/menu.js" type="text/javascript"></script><script src="/sampleWeb/framework/skins/default/js/delete.js" type="text/javascript"></script><script src="/sampleWeb/framework/skins/default/js/float.js" type="text/javascript"></script><script type="text/javascript" src="/sampleWeb/framework/skins/default/js/menufx.js"></script>
     </head>
<body
class="bea-portal-body"
onload="initSkin();"
><div class="bea-portal-body-content">
<div
class="bea-portal-body-header"
>
</div>
<div
class="bea-portal-book-primary"
>
<div class="bea-portal-ie-table-buffer-div">
<table border="0" cellpadding="0" cellspacing="0" width="100%">
<tr>
<td class="bea-portal-book-primary-menu-single-container" align="left" nowrap="nowrap">
<ul
class="bea-portal-book-primary-menu-single"
><li class="bea-portal-book-primary-menu-single-item">Page 1</li><li class="bea-portal-book-primary-menu-single-item">New Book</li><li class="bea-portal-book-primary-menu-single-item-active"><span>New Book</span></li></ul>
</td>
</tr>
</table>
</div>
<div
class="bea-portal-book-primary-content"
>
<div
class="bea-portal-book-invisible"
>
<div class="bea-portal-ie-table-buffer-div">
<table border="0" cellpadding="0" cellspacing="0" width="100%">
<tr>
<td class="bea-portal-book-menu-single-container" align="left" nowrap="nowrap">
<ul
class="bea-portal-book-menu-single"
><li class="bea-portal-book-menu-single-item-active"><span>New Page</span></li></ul>
</td>
</tr>
</table>
</div>
<div
class="bea-portal-book-content"
>
<div
class="bea-portal-book-page"
>
<table
class="bea-portal-layout-grid"
cellspacing="0"
>
<tr>
<td class="bea-portal-layout-placeholder-container"
width="30%"
>
<div
class="bea-portal-layout-placeholder"
>
<div
class="bea-portal-window"
width="100%"
>
<div
class="bea-portal-window-titlebar"
>
<div class="bea-portal-ie-table-buffer-div">
<table class="bea-portal-window-titlebar-container" cellspacing="0">
<tr>
<td class="bea-portal-window-titlebar-title" nowrap="nowrap">Untitled</td>
<td class="bea-portal-window-titlebar-buttons" nowrap="nowrap">
</td>
</tr>
</table>
</div>
</div>
<div
class="bea-portal-window-content"
>
<html>
<head>
</head>
<body>
     <p>Beehive NetUI-JavaServer Faces Page - /sampleWeb/sample1/index.faces</p>
<form id="portletInstance_6:_id1" method="post" action="http://localhost:7001/sampleWeb/sample.portal?_nfpb=true&_windowLabel=portletInstance_6&_nffvid=%2FsampleWeb%2Fsample1%2Findex.faces&_pageLabel=defaultDesktopLabel_page_2" enctype="application/x-www-form-urlencoded">
<a href="# onclick="document.forms['portletInstance_6:_id1'['portletInstance_6:_id1:_idcl'].value='portletInstance_6:_id1:_id2'; document.forms['portletInstance_6:_id1'].submit(); return false;">sample</a>
<input type="hidden" name="portletInstance_6:_id1" value="portletInstance_6:_id1" /></form>
</body>
</html>
</div>
</div>
</div>
</td>
<td class="bea-portal-layout-placeholder-container"
width="70%"
>
<div
class="bea-portal-layout-placeholder"
>
<div
class="bea-portal-window"
width="100%"
>
<div
class="bea-portal-window-titlebar"
>
<div class="bea-portal-ie-table-buffer-div">
<table class="bea-portal-window-titlebar-container" cellspacing="0">
<tr>
<td class="bea-portal-window-titlebar-title" nowrap="nowrap">Untitled</td>
<td class="bea-portal-window-titlebar-buttons" nowrap="nowrap">
</td>
</tr>
</table>
</div>
</div>
<div
class="bea-portal-window-content"
>
<html>
<head>
</head>
<body>
     <p>Beehive NetUI-JavaServer Faces Page - /sampleWeb/sample1/index.faces</p>
<form id="portletInstance_5:_id1" method="post" action="http://localhost:7001/sampleWeb/sample.portal?_nfpb=true&_windowLabel=portletInstance_5&_nffvid=%2FsampleWeb%2Fsample1%2Findex.faces&_pageLabel=defaultDesktopLabel_page_2" enctype="application/x-www-form-urlencoded">
<a href="#" onclick="document.forms['portletInstance_5:_id1']['portletInstance_5:_id1:_idcl'].value='portletInstance_5:_id1:_id2'; document.forms['portletInstance_5:_id1'].submit(); return false;">sample</a>
<input type="hidden" name="portletInstance_5:_id1" value="portletInstance_5:_id1" /><input type="hidden" name="portletInstance_5:_id1:_idcl" /></form>
</body>
</html>
</div>
</div>
</div>
</td>
</tr>
</table>
</div>
</div>
</div>
</div>
</div>
<div
class="bea-portal-body-footer"
>
</div>
</div></body>
</html>
Javascript error
Line: 292
Char: 1
Error: 'portletinstance_6_id1:_idcl' is null or not an object
Code: 0
URL: http://localhost:7001/sampleWeb/sample.portal?_nfpb=true&_windowLabel=
portletInstance_5&_nffvid=%2FsampleWeb%2Fsample1%2Findex.faces&_pageLabel=
defaultDesktopLabel_page_2

Faces / Beehive problem

Hi
I work with the weblogic 10.0, using beehive pageflows, myfaces 1.1 and ajax4jsf 1.0.
We use the beehive pageflow to store the data that all the faces screens will use. We use the @Jpf.PageFlowField in all the FacesBacking beans. With this configuration we dont have any problem and all the FacesBacking beans get the same pageflow data.
We updated the ajax4jsf with the richfaces 3.1 and after that we have this problem:
####<Jun 30, 2008 8:14:07 AM ACT> <Error> <org.apache.beehive.netui.pageflow.PageFlowManagedObject> <WSAR2S00084> <AdminServer> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1214831647687> <BEA-000000> <Could not set field myController on vccas.flows.adminRequest.popups.ServiceTypePopup; instance is of type Controller, field type is vccas.flows.adminRequest.AdminRequestController>
This problem apears when the faces backing bean try to get the pageflow from the context.
Does anyone have an idea of what is the problem?
I didnt modify anything only replace tha ajax4jsf jar with the richfaces 3.1 jars.

>
In the future, you should be posting JSF related questions at the JSF forum: [http://forums.sun.com/forum.jspa?forumID=427].
I have this main jsp:In the future, please post code in code tags. It will format the code and thus greatly improve readability. You can get the code tags by pressing the CODE button in the message editor toolbar. Copypaste your code in between those tags.
<title>Homework 1 - Distribuited systems</title>Homework?
<body BGCOLOR="#FDF5E6">Would rather use CSS here. Attribute names doesn't need to be uppercased either.
<center><h1><h:outputText value="Welcome !" /></h1></center>
<center>
<h:form>
<h:commandButton action="start" id="start" value="Jump" />
</h:form>
</center>The <center> tag is deprecated since HTML 4.01 in 1999(!!). Use CSS.
<navigation-rule>
<from-view-id>/LoginPage.jsp</from-view-id>
<navigation-case>
<from-outcome>start</from-outcome>
<to-view-id>/UserPage.jsp</to-view-id>
</navigation-case>
</navigation-rule>
If i press the Jump button i`m not redirected to the user page? Can anyone tell me the problem? ThanksEither the from-view-id, from-outcome or to-view-id is invalid. At least the from-outcome looks fine. Left behind the view-id's. Those must match the relative URL to the page as seen from the root of the web content. It is -as usual in Java- case sensitive. Doublecheck it all.
It might also be worth the effort to read the application server logs and placing a <h:messages/> tag in the page to get notified of any 'uncaught' error messages.

How to get ALL values as default for a drop down box in JSF

Hi,
I have a drop down box in JSF page which retrieves values from LOVCache.java. I have values like Company, Client, User, ALL in the drop down box.
By default blank value is selected for the drop down box. I want to make ALL(which retrieves data for all the values) as default value for the drop down box.
Could any body help me? Any help must be appreciated.
Thanks,
Aseet

Thanks Nikhil. But I am fetching the values from the LOVCache.java.
I am using <af:selectManyChoice>. Is there any way I can use LOVCache.java value for selecting default values instead of hard coding?
I mean to say can I write
unselectedLabel="#{LOVCache.entityTypeSelectionList.anyValue}"
where LOVCache.entityTypeSelectionList is used to populate the drop down box.
Regards,
Aseet

I am trying to use java file as Model layer and jsf as presentation layer

I am trying to use java file as Model layer and jsf as presentation layer and need some help
I successfully get the value of h:outputText from java file by doing simple binding operation but I am facing problems when I am trying to fill h:dataTable
I create java file
package oracle.model;
import java.sql.;*
import java.util.;*
*public class TableBean {*
Connection con ;
Statement ps;
ResultSet rs;
private List perInfoAll = new ArrayList();
*public List getperInfoAll() {*
perInfoAll.add(0,new perInfo("name","username","blablabla"));
return perInfoAll;
*public class perInfo {*
String uname;
String firstName;
String lastName;
*public perInfo(String firstName,String lastName,String uname) {*
this.uname = uname;
this.firstName = firstName;
this.lastName = lastName;
*public String getUname() {*
return uname;
*public String getFirstName() {*
return firstName;
*public String getLastName() {*
return lastName;
right click on the file and choose 'create data control'
then i wrote the jsf file:
*<%@ taglib uri="http://java.sun.com/jsf/html" prefix="h"%>*
*<%@ taglib uri="http://java.sun.com/jsf/core" prefix="f"%>*
*<f:view>*
*<h:dataTable id="dt1" value="#{bindings.perInfoAll}"*
var="item" bgcolor="#F1F1F1" border="10"
cellpadding="5" cellspacing="3" rows="4" width="50%"
dir="LTR" frame="hsides" rules="all"
*>*
*<f:facet name="header">*
*<h:outputText value="This is 'dataTable' demo" id="ot6"/>*
*</f:facet>*
*<h:column id="c2">*
*<f:facet name="header">*
*<h:outputText value="First Name" id="ot1"/>*
*</f:facet>*
*<h:outputText style="" value="#{item.firstName}"*
id="ot2"/>
*</h:column>*
*<h:column id="c4">*
*<f:facet name="header">*
*<h:outputText value="Last Name" id="ot9"/>*
*</f:facet>*
*<h:outputText value="#{item.lastName}" id="ot8"/>*
*</h:column>*
*<h:column id="c3">*
*<f:facet name="header">*
*<h:outputText value="Username" id="ot7"/>*
*</f:facet>*
*<h:outputText value="#{item.uname}" id="ot4"/>*
*</h:column>*
*<f:facet name="footer">*
*<h:outputText value="The End" id="ot3"/>*
*</f:facet>*
*</h:dataTable>*
*</center>*
*</af:document>*
*</f:view>*
but nothing is appear in my table
I know that there is something wrong in calling the binding object
I need help pls and where can i find some help to deal with another tag types
thanks

i dragged the "perInfoAll" from my "Data Controls" and choosed adf table (even I know that new table with adf tags well be generated and i want table with jsf tags)
and this code is generated
*<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"*
*"http://www.w3.org/TR/html4/loose.dtd">*
*<%@ page contentType="text/html;charset=UTF-8"%>*
*<%@ taglib uri="http://java.sun.com/jsf/core" prefix="f"%>*
*<%@ taglib uri="http://java.sun.com/jsf/html" prefix="h"%>*
*<%@ taglib uri="http://xmlns.oracle.com/adf/faces/rich" prefix="af"%>*
*<f:view>*
*<af:document id="d1">*
*<af:messages id="m1"/>*
*<af:form id="f1">*
*<af:table value="#{bindings.perInfoAll1.collectionModel}" var="row"*
*rows="#{bindings.perInfoAll1.rangeSize}"*
*emptyText="#{bindings.perInfoAll1.viewable ? 'No data to display.' : 'Access Denied.'}"*
*fetchSize="#{bindings.perInfoAll1.rangeSize}"*
*rowBandingInterval="0"*
*selectionListener="#{bindings.perInfoAll1.collectionModel.makeCurrent}"*
*rowSelection="multiple" id="t1">*
*<af:column sortProperty="uname" sortable="false"*
*headerText="#{bindings.perInfoAll1.hints.uname.label}"*
*id="c1">*
*<af:inputText value="#{row.bindings.uname.inputValue}"*
*label="#{bindings.perInfoAll1.hints.uname.label}"*
*required="#{bindings.perInfoAll1.hints.uname.mandatory}"*
*columns="#{bindings.perInfoAll1.hints.uname.displayWidth}"*
*maximumLength="#{bindings.perInfoAll1.hints.uname.precision}"*
*shortDesc="#{bindings.perInfoAll1.hints.uname.tooltip}"*
*id="it3">*
*<f:validator binding="#{row.bindings.uname.validator}"/>*
*</af:inputText>*
*</af:column>*
*<af:column sortProperty="firstName" sortable="false"*
*headerText="#{bindings.perInfoAll1.hints.firstName.label}"*
*id="c2">*
*<af:inputText value="#{row.bindings.firstName.inputValue}"*
*label="#{bindings.perInfoAll1.hints.firstName.label}"*
*required="#{bindings.perInfoAll1.hints.firstName.mandatory}"*
*columns="#{bindings.perInfoAll1.hints.firstName.displayWidth}"*
*maximumLength="#{bindings.perInfoAll1.hints.firstName.precision}"*
*shortDesc="#{bindings.perInfoAll1.hints.firstName.tooltip}"*
*id="it2">*
*<f:validator binding="#{row.bindings.firstName.validator}"/>*
*</af:inputText>*
*</af:column>*
*<af:column sortProperty="lastName" sortable="false"*
*headerText="#{bindings.perInfoAll1.hints.lastName.label}"*
*id="c3">*
*<af:inputText value="#{row.bindings.lastName.inputValue}"*
*label="#{bindings.perInfoAll1.hints.lastName.label}"*
*required="#{bindings.perInfoAll1.hints.lastName.mandatory}"*
*columns="#{bindings.perInfoAll1.hints.lastName.displayWidth}"*
*maximumLength="#{bindings.perInfoAll1.hints.lastName.precision}"*
*shortDesc="#{bindings.perInfoAll1.hints.lastName.tooltip}"*
*id="it1">*
*<f:validator binding="#{row.bindings.lastName.validator}"/>*
*</af:inputText>*
*</af:column>*
*</af:table>*
*</af:form>*
*</af:document>*
*</f:view>*
but when run it i see the following errors
*Class oracle.adf.model.adapter.bean.BeanDataControl can not access a member of class nl.amis.hrm.EmpManager with modifiers "private"*
*Object EmpManager of type DataControl is not found.*
*java.lang.NullPointerException*
*Class oracle.adf.model.adapter.bean.BeanDataControl can not access a member of class nl.amis.hrm.EmpManager with modifiers "private"*
*Object EmpManager of type DataControl is not found.*
*java.lang.NullPointerException*
:(

Beehive & JSF

Similar Messages

Maybe you are looking for