I am glad I joined this list, because now I know that at least I am
not the only one with some of these problems. I wish the project owners
would peruse this list from time-to-time. I guess they are too busy
coding the newest release. I think I have the same problem as Ashok.
To be more specific...My problem is dynamically including new psml
files in new JSP templates. It appears that jetspeed registers the name
of each psml as a named pane somewhere. I have looked through all of
the configuration files and I haven't been able to find this. It also
appears that panes are loaded with the tag <jetspeed:pane
name="panename" /> for the templates...I think. At least that is how it
appears that the default.jsp loads the home pane (via the included
Home.jsp). I have tried using this tag to call a different pane (is
pane a synonym for portal?), but it always loads the default pane. My
goal is to create templates for different functional areas and have
these load the relevant panes. It would be cool if there was a tag that
allowed a developer to specify the psml file and the template together
for the desired output--kind of like you can specify an XML and XSL
together file with XTags.
One issue that has bothered me a little is that Jetspeed is
completely designed around users/roles/groups when on many sites one
wishes to organize portals and templates around functionality. It seems
that Jetspeed forces you to describe and reference portals in the
context of these users/groups rather than by functional area. Maybe I
just haven't figured out how to do this yet. Best regards, Aaron
BTW: To the developers: I can't believe you guys are developing two
different templating systems--Velocity and JSP. Isn't this thing
complicated enough? It would be awesome if instead of having two
template systems we had just one verbose set of JSP tags for describing
templates.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
