maven portlet deployment

[ChadDavis]

I'm using pluto 1.0.1.

I'm just trying to learn portlets.  What exactly does the maven
portlet deployment do?  I'm talking about the one in the source code
distribution, deploy directory.  I'm using it to deploy my portlet
applications, as per the pluto site docs, and it works, but I want to
know what it does?

[Antony Stubbs]

Yes I would also like to know what it does, and why it is necessary to use - should we not simple be able to deploy simple wars that are portal compatible? can't pluto detect their existence?

I have found this, but it doesn't really answer my question - from the AssembleMojo javadoc:
 * The AssembleMojo is responsible for assembling a web application for deployment
 * into the Pluto portlet container.  Assembly, in this context, is the process of
 * updating a web application's WEB-INF/web.xml with Pluto specific parameters for
 * deployment in Pluto.  
 * <p>
 * This Mojo is able to operate on individual descriptors by specifying
 * <code>portletXml</code>, <code>webXml</code>, and <code>webXmlDestination</code>.
 * If your project uses standard Maven 2 directory layouts, the defaults will
 * provide proper values.
 * <p/>
 * Example Maven 2 <code>pom.xml</code> usage:

chadmichael wrote:

I'm using pluto 1.0.1.

I'm just trying to learn portlets.  What exactly does the maven
portlet deployment do?  I'm talking about the one in the source code
distribution, deploy directory.  I'm using it to deploy my portlet
applications, as per the pluto site docs, and it works, but I want to
know what it does?

[Antony Stubbs]

Hmm, after examining what it generates, it seems wrap your portlet in a pluto servlet...


Yes I would also like to know what it does, and why it is necessary to use - should we not simple be able to deploy simple wars that are portal compatible? can't pluto detect their existence?

I have found this, but it doesn't really answer my question - from the AssembleMojo javadoc:
 * The AssembleMojo is responsible for assembling a web application for deployment
 * into the Pluto portlet container.  Assembly, in this context, is the process of
 * updating a web application's WEB-INF/web.xml with Pluto specific parameters for
 * deployment in Pluto.  
 * <p>
 * This Mojo is able to operate on individual descriptors by specifying
 * <code>portletXml</code>, <code>webXml</code>, and <code>webXmlDestination</code>.
 * If your project uses standard Maven 2 directory layouts, the defaults will
 * provide proper values.
 * <p/>
 * Example Maven 2 <code>pom.xml</code> usage:

chadmichael wrote:

I'm using pluto 1.0.1.

I'm just trying to learn portlets.  What exactly does the maven
portlet deployment do?  I'm talking about the one in the source code
distribution, deploy directory.  I'm using it to deploy my portlet
applications, as per the pluto site docs, and it works, but I want to
know what it does?

[Eric Dalquist]

No, pluto cannot detect the presence of the portlets. It needs the wrapper servlet to do the following:
-Know the portlet webapp exists
-Determine the location of the portlet.xml file and parse it along with the web.xml
-Have a location to dispatch requests to that portlet to, if there was no servlet how could a portal in another webapp target the portlet?

All portals I am aware of do some similar sort of web.xml modification when deploying portlet webapps to their container.

-Eric


Antony Stubbs wrote:

Hmm, after examining what it generates, it seems wrap your portlet in a pluto
servlet...


Antony Stubbs wrote:
  

Yes I would also like to know what it does, and why it is necessary to use
- should we not simple be able to deploy simple wars that are portal
compatible? can't pluto detect their existence?

I have found this, but it doesn't really answer my question - from the
AssembleMojo javadoc:
 * The AssembleMojo is responsible for assembling a web application for
deployment
 * into the Pluto portlet container.  Assembly, in this context, is the
process of
 * updating a web application's WEB-INF/web.xml with Pluto specific
parameters for 
 * deployment in Pluto.   
 * <p>
 * This Mojo is able to operate on individual descriptors by specifying 
 * <code>portletXml</code>, <code>webXml</code>, and
<code>webXmlDestination</code>.
 * If your project uses standard Maven 2 directory layouts, the defaults
