webwork-user — WebWork users mailing list

Re: [Webwork-user] velocity usage in WW (docs)

[Matt B. <ma...@sm...>]

Yes, we could really use some help in regards to Velocity+WebWork. For now,
the preferred format is still docbook. I will be transitioning this soon. If
you are still interested, you can e-mail me offline to work out the doc
details.

-Matt

----- Original Message -----
From: "Marc Logemann" <dev...@lo...>
To: <web...@li...>
Sent: Saturday, July 06, 2002 6:14 AM
Subject: [Webwork-user] velocity usage in WW (docs)


> Hi,
>
> i am using velocity as view for webwork. There are some sentences in the
docs
> about how to start with this combination, but IMO it could be expanded
> a lot. There is also some TODO paragraph at the end.
>
> If there is nothing against it, i would start to document this better as
soon
> i read through the main classes of Webwork to really understand the action
> behavior.
>
> But what is the desired format for any doc contributions? I heard that
docbook
> should be droped??
>
>
> ---
> Marc Logemann
> (see him @ www.logemann.info)
>
>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Got root? We do.
> http://thinkgeek.com/sf
> _______________________________________________
> Webwork-user mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/webwork-user
>
>

Re: [Webwork-user] OT: AOP toolkit, was Why I like WebWork

[Rickard <ri...@dr...>]

Roger Holbrook wrote:
> Many thanks.

No promises ;-)

>> Nope, this is actually my first purely closed source project :-) Feels=
=20
>> strange really. We might do a developer source license though, or at=20
>> least an open API for plugins.
>=20
> Is there a corporate presence yet - where do we check for news of progr=
ess?

Not yet. We created the company a couple of weeks ago, and coding has=20
just begun. The others have already done it before though, so we expect=20
to have something running by mid August. I'll make an announcement when=20
the first release is available for purchase/demo. I'll probably also=20
describe how we're using WebWork, as it seems we will be using it alot,=20
both for applet/server comms and actual page rendering.

/Rickard

--=20
Rickard =D6berg

Re: [Webwork-user] OT: AOP toolkit, was Why I like WebWork

[Roger H. <ro...@fl...>]

Rickard wrote:
>> If these are long, is there  anything you would consider making a 
>>snapshot of, as you did for the  'first go'?
>
>I'll have to check with the others.

Many thanks.

>Nope, this is actually my first purely closed source project :-) Feels 
>strange really. We might do a developer source license though, or at 
>least an open API for plugins.

Is there a corporate presence yet - where do we check for news of 
progress?

Roger

Re: [Webwork-user] OT: AOP toolkit, was Why I like WebWork

[Rickard <ri...@dr...>]

Roger Holbrook wrote:
> I can well understand wanting to test it in you own stuff first - do yo=
u=20
> have any feel for the time scales involved? =20

Probably somewhere in October/November.

> If these are long, is there=20
> anything you would consider making a snapshot of, as you did for the=20
> 'first go'?  I don't wish to sound impatient - I'm just fascinated by=20
> this bit of code!  I happened to bump into the 'first go' soon after I=20
> worked out the Proxy class was 'interesting' - I just hadn't understood=
=20
> quite 'how interesting' it might be :-)

I'll have to check with the others.

> Also off topic, but this time with regard to the content management=20
> system - are you pursuing the JDO / RDF scheme you outlined previously?=
=20

No, we'll be using plain serialisation for the storing, since we have=20
almost no needs at all for queries. The content is just one big tree of=20
objects. It wouldn't be difficult to add a JDO or RDF persistence=20
manager to it however, but right now I don't see what we'd gain from it.=20
We'll see.

> If this is your main product, then presumably you won't be opensourcing=
=20
> this code?=20

Nope, this is actually my first purely closed source project :-) Feels=20
strange really. We might do a developer source license though, or at=20
least an open API for plugins.

/Rickard

--=20
Rickard =D6berg

Re: [Webwork-user] WebWorkVelocityServlet views

[G.L. G. <ga...@gr...>]

> Another way of doing this using the ParameterAware interface is as
> follows.  Assuming your Products Action class above has getMyParam() and
> setMyParam(String) methods.  The setMyParam method will be called if
> there's a "myParam" parameter.  Then, within the Velocity template
> forwarded to from that Action you can access it like this:

