Minor portlet changes for 4.1

[Howard Lewis Ship <hl...@gmail.com>]

I have a local client that is pretty desperate to get some minor changes
related to portlets into the 4.1 code. I expect to review and commit the
changes next week.  Just a FYI in terms of the 4.1 release.

-- 
Howard M. Lewis Ship
Independent J2EE / Open-Source Java Consultant
Creator and PMC Chair, Apache Tapestry
Creator, Jakarta HiveMind

Professional Tapestry training, mentoring, support
and project work.  http://howardlewisship.com

Fwd: Minor portlet changes for 4.1

[Jesse Kuhnert <jk...@gmail.com>]

Oops..Default gmail reply only went back to Howard. Sorry.

---------- Forwarded message ----------
From: Jesse Kuhnert <jk...@gmail.com>
Date: Jun 9, 2006 1:53 PM
Subject: Re: Minor portlet changes for 4.1
To: Howard Lewis Ship <hl...@gmail.com>

Sounds good. Now that we have maven2 for 4.1 we should theoretically be able
to create a nightly snapshot/continium build to keep people up to date in
between releases.

There are a couple outstanding maven related issues:

-) Testing - Doesn't really work "out of the box", but that's to be expected
because of the varying set of suites we have. Frankly I would rather spend
the time during this "transitional" phase to replace junit with
testng/upgrade easymock than any attempts to make existing stuff work with
maven "imho" ..

-) Only compiles right now and barely creates a shell site (ie no docs
ported yet ) .

The ant builds all work fine. I haven't added the ant logic to copy over the
built dojo/tapestry js packages into a jar but will be doing it this
weekend.

If you are doing anything related to scripting keep in mind the following
major changes:

-) Body doesn't directly manage JavaScript contributions now,
ResponseRenderer does. (it does call PageRenderSupport methods still, but
it's an indirect/deprecated sort of feature )

-) There are currently ResponseBuilders for:

 * Normal tapestry html - DefaultResponseBuilder
 * JSON renders - JSONResponseBuilder
 * Dojo/ajax renders - AjaxResponseBuilder

-) The ResponseBuilders are just hivemind services like anything else, so
anyone can override any one of them - or add a new one in whenever they
want...Allowing them to change almost every facet of how javascript is
managed/injected by tapestry.

-) JS unit tests - They don't get run by the default ant test task (still
need to investigate why, but as we're moving to maven I may just try and
make it work there instead) but do provide a means of testing some portions
of the tapestry js library if you choose to do so. Go to framework/src/js
and you will find the build.xml to invoke them as well as the
dojo/tapestry/test js packages.

I think the portlet pipeline is currently using the DefaultResponseBuilder
but it makes sense to create a new one specifically for portlets to me.


On 6/9/06, Howard Lewis Ship <hl...@gmail.com> wrote:
>
> I have a local client that is pretty desperate to get some minor changes
> related to portlets into the 4.1 code. I expect to review and commit the
> changes next week.  Just a FYI in terms of the 4.1 release.
>
> --
> Howard M. Lewis Ship
> Independent J2EE / Open-Source Java Consultant
> Creator and PMC Chair, Apache Tapestry
> Creator, Jakarta HiveMind
>
> Professional Tapestry training, mentoring, support
> and project work.   http://howardlewisship.com
>



-- 
Jesse Kuhnert
Tacos/Tapestry, team member/developer

Open source based consulting work centered around
dojo/tapestry/tacos/hivemind.


-- 
Jesse Kuhnert
Tacos/Tapestry, team member/developer

Open source based consulting work centered around
dojo/tapestry/tacos/hivemind.