I'm having trouble getting my new skin to apply to a theme i created. i cust
omized UnlayeredContainer-V.jsp in skins/html/myCustomskin - i altered the n
avigation display in here and i uploaded it to a subdirectory i created for 
my new skin, went through t
he 'add new skin' procedure in the Portal Admin section. myCustomskin shows 
up as a new skin,i attach it to a theme, which is attached to a place.. but 
it never shows up.
i thought websphere was supposed to inherit the interface jsps from the subd
irectories first and only if these don;t contain overwrites then go to the r
oot skin/html folder.

i had success overwriting the UnlayeredContainer-V.jsp file in this folder f
or awhile - but it changed the navigation across all of portal which is not 
what i'm looking for. however this cheap hack has now stopped working too.

does anyone have any idea where i'm going wrong and why the specified skins 
don't show up when they are set to be the default skin for a particular them
e.

thanks.

[ Post a follow-up to this message ]

not sure if this will help but when looking for unlayeredcontainer.jsp
etc, websphere looks in the the default skin-directory for that theme,
failing that, it just goes up to the HTML directory.
I be curious to know what navigation you've built as we have done a
lot of work on this to build a tree-like expand/collapse left-hand
navigator - but it is a bit of a black art and I would like to
sanity-check it with someone who has done similar.

John


dawachan <dawa@sdo.net> wrote in message news:<2034432473.1089851933204.JavaMail.wasadmin@sw
g3ws003>...
> I'm having trouble getting my new skin to apply to a theme i
created. i customized UnlayeredContainer-V.jsp in
skins/html/myCustomskin - i altered the navigation display in here and
i uploaded it to a subdirectory i created for my new skin, went
through the 'add new skin' procedure in the Portal Admin section.
myCustomskin shows up as a new skin,i attach it to a theme, which is
attached to a place.. but it never shows up.
> i thought websphere was supposed to inherit the interface jsps from the su
bdirectories first and only if these don;t contain overwrites then go to the
 root skin/html folder.
>
> i had success overwriting the UnlayeredContainer-V.jsp file in this folder
 for awhile - but it changed the navigation across all of portal which is no
t what i'm looking for. however this cheap hack has now stopped working too.
>
> does anyone have any idea where i'm going wrong and why the specified skin
s don't show up when they are set to be the default skin for a particular th
eme.
>
> thanks.

[ Post a follow-up to this message ]

to stop portal rendering it's own navigator, you're going to have to
strip out some/all of placebar.jsp. When you do this,
layeredcontainer.jsp 'takes' over and actually displays a left-hand
navigator which is quite good but lacks some functionaility, so we
decided to write our own version.

You'll need to work with layeredcontainer.jsp and use the model api to
iterate through all the pages and render the tags etc.

Drop me a line if you have any specific questions.

John



john@eagleinfosystems.com (jm) wrote in message news:<71d780da.0407170653.2d20f227@posting.g
oogle.com>... 
>
>
> i'm trying to do the same thing   there is virtually no
> documentation on this.
>
> my problem is that i want to construct a left nav bar statically (will
> move to
> dynamic creation later but just trying simple nav for now) i'm using
> the urlGeneration tag for my links.
>
> I setup my default page to load my links to the left of where the
> screen is rendering and this gets positioned correctly.  My problem is
> that the portal
> server is rendering a navigation tree automatically???
>
> How can i disable this automatic generation of the navigation tree in
> the
> <screenRender> area???
>
> John --> can you give me some pointers on how you went about creating
> your
> navigation tree?
>
> -jm

[ Post a follow-up to this message ]

jdaniells@yahoo.co.uk (John) wrote in message news:<e8c021ba.0407182354.cb64f84@posting.goog
le.com>...
> to stop portal rendering it's own navigator, you're going to have to
> strip out some/all of placebar.jsp. When you do this,
> layeredcontainer.jsp 'takes' over and actually displays a left-hand
> navigator which is quite good but lacks some functionaility, so we
> decided to write our own version.
>
> You'll need to work with layeredcontainer.jsp and use the model api to
> iterate through all the pages and render the tags etc.
>
> Drop me a line if you have any specific questions.
>
> John
>

I have created a static version of the left Menu and get it to appear
to
left of the <wps:screenRender/>component on Default.jsp.  This static
menu is created with <wps:urlGeneration> tags and works fine.

