Hi Mansour,
See comments inline below. Sorry if this is reiterating things you
already know, it can be hard to tell just how much someone already knows
on the list sometimes.
Mansour Al Akeel wrote:
And I don't even know if it's possible ot include the HTMLPortlets
derectely in the psml file.
Yes, you can add portlets directly to the psml.
My understanding is that I need to create a portlet entry for each
page, then add them to the PSML file.
Like I said in another branch of this thread, you can do it that way,
creating a single portlet for an entire html page, but I'd recommend
encapsulating any recurring content (for ex. a side bar perhaps that
displays a list of sponsor or partner logos that might get displayed on
several pages). That way any modifications/updates to recurring content
can be handled more easily by editing a single file instead of having to
hit each html page that uses the content.
The problem here, even if I wanted to use this method, there's no
example about adding the portlet entry to the registry for JS2.
The portlet registry is seperate from the psml file and is in the
portlet.xml of your portlet application. Check out the j2-admin project
from the repo and have a look at it.
As far as I can remember, I did this while ago, but it was through
j2-admin tool, where you can choose the portlet to add it to the page,
then you can go and customize the url. I can not find this portlet. I
would prefer to add the pages to psml directly.
Any ideas?
Mansour Al Akeel wrote:
Ron, thank you. This was my suggestion in the first place. What do I
do with the existing html pages ?
Do I add each individual page separately as a Html portlets and put
it into psml file ? What about the menus ?
Ron Wheeler wrote:
You might want to think about this from a different approach.
You might find that you just need to add the existing HTML as html
portlets to you new portal.
Make these available to anyone prior to logging in.
If you go to www.napaexcellence.ca, you can see all of the public
content which is for the most part static content.
We built this portal in stages. The first stage was a "marketing"
site that only had static HTML pages delivered by Jetspeed and then
we added some dynamic portlets (catalog search) and finally a full
portal.
Ron
Mansour wrote:
Hello everyone,
I am looking to add jetspeed to an existing website. The site
already contains few static html pages. We need to give the users
the ability to login and use applications provided by jetspeed. A
problem would be is how to introduce JS2 to the system. A possible
way is to add login fields (username and password) to the existing
pages, and forward the credential to jetspeed. So the users, will
be visiting the same old pages (HTML), and they can login with
their credentials. A problem with this approach is, it limits our
ability to add portlets that can be viewed by the public. So, if we
decided that portlet1 is to be available to all users, we have to
find a solution for this and it will be a pain to do it. Another
way is to use HTML portlets or IFrame, but these will be pain as
well, as we have to create a portlet for each existing page and
update the links back and forth, plus we have to consider the
navigation menus.
The existing site consists of html pages, and menu items (contact
us, about us, products(a page for each ), services(a page for each
), home , documentation,......etc) with javascripts.
I though about using the concept of subsites, but AFAIK, it's for
hosting another jetspeed instance, and can not be used for HTML.
If someone have done something similar to this please provide me
with an advice.
Thank you in advance.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
