[gatein-issues] [JBoss JIRA] (GTNPORTAL-1968) Remote portlet only works for the default portal context but doens't work with extension.

[Chris Laprun (Resolved) (JIRA)]

     [ https://issues.jboss.org/browse/GTNPORTAL-1968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Laprun resolved GTNPORTAL-1968.
-------------------------------------

    Fix Version/s: 3.2.0-M02
       Resolution: Done


I think this is fixed with the latest version of GateIn. If you refresh the selfv2 producer in the default portal WSRP admin interface, you should be able to see the selfv2 remote portlets when you click on Application Registry > Portlet > REMOTE in sample-portal admin for example.
                
> Remote portlet only works for the default portal context but doens't work with extension.
> -----------------------------------------------------------------------------------------
>
>                 Key: GTNPORTAL-1968
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-1968
>             Project: GateIn Portal
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: WSRP integration
>            Reporter: Gary Hu
>            Assignee: Chris Laprun
>             Fix For: 3.2.0-M02
>
>
> If I create a WSRP consumer via the WSRP configuration portlet, the WSRP portlets don't show under the "REMOTE" tab or "wsrp" application type when adding portlet to categories if Site Publisher is deployed.
> The same issue doesn't occur if the Site Publisher is not deployed.
> The following steps could reproduce the issue.
> 1) login ecmdemo as "john"
> 2) create a WSRP consumer via the WSRP configuration portlet. I'm using the NetUnity test public WSDL http://www.netunitysoftware.com/wsrp2interop/wsrpproducer.asmx?WSDL. If you see errors "faultCode=OTHER_ERROR: Inconsistent NS in port bindings" using the url above you can try to change it to
> http://www.netunitysoftware.com/wsrp2interop/wsrpproducer.asmx?Operation=WSDL&WsrpVersion=All
> you are likely to see a different error "Refresh failed (probably because the registration information was not valid). ". Then you change the url back to http://www.netunitysoftware.com/wsrp2interop/wsrpproducer.asmx?WSDL (click the Refresh and Save a couple of times if it doesn't work) you should be able to successfully register the WSRP producer.
> 3) go to Adminstration->Application Registry->Portlet->REMOTE, the WSRP portlets are not showing there.
> If you click "Categories", and under "CATEGORIES", you select any category, for example "Web", can click "+" to add a portlet. And then select "wsrp" as the Application Type and click "Add" button, it shows empty.
> If I go through the same steps by logging in "portal" as root, you can see the WSRP portlets are showing up.
> The further research shows that this is a limitation in the current EPP 5 product.
> This limitation is caused by hard-codes in EPP-5.1.x source code in file component/wsrp/src/main/java/org/gatein/portal/wsrp/WSRPServiceIntegration.java:
> ...
>  public WSRPServiceIntegration(ExoContainerContext context, InitParams params, ConfigurationManager configurationManager,
>                                  ExoKernelIntegration pc, NodeHierarchyCreator nhc) throws Exception
>    {
>       // IMPORTANT: even though PC ExoKernelIntegration and NodeHierarchyCreator is not used anywhere in the code, it's still needed for pico
>       // to properly make sure that this service is started after the PC one. Yes, Pico is crap. :/
>       // todo: we currently only allow the service to go through initialization if we are running in the default portal
>       // as this service is not meant to work with extensions yet...
>       String consumersConfigLocation;
>       if ("portal".equals(context.getName()))
>       {
>          if (params != null)
>          {
>             producerConfigLocation = params.getValueParam(PRODUCER_CONFIG_LOCATION).getValue();
>             consumersConfigLocation = params.getValueParam(CONSUMERS_CONFIG_LOCATION).getValue();
>          }
>          else
>          {
>             throw new IllegalArgumentException("Improperly configured service: missing values for "
>                + PRODUCER_CONFIG_LOCATION + "and " + CONSUMERS_CONFIG_LOCATION);
>          }
> ...
> Can you add a new feature that makes the remote portlet also work with the extension?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira