You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pluto-dev@portals.apache.org by "Luta, Raphael (VUN)" <Ra...@groupvu.Com> on 2003/12/16 10:18:00 UTC
RE : portals.apache.org
De : David Sean Taylor [mailto:david@bluesunrise.com]
>
> I would like to propose creating a new top level project (TLP) at
> Apache: portals.apache.org
> Before doing so, I've started this email thread to introduce the
> concept.
> Could you all please provide some feedback and opinions so we can see
> if everyone stands behind this new TLP.
>
I'm +1 on the idea in general by I have some questions on specific goals of
such a project. See below.
>
> Goals of portals.apache.org:
>
> 1. To promote the use of portlet applications. We view portlets as an
> important technology in the growing portal and web application
> environments. We intend to build freely available portlet
> applications, portal servers, and portlet containers in order to
> promote the use of this technology.
I think that for this goal to have a global meaning you need to define
what you call portlet and portlet applications.
Integrating a definition similar to the the one used by JSR168 like
"portlets are pluggable user-interface components used by portals to provide
a presentation and interaction layer to Information Systems" would help
better define the intent to non-portal aware people
> 2. To encourage developers from all Apache portal projects to work
> together and share common code
Big question here, what about PHP ? It's part of Apache and is also a very
popular choice for building portals. WSRP could definitely be used as a
bridge
between the Java and PHP world which would be a very good thing IMO.
Also consider Perl, etc...
> 3. To develop Portlet Applications and Portlet Application frameworks
> at portals.apache.org and grow the portal community here. Portlet
> Applications will be managed as sub-projects.
> Portal Applications will enable a higher level of application
> development while cleanly separating the development of
> portals such as
> Jetspeed from applications code.
> 4. To provide a community for portal-related Java and XML
> standards and
> reference implementations under the ASF license at portals.apache.org
>
I think that limiting the scope of portals.apache.org to Java and XML is too
restrictive. Although I admit that the communities mostly fall along
technology
lines right now, Portals address application integration issues within a
company
and should do their best to easily integrate many technologies. I think that
a common ground for all portal-related issues for any technology currently
represented in the ASF would be a very good move.
--
Raphaël Luta - raphael@apache.org
Jakarta Jetspeed - Enterprise Portal in Java
http://jakarta.apache.org/jetspeed/
**********************************************
Vivendi Universal Disclaimer - HTTP://www.vivendiUniversal.com:
The information transmitted is intended only for the person or entity
to which it is addressed and may contain confidential and/or privileged
material of Vivendi Universal which is for the exclusive use of the
individual designated above as the recipient. Any review, retransmission,
dissemination or other use of, or taking of any action in reliance upon,
this information by persons or entities other than the intended recipient
is prohibited. If you received this in error, please contact immediately
the sender by returning e-mail and delete the material from any computer.
If you are not the specified recipient, you are hereby notified that all
disclosure, reproduction, distribution or action taken on the basis of
this message is prohibited.
Re: RE : portals.apache.org
Posted by Barnhill William <ba...@bah.com>.
I agree that it should be possible to integrate PHP and Perl as portlet
content sources. I don't see why they would need to be in the portal
itself. Have PHP and Perl bindings to your portal's API, and have PHP
authors write their apps (or integration glue code) as a set of
cooperating portlets. This also allows developers of xxx, the as yet
undiscovered latest and greatest language, to support their languages
use in the portal by contributing language bindings for the API.
Luta, Raphael (VUN) wrote:
>Big question here, what about PHP ? It's part of Apache and is also a very
>
>popular choice for building portals. WSRP could definitely be used as a
>bridge
>between the Java and PHP world which would be a very good thing IMO.
>Also consider Perl, etc...
>
>
>
>I think that limiting the scope of portals.apache.org to Java and XML is too
>restrictive. Although I admit that the communities mostly fall along
>technology
>lines right now, Portals address application integration issues within a
>company
>and should do their best to easily integrate many technologies. I think that
>
>a common ground for all portal-related issues for any technology currently
>represented in the ASF would be a very good move.
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
Re: RE : portals.apache.org
Posted by Santiago Gala <sg...@hisitech.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
El martes, 16 dici, 2003, a las 10:18 Europe/Madrid, Luta, Raphael
(VUN) escribió:
>
> De : David Sean Taylor [mailto:david@bluesunrise.com]
>>
>> I would like to propose creating a new top level project (TLP) at
>> Apache: portals.apache.org
>> Before doing so, I've started this email thread to introduce the
>> concept.
>> Could you all please provide some feedback and opinions so we can see
>> if everyone stands behind this new TLP.
>>
>
A global +1, first of all.
> I'm +1 on the idea in general by I have some questions on specific
> goals of
> such a project. See below.
>
>>
>> Goals of portals.apache.org:
>>
>> 1. To promote the use of portlet applications. We view portlets as an
>> important technology in the growing portal and web application
>> environments. We intend to build freely available portlet
>> applications, portal servers, and portlet containers in order to
>> promote the use of this technology.
>
> I think that for this goal to have a global meaning you need to define
> what you call portlet and portlet applications.
> Integrating a definition similar to the the one used by JSR168 like
> "portlets are pluggable user-interface components used by portals to
> provide
> a presentation and interaction layer to Information Systems" would help
> better define the intent to non-portal aware people
>
>> 2. To encourage developers from all Apache portal projects to work
>> together and share common code
>
> Big question here, what about PHP ? It's part of Apache and is also a
> very
> popular choice for building portals. WSRP could definitely be used as a
> bridge
> between the Java and PHP world which would be a very good thing IMO.
> Also consider Perl, etc...
>
You stole my idea!!! :-P
Now seriously, during the last ApacheCON I explored the possibility and
spoke to mod_perl and mod_php and other perl and php oriented people
about having a project to implement "remote portlets" which speak WSRP
and are written in perl, php and/or python. Some people understood the
idea and was willing to explore the possibilities.
>> 3. To develop Portlet Applications and Portlet Application frameworks
>> at portals.apache.org and grow the portal community here. Portlet
>> Applications will be managed as sub-projects.
>> Portal Applications will enable a higher level of application
>> development while cleanly separating the development of
>> portals such as
>> Jetspeed from applications code.
>> 4. To provide a community for portal-related Java and XML
>> standards and
>> reference implementations under the ASF license at portals.apache.org
>>
>
> I think that limiting the scope of portals.apache.org to Java and XML
> is too
> restrictive. Although I admit that the communities mostly fall along
> technology
> lines right now, Portals address application integration issues within
> a
> company
> and should do their best to easily integrate many technologies. I
> think that
>
> a common ground for all portal-related issues for any technology
> currently
> represented in the ASF would be a very good move.
>
I agree with Raphael that the charter should not be java-specific.
Regards,
Santiago
(intermittently, mostly unconnected during most of this week, on a
business trip)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (Darwin)
iD8DBQE/4GcMZAeG2a2/nhoRAuj7AKC0/6NVm4IaO5pPMsebJkTLqqqqtQCeOOK6
mWmLAbqlaHCdzaSADA06XQ8=
=HN+N
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
Re: RE : portals.apache.org
Posted by David Sean Taylor <da...@bluesunrise.com>.
On Tuesday, December 16, 2003, at 01:18 AM, Luta, Raphael (VUN) wrote:
>
> De : David Sean Taylor [mailto:david@bluesunrise.com]
>>
>> I would like to propose creating a new top level project (TLP) at
>> Apache: portals.apache.org
>> Before doing so, I've started this email thread to introduce the
>> concept.
>> Could you all please provide some feedback and opinions so we can see
>> if everyone stands behind this new TLP.
>>
>
> I'm +1 on the idea in general by I have some questions on specific
> goals of
> such a project. See below.
>
>>
>> Goals of portals.apache.org:
>>
>> 1. To promote the use of portlet applications. We view portlets as an
>> important technology in the growing portal and web application
>> environments. We intend to build freely available portlet
>> applications, portal servers, and portlet containers in order to
>> promote the use of this technology.
>
> I think that for this goal to have a global meaning you need to define
> what you call portlet and portlet applications.
> Integrating a definition similar to the the one used by JSR168 like
> "portlets are pluggable user-interface components used by portals to
> provide
> a presentation and interaction layer to Information Systems" would help
> better define the intent to non-portal aware people
>
Yes. Definitions will be included in the upcoming project charter.
>> 2. To encourage developers from all Apache portal projects to work
>> together and share common code
>
> Big question here, what about PHP ? It's part of Apache and is also a
> very
> popular choice for building portals. WSRP could definitely be used as a
> bridge
> between the Java and PHP world which would be a very good thing IMO.
> Also consider Perl, etc...
>
Or Python or Ruby or Groovy portlets. Absolutely.
Thanks for pointing that out.
>> 3. To develop Portlet Applications and Portlet Application frameworks
>> at portals.apache.org and grow the portal community here. Portlet
>> Applications will be managed as sub-projects.
>> Portal Applications will enable a higher level of application
>> development while cleanly separating the development of
>> portals such as
>> Jetspeed from applications code.
>> 4. To provide a community for portal-related Java and XML
>> standards and
>> reference implementations under the ASF license at portals.apache.org
>>
>
> I think that limiting the scope of portals.apache.org to Java and XML
> is too
> restrictive. Although I admit that the communities mostly fall along
> technology
> lines right now, Portals address application integration issues within
> a
> company
> and should do their best to easily integrate many technologies. I
> think that
>
> a common ground for all portal-related issues for any technology
> currently
> represented in the ASF would be a very good move.
>
Excellent points Raphael. I will add your input to the project charter
and send it back to the list soon
--
David Sean Taylor
Bluesunrise Software
david@bluesunrise.com
[office] +01 707 773-4646
[mobile] +01 707 529 9194
Re: RE : portals.apache.org
Posted by David Sean Taylor <da...@bluesunrise.com>.
On Tuesday, December 16, 2003, at 01:18 AM, Luta, Raphael (VUN) wrote:
>
> De : David Sean Taylor [mailto:david@bluesunrise.com]
>>
>> I would like to propose creating a new top level project (TLP) at
>> Apache: portals.apache.org
>> Before doing so, I've started this email thread to introduce the
>> concept.
>> Could you all please provide some feedback and opinions so we can see
>> if everyone stands behind this new TLP.
>>
>
> I'm +1 on the idea in general by I have some questions on specific
> goals of
> such a project. See below.
>
>>
>> Goals of portals.apache.org:
>>
>> 1. To promote the use of portlet applications. We view portlets as an
>> important technology in the growing portal and web application
>> environments. We intend to build freely available portlet
>> applications, portal servers, and portlet containers in order to
>> promote the use of this technology.
>
> I think that for this goal to have a global meaning you need to define
> what you call portlet and portlet applications.
> Integrating a definition similar to the the one used by JSR168 like
> "portlets are pluggable user-interface components used by portals to
> provide
> a presentation and interaction layer to Information Systems" would help
> better define the intent to non-portal aware people
>
Yes. Definitions will be included in the upcoming project charter.
>> 2. To encourage developers from all Apache portal projects to work
>> together and share common code
>
> Big question here, what about PHP ? It's part of Apache and is also a
> very
> popular choice for building portals. WSRP could definitely be used as a
> bridge
> between the Java and PHP world which would be a very good thing IMO.
> Also consider Perl, etc...
>
Or Python or Ruby or Groovy portlets. Absolutely.
Thanks for pointing that out.
>> 3. To develop Portlet Applications and Portlet Application frameworks
>> at portals.apache.org and grow the portal community here. Portlet
>> Applications will be managed as sub-projects.
>> Portal Applications will enable a higher level of application
>> development while cleanly separating the development of
>> portals such as
>> Jetspeed from applications code.
>> 4. To provide a community for portal-related Java and XML
>> standards and
>> reference implementations under the ASF license at portals.apache.org
>>
>
> I think that limiting the scope of portals.apache.org to Java and XML
> is too
> restrictive. Although I admit that the communities mostly fall along
> technology
> lines right now, Portals address application integration issues within
> a
> company
> and should do their best to easily integrate many technologies. I
> think that
>
> a common ground for all portal-related issues for any technology
> currently
> represented in the ASF would be a very good move.
>
Excellent points Raphael. I will add your input to the project charter
and send it back to the list soon
--
David Sean Taylor
Bluesunrise Software
david@bluesunrise.com
[office] +01 707 773-4646
[mobile] +01 707 529 9194
Re: RE : portals.apache.org
Posted by David Sean Taylor <da...@bluesunrise.com>.
On Tuesday, December 16, 2003, at 01:18 AM, Luta, Raphael (VUN) wrote:
>
> De : David Sean Taylor [mailto:david@bluesunrise.com]
>>
>> I would like to propose creating a new top level project (TLP) at
>> Apache: portals.apache.org
>> Before doing so, I've started this email thread to introduce the
>> concept.
>> Could you all please provide some feedback and opinions so we can see
>> if everyone stands behind this new TLP.
>>
>
> I'm +1 on the idea in general by I have some questions on specific
> goals of
> such a project. See below.
>
>>
>> Goals of portals.apache.org:
>>
>> 1. To promote the use of portlet applications. We view portlets as an
>> important technology in the growing portal and web application
>> environments. We intend to build freely available portlet
>> applications, portal servers, and portlet containers in order to
>> promote the use of this technology.
>
> I think that for this goal to have a global meaning you need to define
> what you call portlet and portlet applications.
> Integrating a definition similar to the the one used by JSR168 like
> "portlets are pluggable user-interface components used by portals to
> provide
> a presentation and interaction layer to Information Systems" would help
> better define the intent to non-portal aware people
>
Yes. Definitions will be included in the upcoming project charter.
>> 2. To encourage developers from all Apache portal projects to work
>> together and share common code
>
> Big question here, what about PHP ? It's part of Apache and is also a
> very
> popular choice for building portals. WSRP could definitely be used as a
> bridge
> between the Java and PHP world which would be a very good thing IMO.
> Also consider Perl, etc...
>
Or Python or Ruby or Groovy portlets. Absolutely.
Thanks for pointing that out.
>> 3. To develop Portlet Applications and Portlet Application frameworks
>> at portals.apache.org and grow the portal community here. Portlet
>> Applications will be managed as sub-projects.
>> Portal Applications will enable a higher level of application
>> development while cleanly separating the development of
>> portals such as
>> Jetspeed from applications code.
>> 4. To provide a community for portal-related Java and XML
>> standards and
>> reference implementations under the ASF license at portals.apache.org
>>
>
> I think that limiting the scope of portals.apache.org to Java and XML
> is too
> restrictive. Although I admit that the communities mostly fall along
> technology
> lines right now, Portals address application integration issues within
> a
> company
> and should do their best to easily integrate many technologies. I
> think that
>
> a common ground for all portal-related issues for any technology
> currently
> represented in the ASF would be a very good move.
>
Excellent points Raphael. I will add your input to the project charter
and send it back to the list soon
--
David Sean Taylor
Bluesunrise Software
david@bluesunrise.com
[office] +01 707 773-4646
[mobile] +01 707 529 9194
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org