will
 * provide proper values.
 * <p/>
 * Example Maven 2 <code>pom.xml</code> usage:


chadmichael wrote:
    

I'm using pluto 1.0.1.

I'm just trying to learn portlets.  What exactly does the maven
portlet deployment do?  I'm talking about the one in the source code
distribution, deploy directory.  I'm using it to deploy my portlet
applications, as per the pluto site docs, and it works, but I want to
know what it does?


      

-----
___________________________

http://stubbisms.wordpress.com http://stubbisms.wordpress.com 
  

[Antony Stubbs]

Cheers! Thanks for the explanation.

I wonder why there's no standard way of doing this in the spec?

Eric Dalquist wrote:

No, pluto cannot detect the presence of the portlets. It needs the
wrapper servlet to do the following:
-Know the portlet webapp exists
-Determine the location of the portlet.xml file and parse it along with
the web.xml
-Have a location to dispatch requests to that portlet to, if there was
no servlet how could a portal in another webapp target the portlet?

All portals I am aware of do some similar sort of web.xml modification
when deploying portlet webapps to their container.

-Eric


Antony Stubbs wrote:
> Hmm, after examining what it generates, it seems wrap your portlet in a pluto
> servlet...
>
>
> Antony Stubbs wrote:
>  
>> Yes I would also like to know what it does, and why it is necessary to use
>> - should we not simple be able to deploy simple wars that are portal
>> compatible? can't pluto detect their existence?
>>
>> I have found this, but it doesn't really answer my question - from the
>> AssembleMojo javadoc:
>>  * The AssembleMojo is responsible for assembling a web application for
>> deployment
>>  * into the Pluto portlet container.  Assembly, in this context, is the
>> process of
>>  * updating a web application's WEB-INF/web.xml with Pluto specific
>> parameters for
>>  * deployment in Pluto.  
>>  * <p>
>>  * This Mojo is able to operate on individual descriptors by specifying
>>  * <code>portletXml</code>, <code>webXml</code>, and
>> <code>webXmlDestination</code>.
>>  * If your project uses standard Maven 2 directory layouts, the defaults
>> will
>>  * provide proper values.
>>  * <p/>
>>  * Example Maven 2 <code>pom.xml</code> usage:
>>
>>
>> chadmichael wrote:
>>    
>>> I'm using pluto 1.0.1.
>>>
>>> I'm just trying to learn portlets.  What exactly does the maven
>>> portlet deployment do?  I'm talking about the one in the source code
>>> distribution, deploy directory.  I'm using it to deploy my portlet
>>> applications, as per the pluto site docs, and it works, but I want to
>>> know what it does?
>>>
>>>
>>>      
>>    
>
>
> -----
> ___________________________
>
> http://stubbisms.wordpress.com http://stubbisms.wordpress.com 
>  

 

[Eric Dalquist]

That is a good question, I think they wanted to leave it up to the individual portal vendors but it can cause some confusion. The best policy it do develop with a 'clean' web.xml and only add the portal specific bits just before deploying (with a tool such as the Pluto Maven Plugin)

-Eric

Antony Stubbs wrote:

Cheers! Thanks for the explanation. 

I wonder why there's no standard way of doing this in the spec?


Eric Dalquist wrote:
  

No, pluto cannot detect the presence of the portlets. It needs the 
wrapper servlet to do the following:
-Know the portlet webapp exists
-Determine the location of the portlet.xml file and parse it along with 
the web.xml
-Have a location to dispatch requests to that portlet to, if there was 
no servlet how could a portal in another webapp target the portlet?

All portals I am aware of do some similar sort of web.xml modification 
when deploying portlet webapps to their container.

-Eric


Antony Stubbs wrote:
    

Hmm, after examining what it generates, it seems wrap your portlet in a
pluto
servlet...


Antony Stubbs wrote:
  
      

Yes I would also like to know what it does, and why it is necessary to
use
- should we not simple be able to deploy simple wars that are portal
compatible? can't pluto detect their existence?

I have found this, but it doesn't really answer my question - from the
AssembleMojo javadoc:
 * The AssembleMojo is responsible for assembling a web application for
