Re: Portlet related issues

2009-01-23 Thread German Morales
Well, i haven't tried but from what i see the images suggestion should
work...

By the way, i see that there is a chance of conflict between our CSSs and
the ones of the portal, and other portlets.

I'm understanding now that it's not that simple to take a working wicket
application and deploying it as a portlet.
Is there anything else we should consider?
(I'm having some trouble with some javascript too, i didn't have time to
check the reason yet).

Additionally, how do i get access to portal services like single sing-on?

Thanks for the help,

German

2009/1/22 German Morales germanamora...@gmail.com

 Hi Serkan,

 Thanks for the answer, i will give it a try and post the results later

 German

 2009/1/22 Serkan Camurcuoglu serkan.camurcuo...@telenity.com

 1. To overcome this problem in my application I put my css and image files
 into the jetspeed layout template directory, for example
 /jetspeed/decorations/layout/tigris/css/styles.css and modified the template
 velocity file to include my css file.

 2. I think that's normal, and I think it would be impossible to confine
 the modal window within your portlet div since it's on a different z-index.
 If you want it to look better, you can try to style the modal window to
 better suit your portal page.

 hope this helps..

 SerkanC





 German Morales wrote:

 Hi all,

 I'm trying to run an existing wicket application as a Portlet.
 I've chosen Jetspeed-2, because it's Apache too, and i've also read in
 the
 list that people working in the Portlet support also work in Jetspeed
 development.

 I've got some success, specially following this HowTo:
 http://cwiki.apache.org/WICKET/portal-howto.html

 After some effort, my application is basically running.
 However, i'm having trouble with some issues:

 1. CSS references to images (as div backgrounds).
   I've read in some forums and it seems to be generic problem in portals.
   CSS have URLs to images, which the portal does not transform to provide
 a
 redirection.
   The browser, then asks for the images to the portal server directly, no
 redirection is done to the portlet application.
   Any tips on how to solve this?
   (there seems to be a workaround for WebLogic portal:
 http://www.gexperts.com/blog/archives/2007/12/entry_20.html)

 2. ModalWindow
   ModalWindow works by hanging (with javascript) a new div from the body
 of
 the current document.
   This works wonderful when Wicket is the owner of the page.
   However, the application is now inside a portlet window, not in the
 whole page.
   When ModalWindow hangs from the page as usual, it looks odd... it's
 outside the portlet window.
   Any ideas?

 Thanks in advance,

 German





 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org





Portlet related issues

2009-01-22 Thread German Morales
Hi all,

I'm trying to run an existing wicket application as a Portlet.
I've chosen Jetspeed-2, because it's Apache too, and i've also read in the
list that people working in the Portlet support also work in Jetspeed
development.

I've got some success, specially following this HowTo:
http://cwiki.apache.org/WICKET/portal-howto.html

After some effort, my application is basically running.
However, i'm having trouble with some issues:

1. CSS references to images (as div backgrounds).
   I've read in some forums and it seems to be generic problem in portals.
   CSS have URLs to images, which the portal does not transform to provide a
redirection.
   The browser, then asks for the images to the portal server directly, no
redirection is done to the portlet application.
   Any tips on how to solve this?
   (there seems to be a workaround for WebLogic portal:
http://www.gexperts.com/blog/archives/2007/12/entry_20.html)

2. ModalWindow
   ModalWindow works by hanging (with javascript) a new div from the body of
the current document.
   This works wonderful when Wicket is the owner of the page.
   However, the application is now inside a portlet window, not in the
whole page.
   When ModalWindow hangs from the page as usual, it looks odd... it's
outside the portlet window.
   Any ideas?

Thanks in advance,

German


Re: Portlet related issues

2009-01-22 Thread Serkan Camurcuoglu
1. To overcome this problem in my application I put my css and image 
files into the jetspeed layout template directory, for example 
/jetspeed/decorations/layout/tigris/css/styles.css and modified the 
template velocity file to include my css file.


2. I think that's normal, and I think it would be impossible to confine 
the modal window within your portlet div since it's on a different 
z-index. If you want it to look better, you can try to style the modal 
window to better suit your portal page.


hope this helps..

SerkanC




German Morales wrote:

Hi all,

I'm trying to run an existing wicket application as a Portlet.
I've chosen Jetspeed-2, because it's Apache too, and i've also read in the
list that people working in the Portlet support also work in Jetspeed
development.

I've got some success, specially following this HowTo:
http://cwiki.apache.org/WICKET/portal-howto.html

After some effort, my application is basically running.
However, i'm having trouble with some issues:

1. CSS references to images (as div backgrounds).
   I've read in some forums and it seems to be generic problem in portals.
   CSS have URLs to images, which the portal does not transform to provide a
redirection.
   The browser, then asks for the images to the portal server directly, no
redirection is done to the portlet application.
   Any tips on how to solve this?
   (there seems to be a workaround for WebLogic portal:
http://www.gexperts.com/blog/archives/2007/12/entry_20.html)

2. ModalWindow
   ModalWindow works by hanging (with javascript) a new div from the body of
the current document.
   This works wonderful when Wicket is the owner of the page.
   However, the application is now inside a portlet window, not in the
whole page.
   When ModalWindow hangs from the page as usual, it looks odd... it's
outside the portlet window.
   Any ideas?

Thanks in advance,

German

  



-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: Portlet related issues

2009-01-22 Thread German Morales
Hi Serkan,

Thanks for the answer, i will give it a try and post the results later

German

2009/1/22 Serkan Camurcuoglu serkan.camurcuo...@telenity.com

 1. To overcome this problem in my application I put my css and image files
 into the jetspeed layout template directory, for example
 /jetspeed/decorations/layout/tigris/css/styles.css and modified the template
 velocity file to include my css file.

 2. I think that's normal, and I think it would be impossible to confine the
 modal window within your portlet div since it's on a different z-index. If
 you want it to look better, you can try to style the modal window to better
 suit your portal page.

 hope this helps..

 SerkanC





 German Morales wrote:

 Hi all,

 I'm trying to run an existing wicket application as a Portlet.
 I've chosen Jetspeed-2, because it's Apache too, and i've also read in the
 list that people working in the Portlet support also work in Jetspeed
 development.

 I've got some success, specially following this HowTo:
 http://cwiki.apache.org/WICKET/portal-howto.html

 After some effort, my application is basically running.
 However, i'm having trouble with some issues:

 1. CSS references to images (as div backgrounds).
   I've read in some forums and it seems to be generic problem in portals.
   CSS have URLs to images, which the portal does not transform to provide
 a
 redirection.
   The browser, then asks for the images to the portal server directly, no
 redirection is done to the portlet application.
   Any tips on how to solve this?
   (there seems to be a workaround for WebLogic portal:
 http://www.gexperts.com/blog/archives/2007/12/entry_20.html)

 2. ModalWindow
   ModalWindow works by hanging (with javascript) a new div from the body
 of
 the current document.
   This works wonderful when Wicket is the owner of the page.
   However, the application is now inside a portlet window, not in the
 whole page.
   When ModalWindow hangs from the page as usual, it looks odd... it's
 outside the portlet window.
   Any ideas?

 Thanks in advance,

 German





 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org