Portlet in separate war?

[David Hay，修改在16 年前。]

What are the disadvantages of bundling/deploying our portlets in a separate war file, rather than in the Liferay ext?

cheers,

David

[Jerry Niu，修改在16 年前。]

One advantage is the deployment of a war vs an EXT.

With a war, you just hot deploy it. With an EXT, you'll have to shut down the server upon the deploy.

[David Hay，修改在16 年前。]

Hi,

Thx. Can I point Liferay to a class in my separate web app to do autologin?

eg auto.login.hooks=my.package.in.my.webapp.myloginclass?

cheers,

David

[Jerry Niu，修改在16 年前。]

The recommendation is to use EXT for what you described. There are hacks around this, but I do not recommend them.

[David Hay，修改在16 年前。]

Hi Jerry,

Thx. Would you mind explaining the hacks - we might be forced to use them.

Also, how does Liferay manage portlets that are in different wars - handling sessions etc.?

many thanks,

David

[Jerry Niu，修改在16 年前。]

You'll have to use regular web programming work arounds.

[David Hay，修改在16 年前。]

That's actually what I was trying to discover ;)

Would you mind pointing me in the right direction? crossContext=true?

cheers,

David

[Raju Uppalapati，修改在16 年前。]

Advantages of Portlet in separate WAR:
1. Easy to package, maintain and upgrade.
2. Complete classloader isolation from other component Jars that might have version conflict.
3. Updating Portlets in a separate WAR file on a live system does not impact the rest of the portlets.

Disadvantages:
1. In a separate WAR file, all the Jars/classes are loaded in a separate Classloader. Due to this if a lot of classes/Jars are common to other portlets are loaded into memory again. So this solution might use more memory than combining all portlets into the same webapp.

[Krzysztof Makowski，修改在14 年前。]

Thanks for your input Raju!

Now I see more clearly pros and cons of WAR deploying.

But I still wonder is it possible to define web services in WAR portlet in the similar way as it could be done with service builder in the EXT environment?

Thanks in advance for the reply.