nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Deploying Alfresco Portlets to another portal

nashukla

Hi,

I wanted to deploy the Alfresco portlets to another portal instance which has support for JSR-168 comliant portlets. I need to have the access to the WSDL url for the Alfresco portlets. Is there a WSDL url that I can access for the Alfresco portlets ?

Thank you for your help.

Regards,
– Nachi

Note: If this is not the right forum for this question, please point me to the correct one. Sorry for the inconvenience caused.

Find more posts tagged with

Comments

davidc

We don't have WSDL definitions for our portlets. Which portal do you want to deploy to?

mfeldstein

I don't know about Nachi, but I'd personally be interested in the feasibility of deploying to uPortal.

nashukla

Hi,

I would be interested to deploy this into Oracle Portal.

In Oracle Portal it requires a WSDL url which contains an abstract definition of the provider. I think this is for compliance with WSRP & JSR-168.

Though I understand that there in no WSDL url, Is there any information available with regard to how to make these portlets available in another portal. I looked around on the wiki and saw that there is a section for integration into Liferay but there was no content.

It would be very helpful if someone could point out how would you go about making these portlets available in any other portal. I could learn from that and try to fir that into my requirement.

Thank you for your replies.

Regards,
– Nachi

kevinr

Hello,

Each JSR-168 portal environment is different - although they all support the same basic JSR-168 javax interfaces, they mostly use slightly different deployment mechanisms.

We were able to deploy our web-client to the JBoss JSR168 portal by working on the deployment xml files found here:

web-client\source\web\WEB-INF

the jboss specific files are:
jboss-portlet.xml, jboss-web.xml and jboss-service.xml
which at the moment are all either blank or the minimum required as we don't need any jboss specifics.

the "standard" JSR-168 portlet deployment files are:
portlet.xml and portlet-instances.xml
these files will probably be very similar for your JSR-168 portal. You should edit them as appropriate - look at your portal and find out what needs to be done to deploy a portlet WAR.

In theory it should be possible to deploy the app into any JSR-168 portal - however we have not tried many others except for LifeRay… It should be noted that we rely on the JSF Portal bridge code in MyFaces. If you have problems it may be because your portal already has a version of MyFaces as part of it's standard libraries - you may need to either remove it or change the version of the jar to match the latest.

Hope this helps,

Kevin