One thing I didn't understand about this is how the Product class would be
mapped to that 'select' context. Are you saying that in the views.properties
I'd have my Products Action return the view "selectB.success" (like below)
and then in my velocity template I'd write what's below (assuming MyParam is
actually a getMyParam() method of the Action)?

velocity.Products.selectB.success=prods/prods.vm?select=myVal

Which I know I'm misunderstanding because the val of the select key would
not be used.

>     ## assumes the Products Action is mapped to select.
>     #if ( $select.MyParam )  ## same as $select.getMyParam()
>         ## do something
>     #end
>

Much thanks and all help appreciated.

Re: [Webwork-user] OT: AOP toolkit, was Why I like WebWork

[Roger H. <ro...@fl...>]

Rickard wrote:
>What I have now is a rewrite of that stuff. It wasn't very scalable 
>(e.g. interceptor/aspect instances couldn't be reused even if they were 
>stateless), and making interceptors Proxy InvocationHandlers just 
>wasn't the best way to do it. What I have now is not only easy to work 
>with, it's scalable (stateless instances can be reused, and object 
>caches can be flushed, like EJB) and fast (during an invocation no 
>objects are created by the framework itself). Other than that the basic 
>semantics is the same as the old framework.

>See above, it's a lot better/simpler. Who would've thought that 
>possible..

>Anyway, we've talked about doing the AOP toolkit as a separate thing 
>from our main product (which is a content management system). We'd like 
>to test it in our own stuff first, to see if it can be used in a large 
>system effectively. We think so, but need to try to actually know so :-)

I can well understand wanting to test it in you own stuff first - do you 
have any feel for the time scales involved?  If these are long, is there 
anything you would consider making a snapshot of, as you did for the 
'first go'?  I don't wish to sound impatient - I'm just fascinated by 
this bit of code!  I happened to bump into the 'first go' soon after I 
worked out the Proxy class was 'interesting' - I just hadn't understood 
quite 'how interesting' it might be :-)

Also off topic, but this time with regard to the content management 
system - are you pursuing the JDO / RDF scheme you outlined previously? 
If this is your main product, then presumably you won't be opensourcing 
this code? - unless perhaps there are other generic modules? Etc. etc. - 
ever curious????

Roger

Re: [Webwork-user] Why I like WebWork

[Rickard <ri...@dr...>]

Matt Baldree wrote:
> What are you using instead of Aspect and why did you decide not to use =
it?

What I'm using is already answered in other posts, but why I didn't use=20
it is for the following reasons:
1) the need for a proprietary compiler
2) the somewhat unwieldy language extensions in AspectJ
3) the inability to do runtime changes (everything in AspectJ is=20
compiletime)
4) I needed the system as a whole to be proxy-based in order to do=20
memorymanagement with object caches. Since AspectJ works on regular=20
classes that wouldn't work (AFAIK).
5) I wanted to find out if it was possible to implement AOP using plain=20
Java.

That's about it I guess.

/Rickard

--=20
Rickard =D6berg

Re: [Webwork-user] Why I like WebWork

[Matt B. <ma...@sm...>]

What are you using instead of Aspect and why did you decide not to use it?

----- Original Message -----
From: "Rickard" <ri...@dr...>
To: "Christoph Kiehl" <ki...@su...>
Cc: <web...@li...>
Sent: Wednesday, July 10, 2002 4:22 AM
Subject: Re: [Webwork-user] Why I like WebWork


Christoph Kiehl wrote:
>>ps. and instead of EJB we're using AOP which makes the app really
>>ultracool, but that's another story..
>
> What is AOP? ;)

Aspect Oriented Programming. The "next big thing" as they say. Been
using it for a couple of weeks now (no, I'm not using AspectJ) and I
never ever want to go back to plain old OOP again :-))) I just love the
flexibility I get from being able to "tack on" new interfaces and call
interceptors to objects without redesigning my whole app. It rocks. :-)

/Rickard

--
Rickard Öberg



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Two, two, TWO treats in one.
http://thinkgeek.com/sf
_______________________________________________
Webwork-user mailing list
Web...@li...
https://lists.sourceforge.net/lists/listinfo/webwork-user

