You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-user@portals.apache.org by Randy Watler <wa...@wispertel.net> on 2005/08/24 09:30:17 UTC
Integrating Graffito in Jetspeed-2 as PageManager for PSML
Graffito Dev Team,
For those that do not recognize me, I am a committer on the J2 portal team.
Although I have been threatening to do this for some time, I am finally
getting started on the integration of Graffito into J2 as a PageManager
component. The intent is to store the PSML that currently resides in the
file system in Graffito as XML documents. We will also want to leverage
many of Graffito's features in the J2 implementation, including security
and modification notification/timestamps.
There are new patches to the J2 svn HEAD version related to Connection
management, (see JS2-326), that should allow us to update the J2
deployment past the M3 support currently in place.
My personal goal is to commit this optional component into J2 for M4.
Of course, many thanks for developing, managing, and promoting Graffito.
Randy Watler
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: Integrating Graffito in Jetspeed-2 as PageManager for PSML
Posted by Santiago Gala <sg...@apache.org>.
El jue, 25-08-2005 a las 09:54 +0200, Raphaël Luta escribió:
> I actually discussed this issue with Noel Bergman (VP Incubator) at ApacheCon.
> >From his point of view, having a "release" of Graffito packaged with J2 M4 is
> fine as long as it helps build the community around Graffito and help
> the J2 and Graffito teams work together.
>
> So no issue there :)
>
Agreed. It would be fine if we take a snapshot build tagged with the
subversion revision number for J2-M4, specially since IP issues are
clean in Graffito. The process is tougher for projects coming from
donations where the paperwork is not yet done.
> Having a standalone Graffito release would still require to go through the
> usual Incubator release process.
>
This is not a tough requirement, BTW. Just some more voting stuff...
> Christophe Lombart wrote:
> > Sorry I don't know - Raphael ? I'm going to check on the Incubating site.
> >
> > Christophe
> >
> > 2005/8/24, Randy Watler <wa...@wispertel.net>:
> >
> >>Christophe/Raphael,
> >>
> >>There is some concern on the J2 dev team about the incubator status of
> >>Graffito as far as inclusion into a M4 J2 release. I am just opening up
> >>the topic here in hopes that either of you can assure the J2 team that
> >>we can release J2 with a component in incubator status and/or help us
> >>determine what we need to do ASF wise to make it happen.
> >>
> >>Thanks in advance for any help on this and future development questions,
> >>
> >>Randy
> >>
> >>Christophe Lombart wrote:
> >>
> >>
> >>>Hi Randy,
> >>>
> >>>Managing PSML into Graffito will be great. Count on me each time you
> >>>need more info on Graffito. Let me know when you start this work, we
> >>>can exchange some info in order to work faster.
> >>>
> >>>Christophe
> >>>
> >>>
> >>>2005/8/24, Randy Watler <wa...@wispertel.net>:
> >>>
> >>>
> >>>
> >>>>Graffito Dev Team,
> >>>>
> >>>>For those that do not recognize me, I am a committer on the J2 portal team.
> >>>>
> >>>>Although I have been threatening to do this for some time, I am finally
> >>>>getting started on the integration of Graffito into J2 as a PageManager
> >>>>component. The intent is to store the PSML that currently resides in the
> >>>>file system in Graffito as XML documents. We will also want to leverage
> >>>>many of Graffito's features in the J2 implementation, including security
> >>>>and modification notification/timestamps.
> >>>>
> >>>>There are new patches to the J2 svn HEAD version related to Connection
> >>>>management, (see JS2-326), that should allow us to update the J2
> >>>>deployment past the M3 support currently in place.
> >>>>
> >>>>My personal goal is to commit this optional component into J2 for M4.
> >>>>
> >>>>Of course, many thanks for developing, managing, and promoting Graffito.
> >>>>
> >>>>Randy Watler
> >>>>
>
--
VP and Chair, Apache Portals (http://portals.apache.org)
Apache Software Foundation
Re: Integrating Graffito in Jetspeed-2 as PageManager for PSML
Posted by Raphaël Luta <ra...@apache.org>.
I actually discussed this issue with Noel Bergman (VP Incubator) at ApacheCon.
From his point of view, having a "release" of Graffito packaged with J2 M4 is
fine as long as it helps build the community around Graffito and help
the J2 and Graffito teams work together.
So no issue there :)
Having a standalone Graffito release would still require to go through the
usual Incubator release process.
Christophe Lombart wrote:
> Sorry I don't know - Raphael ? I'm going to check on the Incubating site.
>
> Christophe
>
> 2005/8/24, Randy Watler <wa...@wispertel.net>:
>
>>Christophe/Raphael,
>>
>>There is some concern on the J2 dev team about the incubator status of
>>Graffito as far as inclusion into a M4 J2 release. I am just opening up
>>the topic here in hopes that either of you can assure the J2 team that
>>we can release J2 with a component in incubator status and/or help us
>>determine what we need to do ASF wise to make it happen.
>>
>>Thanks in advance for any help on this and future development questions,
>>
>>Randy
>>
>>Christophe Lombart wrote:
>>
>>
>>>Hi Randy,
>>>
>>>Managing PSML into Graffito will be great. Count on me each time you
>>>need more info on Graffito. Let me know when you start this work, we
>>>can exchange some info in order to work faster.
>>>
>>>Christophe
>>>
>>>
>>>2005/8/24, Randy Watler <wa...@wispertel.net>:
>>>
>>>
>>>
>>>>Graffito Dev Team,
>>>>
>>>>For those that do not recognize me, I am a committer on the J2 portal team.
>>>>
>>>>Although I have been threatening to do this for some time, I am finally
>>>>getting started on the integration of Graffito into J2 as a PageManager
>>>>component. The intent is to store the PSML that currently resides in the
>>>>file system in Graffito as XML documents. We will also want to leverage
>>>>many of Graffito's features in the J2 implementation, including security
>>>>and modification notification/timestamps.
>>>>
>>>>There are new patches to the J2 svn HEAD version related to Connection
>>>>management, (see JS2-326), that should allow us to update the J2
>>>>deployment past the M3 support currently in place.
>>>>
>>>>My personal goal is to commit this optional component into J2 for M4.
>>>>
>>>>Of course, many thanks for developing, managing, and promoting Graffito.
>>>>
>>>>Randy Watler
>>>>
--
Raphaël Luta - raphael@apache.org
Apache Portals - Enterprise Portal in Java
http://portals.apache.org/
Re: Integrating Graffito in Jetspeed-2 as PageManager for PSML
Posted by Christophe Lombart <ch...@gmail.com>.
Sorry I don't know - Raphael ? I'm going to check on the Incubating site.
Christophe
2005/8/24, Randy Watler <wa...@wispertel.net>:
> Christophe/Raphael,
>
> There is some concern on the J2 dev team about the incubator status of
> Graffito as far as inclusion into a M4 J2 release. I am just opening up
> the topic here in hopes that either of you can assure the J2 team that
> we can release J2 with a component in incubator status and/or help us
> determine what we need to do ASF wise to make it happen.
>
> Thanks in advance for any help on this and future development questions,
>
> Randy
>
> Christophe Lombart wrote:
>
> >Hi Randy,
> >
> >Managing PSML into Graffito will be great. Count on me each time you
> >need more info on Graffito. Let me know when you start this work, we
> >can exchange some info in order to work faster.
> >
> >Christophe
> >
> >
> >2005/8/24, Randy Watler <wa...@wispertel.net>:
> >
> >
> >>Graffito Dev Team,
> >>
> >>For those that do not recognize me, I am a committer on the J2 portal team.
> >>
> >>Although I have been threatening to do this for some time, I am finally
> >>getting started on the integration of Graffito into J2 as a PageManager
> >>component. The intent is to store the PSML that currently resides in the
> >>file system in Graffito as XML documents. We will also want to leverage
> >>many of Graffito's features in the J2 implementation, including security
> >>and modification notification/timestamps.
> >>
> >>There are new patches to the J2 svn HEAD version related to Connection
> >>management, (see JS2-326), that should allow us to update the J2
> >>deployment past the M3 support currently in place.
> >>
> >>My personal goal is to commit this optional component into J2 for M4.
> >>
> >>Of course, many thanks for developing, managing, and promoting Graffito.
> >>
> >>Randy Watler
> >>
> >>
> >>
> >>
> >>---------------------------------------------------------------------
> >>To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> >>For additional commands, e-mail: jetspeed-user-help@portals.apache.org
> >>
> >>
> >>
> >>
> >
> >
> >
> >
>
>
>
Re: Integrating Graffito in Jetspeed-2 as PageManager for PSML
Posted by Randy Watler <wa...@wispertel.net>.
Christophe/Raphael,
There is some concern on the J2 dev team about the incubator status of
Graffito as far as inclusion into a M4 J2 release. I am just opening up
the topic here in hopes that either of you can assure the J2 team that
we can release J2 with a component in incubator status and/or help us
determine what we need to do ASF wise to make it happen.
Thanks in advance for any help on this and future development questions,
Randy
Christophe Lombart wrote:
>Hi Randy,
>
>Managing PSML into Graffito will be great. Count on me each time you
>need more info on Graffito. Let me know when you start this work, we
>can exchange some info in order to work faster.
>
>Christophe
>
>
>2005/8/24, Randy Watler <wa...@wispertel.net>:
>
>
>>Graffito Dev Team,
>>
>>For those that do not recognize me, I am a committer on the J2 portal team.
>>
>>Although I have been threatening to do this for some time, I am finally
>>getting started on the integration of Graffito into J2 as a PageManager
>>component. The intent is to store the PSML that currently resides in the
>>file system in Graffito as XML documents. We will also want to leverage
>>many of Graffito's features in the J2 implementation, including security
>>and modification notification/timestamps.
>>
>>There are new patches to the J2 svn HEAD version related to Connection
>>management, (see JS2-326), that should allow us to update the J2
>>deployment past the M3 support currently in place.
>>
>>My personal goal is to commit this optional component into J2 for M4.
>>
>>Of course, many thanks for developing, managing, and promoting Graffito.
>>
>>Randy Watler
>>
>>
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
>>For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>>
>>
>>
>>
>
>
>
>
Re: Integrating Graffito in Jetspeed-2 as PageManager for PSML
Posted by Christophe Lombart <ch...@gmail.com>.
Hi Randy,
Managing PSML into Graffito will be great. Count on me each time you
need more info on Graffito. Let me know when you start this work, we
can exchange some info in order to work faster.
Christophe
2005/8/24, Randy Watler <wa...@wispertel.net>:
> Graffito Dev Team,
>
> For those that do not recognize me, I am a committer on the J2 portal team.
>
> Although I have been threatening to do this for some time, I am finally
> getting started on the integration of Graffito into J2 as a PageManager
> component. The intent is to store the PSML that currently resides in the
> file system in Graffito as XML documents. We will also want to leverage
> many of Graffito's features in the J2 implementation, including security
> and modification notification/timestamps.
>
> There are new patches to the J2 svn HEAD version related to Connection
> management, (see JS2-326), that should allow us to update the J2
> deployment past the M3 support currently in place.
>
> My personal goal is to commit this optional component into J2 for M4.
>
> Of course, many thanks for developing, managing, and promoting Graffito.
>
> Randy Watler
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>
>
Re: Integrating Graffito in Jetspeed-2 as PageManager for PSML
Posted by Christophe Lombart <ch...@gmail.com>.
Hi Randy,
Managing PSML into Graffito will be great. Count on me each time you
need more info on Graffito. Let me know when you start this work, we
can exchange some info in order to work faster.
Christophe
2005/8/24, Randy Watler <wa...@wispertel.net>:
> Graffito Dev Team,
>
> For those that do not recognize me, I am a committer on the J2 portal team.
>
> Although I have been threatening to do this for some time, I am finally
> getting started on the integration of Graffito into J2 as a PageManager
> component. The intent is to store the PSML that currently resides in the
> file system in Graffito as XML documents. We will also want to leverage
> many of Graffito's features in the J2 implementation, including security
> and modification notification/timestamps.
>
> There are new patches to the J2 svn HEAD version related to Connection
> management, (see JS2-326), that should allow us to update the J2
> deployment past the M3 support currently in place.
>
> My personal goal is to commit this optional component into J2 for M4.
>
> Of course, many thanks for developing, managing, and promoting Graffito.
>
> Randy Watler
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: Integrating Graffito in Jetspeed-2 as PageManager for PSML
Posted by Randy Watler <wa...@wispertel.net>.
All/Michael,
Thanks for the feedback!
Have created a JIRA issue for this:
http://issues.apache.org/jira/browse/JS2-350.
I copied this message there and a brief response.
Please comment further there if you can so that I can keep things together.
Randy
Dr. Michael Lipp wrote:
>Hello Randy,
>
>I admit that I know little about Graffito; I just looked at the Web site
>and got a first impression. I'd just like to state one concern (and
>maybe this turns out to be no issue at all). "Storing PSML in Graffito"
>and the management portlets mentioned on the web page arise in my mind
>the picture of a managed environment that may turn out to be "closed" to
>batch setup.
>
>I'm using Jetspeed2 as a framework for an application, i.e. I bundle it
>with several portlets, EJBs etc. to get a ready to run EAR. The
>possibility to change the portal at runtime is nice, but of minor
>importance. For this kind of usage, it is very important that I can
>build a runnable Jetspeed configuration automatically from my sources.
>Currently, it is no problem to maintain the PSML files and copy them in
>the proper directory before bundling Jetspeed. Things would be much more
>difficult if e.g. the PSML would be stored in a database. Of course,
>storing it in a database has advantages for changing the portal at
>run-time....
>
>So if configuration should no longer be possible my maintaining the
>pages "manually" in an editor and copying them in the right place, then
>there should at least be support for some kind of "setup directory".
>This directory would be scanned on startup and the data integrated in
>the Graffito database. I could put my page sources there, bundle, and my
>pages would be available after application startup.
>
>Sorry for the noise if everybody else knows that this is no problem at
>all. And as you said that your component should be optional, leaving it
>out of my configuration may be a way, too. It is just that I know that
>many people think of a portal as something that is configured over time
>by an administrator and saved by making database backups, whereas I need
>the possibility to create a valid portal configuration from sources;
>hence my concern.
>
>Regards,
>
> Michael
>
>Randy Watler wrote:
>
>
>>Graffito Dev Team,
>>
>>For those that do not recognize me, I am a committer on the J2 portal team.
>>
>>Although I have been threatening to do this for some time, I am finally
>>getting started on the integration of Graffito into J2 as a PageManager
>>component. The intent is to store the PSML that currently resides in the
>>file system in Graffito as XML documents. We will also want to leverage
>>many of Graffito's features in the J2 implementation, including security
>>and modification notification/timestamps.
>>
>>There are new patches to the J2 svn HEAD version related to Connection
>>management, (see JS2-326), that should allow us to update the J2
>>deployment past the M3 support currently in place.
>>
>>My personal goal is to commit this optional component into J2 for M4.
>>
>>Of course, many thanks for developing, managing, and promoting Graffito.
>>
>>Randy Watler
>>
>>
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
>>For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>>
>>
>>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
>For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Jetspeed Jboss Class Loading config
Posted by Travis Ward <tr...@yahoo.com>.
I was able to deploy Jetspeed1.6 with fusion on Jboss
following the recommendations from
http://issues.apache.org/jira/browse/JS2-210. My
question is there any way to get Jetspeed to work
without setting the follwing property in the
$JBOSS/server/default/deploy/jbossweb-tomcat50.sar/META-INF/jboss-service.xml
<atttribute
name="Java2ClassLoadingCompliance">false</attribute>
Setting this causes problems with multiple deployments
containing the same jars - different versions... and
jetspeed uses some older jars such as axis-1.1.jar.
I tried to use the jboss-web.xml to configure the
class loading specifically for jetspeed with no
success
<class-loading java2ClassLoadingCompliance="false">
<loader-repository>
dot.com:loader=unique-archive-name
<loader-repository-config>
java2ParentDelegation=false
</loader-repository-config>
</loader-repository>
</class-loading>
Thanks,
Travis
____________________________________________________
Start your day with Yahoo! - make it your home page
http://www.yahoo.com/r/hs
____________________________________________________
Start your day with Yahoo! - make it your home page
http://www.yahoo.com/r/hs
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: Integrating Graffito in Jetspeed-2 as PageManager for PSML
Posted by "Dr. Michael Lipp" <Mi...@danet.de>.
Hello Randy,
I admit that I know little about Graffito; I just looked at the Web site
and got a first impression. I'd just like to state one concern (and
maybe this turns out to be no issue at all). "Storing PSML in Graffito"
and the management portlets mentioned on the web page arise in my mind
the picture of a managed environment that may turn out to be "closed" to
batch setup.
I'm using Jetspeed2 as a framework for an application, i.e. I bundle it
with several portlets, EJBs etc. to get a ready to run EAR. The
possibility to change the portal at runtime is nice, but of minor
importance. For this kind of usage, it is very important that I can
build a runnable Jetspeed configuration automatically from my sources.
Currently, it is no problem to maintain the PSML files and copy them in
the proper directory before bundling Jetspeed. Things would be much more
difficult if e.g. the PSML would be stored in a database. Of course,
storing it in a database has advantages for changing the portal at
run-time....
So if configuration should no longer be possible my maintaining the
pages "manually" in an editor and copying them in the right place, then
there should at least be support for some kind of "setup directory".
This directory would be scanned on startup and the data integrated in
the Graffito database. I could put my page sources there, bundle, and my
pages would be available after application startup.
Sorry for the noise if everybody else knows that this is no problem at
all. And as you said that your component should be optional, leaving it
out of my configuration may be a way, too. It is just that I know that
many people think of a portal as something that is configured over time
by an administrator and saved by making database backups, whereas I need
the possibility to create a valid portal configuration from sources;
hence my concern.
Regards,
Michael
Randy Watler wrote:
> Graffito Dev Team,
>
> For those that do not recognize me, I am a committer on the J2 portal team.
>
> Although I have been threatening to do this for some time, I am finally
> getting started on the integration of Graffito into J2 as a PageManager
> component. The intent is to store the PSML that currently resides in the
> file system in Graffito as XML documents. We will also want to leverage
> many of Graffito's features in the J2 implementation, including security
> and modification notification/timestamps.
>
> There are new patches to the J2 svn HEAD version related to Connection
> management, (see JS2-326), that should allow us to update the J2
> deployment past the M3 support currently in place.
>
> My personal goal is to commit this optional component into J2 for M4.
>
> Of course, many thanks for developing, managing, and promoting Graffito.
>
> Randy Watler
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org