JBoss Portal Developer's Blog. Portlet Community. JSR168 support with WSRP- good or bad? I think it makes perfect sense to build applications in portal if portal is your main platform.
I don't see why any application should be ruled out based on it's 'size'. you can't deploy large applications in to a portal (if you're talking JSR-168) -- portal admins aren't going to like deploying an app that needs a lot of memory when they might have a 100+ portlet apps loaded on a decent sized portal server deployment. I guest you are talking about 'putting it al in one war file'. Creating an application that consumes a large amount of memory is bad in any way.
Not only within a portal. That app will only run in a portal in this case. I seem to miss the point of sacrificing. So in general, if you app leans to heavy on the heap, fix the application. Imho, once you picked the portal as your platform, run all you have on it. Adds WSRP Support to JBoss Portal. JBOSS: Web Services for Remote Portlets (WSRP) The Web Services for Remote Portlets specification defines a web service interface for accessing and interacting with interactive presentation-oriented web services.
It has been produced through the efforts of the Web Services for Remote Portlets (WSRP) OASIS Technical Committee. It is based on the requirements gathered and on the concrete proposals made to the committee. Scenarios that motivate WSRP functionality include: Content hosts, such as portal servers, providing Portlets as presentation-oriented web services that can be used by aggregation engines.Aggregating frameworks, including portal servers, consuming presentation-oriented web services offered by content providers and integrating them into the framework.
More information on WSRP can be found on the official website for WSRP. 9.2. JBoss Portal provides a base level support of the WSRP 1.0 standard and offers both consumer and producer services. Build deploy Note. JBoss Portal: Portlet Primer. The tutorials contained in this chapter are targetted toward portlet developers.
Although they are a good starting and reference point, we do heavily recommend that portlet developers read and understand the Portlet Specification (JSR-168) . We also recommend, using our JBoss Portal User Forums for user-to-user help, when needed. 5.2.1. Deploying your first portlet This section will introduce the reader to deploying his first portlet in JBoss Portal. Publishing JSR 168 Portlets as Remote Portlets With WSRP.
Oracle Technology Network > Java Software Downloads View All Downloads Top Downloads New Downloads What's New Java in the Cloud: Rapidly develop and deploy Java business applications in the cloud.
Essential Links Developer Spotlight Java EE—the Most Lightweight Enterprise Framework? Blogs Technologies Contact Us About Oracle Cloud Events Top Actions. Guidelines for Writing JSR-168 Portlets. Java.net: Web Services for Remote Portlets. JBoss Portal v2.4 docs: Chapter 9. Web Services for Remote Portl. Frequently Asked Questions about the JBoss4.2 Release. WSRP 2.0 Specification. [Web Services for Remote Portlets Specification v2.0] [Public Review Draft], [7 June 2006] Artifact Identifier: wsrp-2.0-spec-pr-01 Artifact Type: Specification Technical Committee: OASIS Web Services for Remote Portlets TC Chair: Rich Thompson, IBM Corporation <richt2@us.ibm.com> Editor: Contributors: Subbu Allamaraju, BEA Systems <subbu@bea.com> Michael Freedman, Oracle Corporation <Michael.Freedman@oracle.com> Richard Jacob, IBM Corporation <richard.jacob@de.ibm.com> Andre Kramer, Citrix Systems <andre.kramer@eu.citrix.com> OASIS Conceptual Topic Model Area: Web Services Related Work: This specification replaces or supercedes: [specifications replaced by this standard - OASIS as well as other standards organizations] This specification is related to: [specifications related to this standard - OASIS as well as other standards organizations] Abstract: Integration of remote content and application logic into an End-User presentation has been a task requiring significant custom programming effort.
Using JBoss WSRP behind a firewall. Using JBoss Behind a Firewall. Using Port Forwarding with JBoss.