Re: [Webwork-user] OT: AOP toolkit, was Why I like WebWork

[Rickard <ri...@dr...>]

Roger Holbrook wrote:
> and spent several days playing.  I just kept reading, and reading, and =
smiling ;)  It
> was hugely instructive - many, many thanks for this gift.
>=20
> So here we are, 6 months later, and you mention your AOP Toolkit -

What I have now is a rewrite of that stuff. It wasn't very scalable=20
(e.g. interceptor/aspect instances couldn't be reused even if they were=20
stateless), and making interceptors Proxy InvocationHandlers just wasn't=20
the best way to do it. What I have now is not only easy to work with,=20
it's scalable (stateless instances can be reused, and object caches can=20
be flushed, like EJB) and fast (during an invocation no objects are=20
created by the framework itself). Other than that the basic semantics is=20
the same as the old framework.

It'd probably be quite trivial to implement an EJB server using it. But,=20
then you'd miss all the good stuff that AOP gives you. As I said, being=20
able to just add interfaces/implementations to an object without=20
actually modifying any code is quite powerful. Ya can't do that in EJB,=20
fer shure.

>>The core of it is really generic, and entirely based on reflection/dyna=
mic proxies.
>=20
> Needless to say, I'm now just full of curiosity!
>=20
> Has the Toolkit progressed since the 'first go' ? And if so how?
> It was so simple in its initial conception, that almost any change woul=
d imply a
> conceptual adjustment? etc. etc. ??????????????
>=20
> I for one, would love to see the current version being opensourced!

See above, it's a lot better/simpler. Who would've thought that possible..

Anyway, we've talked about doing the AOP toolkit as a separate thing=20
from our main product (which is a content management system). We'd like=20
to test it in our own stuff first, to see if it can be used in a large=20
system effectively. We think so, but need to try to actually know so :-)

/Rickard

--=20
Rickard =D6berg

Re: [Webwork-user] "text" or "'text'" ?

[Rickard <ri...@dr...>]

