Hi Mario,
Let me try to make a guess here.
The last sentence in the Pluto advantage article states the following:
IMPORTANT: To ensure your custom portlets will run in other portals don’t use non-portable JSF control library or any MWS specific API.
Maybe you are using non-portable JSF controls or a part of an MWS specific API without knowing?
A couple of suggestions:
-
The best way to ensure you’re not using non-portable controls in your project is to select only ‘MwS Portable Controls’ JSF library during the project creation wizard. This will filter Palette view to show controls and beans from this library only. 95% of all Mws controls/beans are portable.
-
‘MwS specific API’ is anything packaged within Portal/lib/wm-caf-server.jar. It includes the following package spaces:
com.webMethods.portal.*
com.webMethods.rtl.*
com.webMethods.jms.db.*
com.webMethods.common.search.*
If you’re using any classes from these packages then you’re using MwS specific API.
-
Standard, i.e. out of the box or custom task portlets created from templates, do use non-portable controls and some MwS specific API’s. Plus they leverage proprietary portlet wiring and embedding as well as in-proc API to work with task engine. All of these make it impossible to re-use these portlets ‘as is’ in other containers.
Hope this helps,
Thomas
#webMethods-BPMS#MWS-CAF-Task-Engine#webMethods