亚洲av成人无遮挡网站在线观看,少妇性bbb搡bbb爽爽爽,亚洲av日韩精品久久久久久,兔费看少妇性l交大片免费,无码少妇一区二区三区

  免費(fèi)注冊(cè) 查看新帖 |

Chinaunix

  平臺(tái) 論壇 博客 文庫(kù)
最近訪問(wèn)板塊 發(fā)新帖
查看: 1579 | 回復(fù): 0
打印 上一主題 下一主題

JSF in a portlet has never been this easy! [復(fù)制鏈接]

論壇徽章:
0
跳轉(zhuǎn)到指定樓層
1 [收藏(0)] [報(bào)告]
發(fā)表于 2008-11-13 21:23 |只看該作者 |倒序?yàn)g覽

               
JSF in a portlet has never been this easy!
               

            
            
               
                  Created:
                                                   Mon 07 Jul 2008
                  
                      Posted by: wesleyhales under Java
                                       
                  
                     
                                            No Comments
                     
                     
                 
               
               
                                             
We just released JBoss Portlet Bridge Beta3 along with some good supporting documentation and  example projects.
See the documentation for full details
.
For those that want to jump right in, you can run the following archetype and have it deployed on JBoss AS + Portal in minutes:
mvn archetype:generate -DarchetypeGroupId=org.jboss.portletbridge.archetypes -DarchetypeArtifactId=1.2-basic -DarchetypeVersion=1.0.0.B3 -DgroupId=org.whatever.project -DartifactId=myprojectname -DarchetypeRepository=http://repository.jboss.org/maven2/ -Dversion=1.0.0.B3
mvn install cargo:start -Premote-portal -Dpc20
mvn cargo:deploy -Premote-portal -Dpc20
Visit
http://localhost:8080/simple-portal/demo/jsr-301.jsp
The majority of the code written for this release is internal to the
portlet bridge project (refactoring, 301 spec updates and enhancements,
bug fixes...). The next release (Beta 4 - early Sept) will be huge for
the portlet bridge for the following reasons:
  • The EG is currently discussing a lot of significant
    clarifications and improvements. For example, working with the JSF 2.0
    EG to allow certain needs and working on Portlet 2.0 areas of the spec.
  • There is currently a lot of discussion about navigation
    between portlet modes. Once this is nailed down in the spec, we will
    implement it.
  • The Portlet 1.0 version should be getting close to public review.
Other
than the spec related reasons for release schedule, we must work in
unison with the latest Seam and RichFaces relases, make sure that we
squash any bugs concerning the 3 integration points, handle
features/improvements/refactorings, and try to test and give feedback
to the 301 EG. And, of course we can't forget about JBoss Portal 2.7+!
There are soo many cool things going on right now within the JBoss
Portal project, I would like to tell you about all of them but then
this post wouldn't be about JBPB anymore. Just stay tuned to this
blog...
With that said, here are a few tips for JSF portlet developers that
concern this release:
  • NamespacingIn situations where you need to
    use the id of an element in your JSF/xhtml markup, you would normally
    see something like 'form1:myBtn' in the rendered markup. But now with
    the bridge namespacing you will see something similar to: jbpns_2fdefault_2fNews_2fStories_2fStoryTemplateWindow12snpbj:_viewRoot:form1:myBtn
    To overcome this, you can use the following expression in your Facelets page to prepend the namespace to your javascript code:
    document.getElementById('#{facesContext.externalContext.response.namespace}the_rest_of_JSF_ID
    since this uses the portletResponse, once you try to view this page on
    the servlet application side, you will get an exception. To avoid this,
    you need to check for the type of response in your backing bean and
    assign a new "safe" namespace variable for the UI.
  • Excluding Attributes from the Bridge Request ScopeWhen
    your application uses request attributes on a per request basis and you
    do not want that particular attribute to be managed in the extended
    bridge request scope, you must use the following configuration in your
    faces-config.xml. Below you will see that any attribute namespaced as
    foo.bar or any attribute beginning with foo.baz(wildcard) will be
    excluded from the bridge request scope and only be used per that
    application's request.
         
             
                 foo.bar
                 foo.baz.*
             
         
       
For more information on this release or to find out more about the project, visit the
project page
.
                          
               
               
               

本文來(lái)自ChinaUnix博客,如果查看原文請(qǐng)點(diǎn):http://blog.chinaunix.net/u/21642/showart_1412979.html
您需要登錄后才可以回帖 登錄 | 注冊(cè)

本版積分規(guī)則 發(fā)表回復(fù)

  

北京盛拓優(yōu)訊信息技術(shù)有限公司. 版權(quán)所有 京ICP備16024965號(hào)-6 北京市公安局海淀分局網(wǎng)監(jiān)中心備案編號(hào):11010802020122 niuxiaotong@pcpop.com 17352615567
未成年舉報(bào)專(zhuān)區(qū)
中國(guó)互聯(lián)網(wǎng)協(xié)會(huì)會(huì)員  聯(lián)系我們:huangweiwei@itpub.net
感謝所有關(guān)心和支持過(guò)ChinaUnix的朋友們 轉(zhuǎn)載本站內(nèi)容請(qǐng)注明原作者名及出處

清除 Cookies - ChinaUnix - Archiver - WAP - TOP