Ryan LeCompte wrote:
> Just a bit confused here... (I'm new to WebWork, obviously).
> How do I know when to use "text" or "'text'" in the WebWork
> JSP Tag attributes? (I know for id it should be "text", but
> I've seen value used in different ways, etc.)
>=20
> Is there a rule? Perhaps I missed it in the documentation.

'text'=3D"text" string. gives a constant value
text=3Devaluate the text property

This holds for all attributes except id, since that is an attribute that=20
is generally defined and whose behaviour we can't/shouldn't change.

/Rickard

--=20
Rickard =D6berg

[Webwork-user] RE: Reporting

[Michael v. L. <M.v...@ef...>]

Hi Peter,

> Has anyone come up with a good way to hang printable reports=20
> off webwork actions which supply the report data ?

We finally went for flash printing, i.e.
- view to a jsp-page containing the flash code ref,
- from the flash-code, call the print-action,
- let the printaction supply a jsp generating XML,
- let flash read, layout and print the stuff,
- let flash call another action for finishing up.

You can also layout on screen and use javascript:
- frames['MAIN'].focus(); frames['MAIN'].print();

Regards,
Micha=EBl
=09
!Effective
M.J.P. van Leeuwen
Software Architect
Westersingel 46
3014 GT Rotterdam
tel.	+31 (0)10 22 11 834
mob.	+31 (0) 6 5577 4487
fax.	+31 (0)10 22 11 800
e-mail	m.v...@ef...=20
website	http://www.effective-it.com
=20

Re[2]: [Webwork-user] Reporting

[Peter K. <pe...@mo...>]

We actually need proper report printing with pagination and repeating
headings etc. HTML would be nice but I don't think it has the features
we need and the printing is not quite what we want.

Thursday, July 11, 2002, 11:46:22 PM, Philipp Meier wrote:

PM> On Thu, Jul 11, 2002 at 12:15:04PM +1000, Peter Kelley wrote:
>> Has anyone come up with a good way to hang printable reports off
>> webwork actions which supply the report data ?

PM> I'm not sure if I understand you correctly, but if you want to "dump"
PM> the result I would suggest using the XSLT-Servlet and a simple
PM> Stylesheet which formats any XML to a printable HTML or plaintext
PM> document. A good starting point is the XSLT stylesheet shipping with
PM> webwork.

PM> -billy.



-- 

regards,
Peter Kelley

MoveIt Pty Ltd    

"If you want to build a ship, don't drum up the men to
gather wood, divide the work and give orders. Instead, 
teach them to yearn for the vast and endless sea."
- Saint-Exupery

Re: [Webwork-user] WebWorkVelocityServlet views

[Bill B. <bi...@pr...>]

Hello,

See below ...

"G.L. Grobe" wrote:
> 
> Still trying to figure this one out. Below is my original action where I
> would compare the values of 'view' and return a view mapping pending the
> value of view ...
> 
> public class Products extends ActionSupport implements ParameterAware {
>    private Map params;
>    ...
>    public void setParameters(Map map) { this.params = map; }
> 
>    public String doExecute() throws Exception {
> 
>       if (view.equals("myview.a")) {
>          return "selectA.success";
>       }
>       else if (view.equals("myview.b")) {
>          return "selectB.success";
>       }
> 
>       return "select.error";
> }
> 
> Then I needed to capture the parameter from within the action (coming from
> the velocity *.vm template) so I changed the class I extended from and now
> have ...

The WebWorkVelocityServlet is part of the _view_, not the model or
controller so it has nothing to do with the Action interface and as such,
the ServletDispatcher will never invoke it as an Action.  Instead, it will
_forward_ to it just like it would a JSP if you have the mappings defined
appropriately.  As a result, the ParameterAware interface will have no
effect they way you're using it.

WebWorkVelocityServlet exposes the HttpServletRequest in the Velocity
context as $req (see the  createContext method and in VelocityServlet.java
the static final REQUEST).  So there's no need to extend
WebWorkVelocityServlet (for this purpose).

The bottom line is there's nothing extra you need to do to access request
parameters within a Velocity template--just call $req.getParameter("foo")
or whatever method you want to call.  

> public class Products extends WebWorkVelocityServlet implements
> ParameterAware {
>    private Map params;
>    ...
>    public void setParameters(Map map) { this.params = map; }
> 
>    public Template handleRequest(Context context) {
>       HttpServletRequest request = (HttpServletRequest)
> context.get(REQUEST);
>       HttpServletResponse response = (HttpServletResponse)
> context.get(RESPONSE);
>    }
> }

With the code below, it will throw a NullPointerException if myParam
doesn't exist.

> As I understand it, I now have the handleRequest() method above so that I
> can get a query string parameter from the servlet now and write something
> like this in the template page ...
> --- *.vm file
>    #if ( $reqParser.getParameter("myParam").equals("this_string") )
>       ## do something
>    #end

Instead, do this which will work whether myParam exists or not ...
    #if ( $req.getParameter("myParam") == "this_string" )
        ## do something
    #end

Another way of doing this using the ParameterAware interface is as
follows.  Assuming your Products Action class above has getMyParam() and
setMyParam(String) methods.  The setMyParam method will be called if
there's a "myParam" parameter.  Then, within the Velocity template
forwarded to from that Action you can access it like this:

    ## assumes the Products Action is mapped to select.
    #if ( $select.MyParam )  ## same as $select.getMyParam()
        ## do something
    #end

> The problem is that whereas I had the execute() method from the first ex.
> (extended from ActionSupport) to compare views and return a different view
> pending on the value of view, I don't know how to do this (return views
> pending a query string parameter in the servlet request) w/ the
> WebWorkVelocityServlet.

If you want to access the existing parameters from the current request to
the action, they will also be available to any Velocity template as shown
above.

> So what I have is a query string coming from the template to the action, and
> then I'll return a view mapping w/ query string parameters back to the
> browser.

If you're trying to create URL's in the Velocity template that pass
through the parameters, I'm not sure of the best way to do that.  The
#url() macro can be used to generate a URL.  Parameters can be added and
the end result will be properly encoded.  

> Any help much appreciated.

Hope this helps,
-Bill

Re: [Webwork-user] Why I like WebWork

[Roger H. <ro...@fl...>]

Hi Rickard

>WATKIN-JONES,ADAM (HP-UnitedKingdom,ex1) wrote:
>> I'm delurking to ask what is surely a daft question but here goes:  if not
>> AspectJ, then what AOP toolkit are you using?
>>
>> (Obvious answer: having super programming-chops, you've written an AOP kit
>> yourself!  In which case, is this something you may put into the public
>> domain!?)
>
>The obvious answer is quite correct. Whether or not it will be
>opensourced is something that is yet to be determined. We've thought
>about it. The core of it is really generic, and entirely based on
>reflection/dynamic proxies. With JDK1.4 the overhead for that is so
>small that it's rather ok to apply it just about everywhere. And boy oh
>boy does it rock :-) It's so cool to have an object implement 10
>interfaces but not have a single class implement more than 1... it's
>what code reuse ought to be like.
>
>/Rickard

I'm also delurking since this is such a tempting topic!

When you posted your message last year titled:

        '[Meinds-developers] Aspect oriented framework, first go'

at:

        http://www.geocrawler.com/archives/3/15432/2001/11/0/7186838/

I downloaded the code from:

        http://prdownloads.sourceforge.net/meinds/aspects.zip?download

and spent several days playing.  I just kept reading, and reading, and smiling ;)  It
was hugely instructive - many, many thanks for this gift.

