Mark Nickel wrote:
>
> In the spirit of open discussion, I hope to begin a thread here where we can
> explore how people intend to use the Jetspeed API.
>
> I am intending to use both Jetspeed and Cocoon to develop an Intranet/Extranet at
> the company where I work. My plan is to use Jetspeed to handle the user
> authentication and session management, and to use the CocoonPortlet, Cocoon, and
> XSP for the business logic stuff--checking onhand balances, order statuses, etc.
+1. There is a bug in Cocoon 1.7.0 that prevents XSP from working
within Jetspeed. Haven't had time to fix it. :(
> I know that I should probably use Turbine instead of Jetspeed if all I would use
> of Jetspeed is the user authentication components. But the advantage of Jetspeed
> is that when I'm ready, I can easily include content from other information
> sources using the RSSPortlet, etc. As well as provide a host of other services as
> they develop--calendaring, mail, discussion boards, etc...
yup!
> Cocoon usage is fairly evident. As we migrate our internal messanging environment
> to XML, Cocoon will play a great roll in managing that information.
>
> Because I plan on using Jetspeed on our intranet to display remote content, I am
> thinking of an enhancement to the way RSSPorlet works. Generally within a
> company, not all people have access directly through the firewall to the
> Internet. If I use Jetspeed and a RSSPortlet, I will eventually be displaying
> href's to sites that most users of the Intranet will not be able to access because
> they don't have access through the firewall.
>
> I'm thinking that it might be interesting to have a security property that could
> be defined on a per entry basis for each portlet in PML. If a security property
> was set to "read_only" in the portlet markup language file, then the RSSPortlet
> would not render a href to the article or newsbyte. The default behavior would of
> course be to have the RSSPortlet render the RDF file just as it is done in the
> defaultPortlets.xml
If you don't want your users going out on the Internet then you probably
shouldn't show them a carrot like the RSS content. I don't think it is
unsafe to say that a requirement for Jetspeed is an Internet
connection... at least through a Proxy server.
> I'm using the RSSPortlet as an example, but I'm sure that it could be extended to
> any of the portlets that pull in content from other sites.
>
> Basically the portlet security property would be a way to include RDF information
> from out on the Internet, but not provide any "clickable" links for people to
> explore. I know that this seems a bit Draconian, not to provide links to data,
> but it would be a compromise between not providing any offsite information on our
> Intranet and allowing every user in the organization Internet access---which an HR
> nightmare...
Proxy Server! :) It isn't an HR nightmare if you do it right.
<snip>
--
Kevin A Burton ([EMAIL PROTECTED])
http://relativity.yi.org
Message to SUN: "Please Open Source Java!"
"For evil to win is for good men to do nothing."
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