BUT.  - like you save pointed out.  the layeredContainer.jsp takes
over and creates a menu in addition to the one i have created

to fix this i have tried to create my own skin and override the
layeredContainer.jsp page.  I try to strip out the code that creates
the menu but i end up getting a blank page without my portlets.

Do you have any idea how to just get the portlets on my page to
display without the portal generating any left nav for me???

-jm

[ Post a follow-up to this message ]

>
> I have created a static version of the left Menu and get it to appear
> to
> left of the <wps:screenRender/>component on Default.jsp.  This static
> menu is created with <wps:urlGeneration> tags and works fine.
>
> BUT.  - like you save pointed out.  the layeredContainer.jsp takes
> over and creates a menu in addition to the one i have created
>
> to fix this i have tried to create my own skin and override the
> layeredContainer.jsp page.  I try to strip out the code that creates
> the menu but i end up getting a blank page without my portlets.
>
> Do you have any idea how to just get the portlets on my page to
> display without the portal generating any left nav for me???
>
> -jm

Follow up on above:  It appears that my skins are not getting parsed
correctly. I look in the log and the /themes/html/MyTheme/Default.jsp
is
getting parsed but the corresponding skin in
skins/html/MySkin/layeredContainer.jsp is not getting initialized.  I
restart the server and it doesn't help.

I'm using the test environment with 5.02 and Portal Toolkit.  Is there
a problem with new skins and 5.02?  I don't think this is a cache
problem as
i restart WPS and it doesn't help.  Can somebody confirm that adding
new
skins works with 5.02 and portal toolkit?

-jm

[ Post a follow-up to this message ]

Hi jm,

Did you do the folowing: (from the wps infocenter)
--------------------------------------------------------
1. Open the file was_root/config/cells/node_name/applications/wps.ear/deploy
ments/wps/wps.war/WEB-INF/ibm-web-ext.xmi
2. Find the following entry in this file:
<webappext:WebAppExtension xmi:version="2.0" xmlns:xmi="http://www.omg.org/X
MI"
xmlns:webappext="webappext.xmi" xmlns:webapplication="webapplication.xmi"
xmlns:commonext="commonext.xmi" xmlns:common="common.xmi"
xmi:id="IBM_WPS_Ext" reloadInterval="3" reloadingEnabled="false"
fileServingEnabled="true" directoryBrowsingEnabled="false"
serveServletsByClassnameEnabled="false" preCompileJSPs="false">

3. Change the value for reloadingEnabled to true.
4. Save the file.
5. Restart the portal server.
--------------------------------------------------------

I'll hope this will help. This is the way i did it.

 
> and get it to appear 
> Default.jsp.  This static 
> works fine. 
> layeredContainer.jsp takes 
> have created 
> override the 
> code that creates 
> my portlets. 
> on my page to 
> for me??? 
>
> Follow up on above:  It appears that my skins are not
> getting parsed
> correctly. I look in the log and the
> /themes/html/MyTheme/Default.jsp
> is
> getting parsed but the corresponding skin in
> skins/html/MySkin/layeredContainer.jsp is not getting
> initialized.  I
> restart the server and it doesn't help.
>
> I'm using the test environment with 5.02 and Portal
> Toolkit.  Is there
> a problem with new skins and 5.02?  I don't think
> this is a cache
> problem as
> i restart WPS and it doesn't help.  Can somebody
> confirm that adding
> new
> skins works with 5.02 and portal toolkit?
>
> -jm

[ Post a follow-up to this message ]

Add a <wps:navigation> tag that goes through at least two levels.  This
will prevent the left nav from being auto-generated.

Justin

jm wrote:
> jdaniells@yahoo.co.uk (John) wrote in message news:<e8c021ba.0407182354.cb
64f84@posting.google.com>...
> 
>
>
> I have created a static version of the left Menu and get it to appear
> to
> left of the <wps:screenRender/>component on Default.jsp.  This static
> menu is created with <wps:urlGeneration> tags and works fine.
>
> BUT.  - like you save pointed out.  the layeredContainer.jsp takes
> over and creates a menu in addition to the one i have created
>
> to fix this i have tried to create my own skin and override the
> layeredContainer.jsp page.  I try to strip out the code that creates
> the menu but i end up getting a blank page without my portlets.
>
> Do you have any idea how to just get the portlets on my page to
> display without the portal generating any left nav for me???
>
> -jm

[ Post a follow-up to this message ]