So here we are, 6 months later, and you mention your AOP Toolkit -
> The core of it is really generic, and entirely based on reflection/dynamic proxies.
Needless to say, I'm now just full of curiosity!

Has the Toolkit progressed since the 'first go' ? And if so how?
It was so simple in its initial conception, that almost any change would imply a
conceptual adjustment? etc. etc. ??????????????

I for one, would love to see the current version being opensourced!

Roger

[Webwork-user] Reporting

[Peter K. <pe...@mo...>]

Has anyone come up with a good way to hang printable reports off
webwork actions which supply the report data ?

-- 

regards,
Peter Kelley

MoveIt Pty Ltd    

"If you want to build a ship, don't drum up the men to
gather wood, divide the work and give orders. Instead, 
teach them to yearn for the vast and endless sea."
- Saint-Exupery

[Webwork-user] "text" or "'text'" ?

[Ryan L. <rm...@lo...>]

Hello all,

Just a bit confused here... (I'm new to WebWork, obviously).
How do I know when to use "text" or "'text'" in the WebWork
JSP Tag attributes? (I know for id it should be "text", but
I've seen value used in different ways, etc.)

Is there a rule? Perhaps I missed it in the documentation.

Thanks,

Ryan LeCompte
rm...@lo...
http://www.louisiana.edu/~rml7669

Re: [Webwork-user] Why I like WebWork

[Rickard <ri...@dr...>]

WATKIN-JONES,ADAM (HP-UnitedKingdom,ex1) wrote:
> I'm delurking to ask what is surely a daft question but here goes:  if =
not
> AspectJ, then what AOP toolkit are you using?
>=20
> (Obvious answer: having super programming-chops, you've written an AOP =
kit
> yourself!  In which case, is this something you may put into the public
> domain!?)

The obvious answer is quite correct. Whether or not it will be=20
opensourced is something that is yet to be determined. We've thought=20
about it. The core of it is really generic, and entirely based on=20
reflection/dynamic proxies. With JDK1.4 the overhead for that is so=20
small that it's rather ok to apply it just about everywhere. And boy oh=20
boy does it rock :-) It's so cool to have an object implement 10=20
interfaces but not have a single class implement more than 1... it's=20
what code reuse ought to be like.

/Rickard

--=20
Rickard =D6berg

[Webwork-user] Action doesn't execute every time

[<jo...@ho...>]

Hi,

We have an WebWork action class that executes the first time it's called, 
then from the JSP page a modal dialog appears with information from the 
action. When user closes that dialog and wants to run the same action to get 
other data the previous data appears again (the action doesn't executes).

Why and how to fix this?

// Jocke

_________________________________________________________________
På MSN hittar du det roliga, intressanta och användbara på internet: 
http://www.msn.se

Re: [Webwork-user] Why I like WebWork

[Marc L. <dev...@lo...>]

>> ps. and instead of EJB we're using AOP which makes the app really
>> ultracool, but that's another story..

> AOP ???

sorry, didnt read your explanation in time...


---
greetings from
Marc Logemann
Homebase @ www.logemann.info

RE: [Webwork-user] Why I like WebWork

[WATKIN-JONES,ADAM (HP-UnitedKingdom,ex1) <ada...@hp...>]

Hi!

I'm delurking to ask what is surely a daft question but here goes:  if =
not
AspectJ, then what AOP toolkit are you using?

(Obvious answer: having super programming-chops, you've written an AOP =
kit
yourself!  In which case, is this something you may put into the public
domain!?)

Just curious.

Thanks,
Adam


-----Original Message-----
From: Rickard

Christoph Kiehl wrote:
>>ps. and instead of EJB we're using AOP which makes the app really=20
>>ultracool, but that's another story..
>=20
> What is AOP? ;)

Aspect Oriented Programming. The "next big thing" as they say. Been=20
using it for a couple of weeks now (no, I'm not using AspectJ) and I=20
never ever want to go back to plain old OOP again :-))) I just love the =