deployment
 * into the Pluto portlet container.  Assembly, in this context, is the
process of
 * updating a web application's WEB-INF/web.xml with Pluto specific
parameters for 
 * deployment in Pluto.   
 * <p>
 * This Mojo is able to operate on individual descriptors by specifying 
 * <code>portletXml</code>, <code>webXml</code>, and
<code>webXmlDestination</code>.
 * If your project uses standard Maven 2 directory layouts, the defaults
will
 * provide proper values.
 * <p/>
 * Example Maven 2 <code>pom.xml</code> usage:


chadmichael wrote:
    
        

I'm using pluto 1.0.1.

I'm just trying to learn portlets.  What exactly does the maven
portlet deployment do?  I'm talking about the one in the source code
distribution, deploy directory.  I'm using it to deploy my portlet
applications, as per the pluto site docs, and it works, but I want to
know what it does?


      
          

-----
___________________________

http://stubbisms.wordpress.com http://stubbisms.wordpress.com 
  
      

-----
___________________________

http://stubbisms.wordpress.com http://stubbisms.wordpress.com 
  

[djencks]

On Oct 13, 2008, at 12:19 PM, Eric Dalquist wrote:

That is a good question, I think they wanted to leave it up to the individual portal vendors but it can cause some confusion. The best policy it do develop with a 'clean' web.xml and only add the portal specific bits just before deploying (with a tool such as the Pluto Maven Plugin)

I thought that there was no assumption that a portlet container would be an extended servlet container.  If the portlet container is implemented to just deal with the portlets on its own then you wouldn't need any kind of wrapping/web.xml modification.  Traditionally there hasn't been any support for deployment in javaee specs with the exception of jsr88 which mostly seems to be ignored AFAICT.  I do think having a jsr88 way to deploy a portlet app would be nice but I doubt it will happen any time soon.

thanks

david jencks

-Eric

Antony Stubbs wrote:

Cheers! Thanks for the explanation. 

I wonder why there's no standard way of doing this in the spec?


Eric Dalquist wrote:
  

No, pluto cannot detect the presence of the portlets. It needs the 
wrapper servlet to do the following:
-Know the portlet webapp exists
-Determine the location of the portlet.xml file and parse it along with 
the web.xml
-Have a location to dispatch requests to that portlet to, if there was 
no servlet how could a portal in another webapp target the portlet?

All portals I am aware of do some similar sort of web.xml modification 
when deploying portlet webapps to their container.

-Eric


Antony Stubbs wrote:
    

Hmm, after examining what it generates, it seems wrap your portlet in a
pluto
servlet...


Antony Stubbs wrote:
  
      

Yes I would also like to know what it does, and why it is necessary to
use
- should we not simple be able to deploy simple wars that are portal
compatible? can't pluto detect their existence?

I have found this, but it doesn't really answer my question - from the
AssembleMojo javadoc:
 * The AssembleMojo is responsible for assembling a web application for
deployment
 * into the Pluto portlet container.  Assembly, in this context, is the
process of
 * updating a web application's WEB-INF/web.xml with Pluto specific
parameters for 
 * deployment in Pluto.   
 * <p>
 * This Mojo is able to operate on individual descriptors by specifying 
 * <code>portletXml</code>, <code>webXml</code>, and
<code>webXmlDestination</code>.
 * If your project uses standard Maven 2 directory layouts, the defaults
will
 * provide proper values.
 * <p/>
 * Example Maven 2 <code>pom.xml</code> usage:


chadmichael wrote:
    
        

I'm using pluto 1.0.1.

I'm just trying to learn portlets.  What exactly does the maven
portlet deployment do?  I'm talking about the one in the source code
distribution, deploy directory.  I'm using it to deploy my portlet
applications, as per the pluto site docs, and it works, but I want to
know what it does?


      
          

-----
___________________________

http://stubbisms.wordpress.com http://stubbisms.wordpress.com 
  
      

-----
___________________________

http://stubbisms.wordpress.com http://stubbisms.wordpress.com