Rapha�l Luta wrote:
>
> "Kevin A. Burton" wrote:
> >
> > oops... I meant <portal-structure> instead of <portlet-structure>
> >
> > :(
> >
>
> <portal-structure> is fine (don't know how cator handles hyphen though...).
If I remember correctly it creates an object named
"PortalStructure.java"
> We could also simply use <screen> since we're describing the content of a Turbine
> screen.
Not in the portletregistry...
> In fact, it's feature I plan to implement (but not for 1.2): support in PSML for
> multiple screen definition.
How is this different from multiple panes?
<snip>
> > > I am also working on a better user customization system and a
> > > getPortletStructure API which returns the Castor PortletStructure object
> > > would be cool.
> > >
> > > Thoughts?
>
> Not so sure about that, at least not with the current version of Castor. The
> Castor generated APIs are certainly very functional but not very OO since AFAIK
> Castor doesn't support yet type inheritance. This makes using these APIs somewhat
> painful as we can't use the features of the language. So I think we should avoid
> exposing castor generated elements in the main Jetspeed APIs and keep those as
> peers of the real Jetspeed elements.
I am cool with that. I was kicking around this idea too. The Castor
generated code also exposes marshal/unmarshal code too which can be
bad. This is why the code is now in xml.api which isn't a package that
should be used by users... So +1 for not exposing this.
> When Castor will be more mature maybe we will
> be able to use Castor-generated API without losing to much in functionality.
maybe.
--
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]