flexibility I get from being able to "tack on" new interfaces and call=20
interceptors to objects without redesigning my whole app. It rocks. :-)

/Rickard

--=20
Rickard =D6berg

Re: [Webwork-user] Why I like WebWork

[Marc L. <dev...@lo...>]

> ps. and instead of EJB we're using AOP which makes the app really
> ultracool, but that's another story..

AOP ???


---
greetings from
Marc Logemann
Homebase @ www.logemann.info

Re: [Webwork-user] Why I like WebWork

[Rickard <ri...@dr...>]

Christoph Kiehl wrote:
>>ps. and instead of EJB we're using AOP which makes the app really=20
>>ultracool, but that's another story..
>=20
> What is AOP? ;)

Aspect Oriented Programming. The "next big thing" as they say. Been=20
using it for a couple of weeks now (no, I'm not using AspectJ) and I=20
never ever want to go back to plain old OOP again :-))) I just love the=20
flexibility I get from being able to "tack on" new interfaces and call=20
interceptors to objects without redesigning my whole app. It rocks. :-)

/Rickard

--=20
Rickard =D6berg

Re: [Webwork-user] Why I like WebWork

[Christoph K. <ki...@su...>]

Hi Rickard,

> ps. and instead of EJB we're using AOP which makes the app really 
> ultracool, but that's another story..

What is AOP? ;)

Greetings
Christph

Re: [Webwork-user] Session (Map) contents.

[Rickard <ri...@dr...>]

Toby Hede wrote:
> The rules will still apply.
>=20
> I might be way off here, but it is my understanding that implementing t=
he
> SessionAware interface simply allows the ActionContext to pass in the
> HTTPSession Map for access.

That is precisely correct.

/Rickard

--=20
Rickard =D6berg

Re: [Webwork-user] Why I like WebWork

[Rickard <ri...@dr...>]

Mike Cannon-Brookes wrote:
> Ok - so if you're on this list you probably don't need convincing, but =
I
> should post it anyway :)
>=20
> http://radio.weblogs.com/0107789/stories/2002/07/09/whyILikeWebwork.htm=
l

Good stuff! Really well written, and actually quite balanced :-)

After a long break from the world of J2EE, I'm getting into the fray=20
again, and yesterday had the pleasure of writing an RMI-stack on top of=20
WebWork (using the ClientDispatcher as transport), since we need to be=20
able to call the server from an applet through firewalls. The whole=20
thing was written in 2 hours, and was made out of three classes:
1) a RemoteServiceFactory that uses the Proxy API to create remote=20
proxies (of ANY interface, that does not need to extend Remote or use=20
RemoteExceptions).
2) Proxy InvocationHandler to handle calls on the client which delegates =
to
3) a RemoteAction that carries the invocation through the=20
ClientDispatcher, executes it on the server, and then carries the result=20
back up through 2)

That was that. I'm sure it will be extended in the future, but this=20
alone allowed remote calls from an applet into the server. Pretty neat.=20
And since webworkclient.jar is only 14k it's pretty small too.

I'll probably be extending the ClientDispatcher stuff rather soon, since=20
for our project we need semi-asynchronous events back to the applet=20
while a call is being executed (for progress bars and such). Since all=20
communication is done through the CD this becomes trivial to implement :-=
)

Me like it.

/Rickard

ps. and instead of EJB we're using AOP which makes the app really=20
ultracool, but that's another story..

--=20
Rickard =D6berg