date:20070726

[s1] security filter for EventDispatchAction

2007-07-26 Thread Strachan, Paul

Hi,

 

For security/authorisation we use a servlet filter which checks the url
against our security database.  We've recently upgraded to Struts 1.2.9
and tried using EventDispatchAction, but the problem is the filter does
not know which event to secure against (as the event name is arbitory
value and only struts knows about it in the mapping).

 

The problem with using EventDispatchAction is we don't know the event
parameter name is (ie what method Struts is going to execute) - to check
if the user has access to this action/event/method.

 

I think I will need to access the struts-config (module relative) and
EventDispatch logic from the Filter in order to deduce the current
event.  Does this sound feasible and is there any good example to do
this.

 

Thanks,

Paul

 

Note - our approach works fine for urls mapped with
MappingDispatchAction and DispatchAction (eg for the latter we know what
the dispatch param name is)


**
This message is intended for the addressee named and may contain
privileged information or confidential information or both. If you
are not the intended recipient please delete it and notify the sender.
**

Re: S2 + REST urls

2007-07-26 Thread Aram Mkhitaryan

First of all, put that constants in struts.properties file next to
struts.xml
there are some problems with constants defined in struts.xml, some of them
does not work correctly

Then, you can create your namespace and mappings for images and csses, this
will add security,
and you will be able to hide real resource names

Also, to use restful urls you need only DefaultActionMapper, the other ones
are parameter automappers of restful urls, I do not use them

You can define your actions like this


  
  
  
  
  


Best,
Aram

Aram Mkhitaryan

52, 25 Lvovyan, Yerevan 375000, Armenia

Mobile: +374 91 518456
E-mail: [EMAIL PROTECTED]

Re: Chart generator servlet

2007-07-26 Thread Aram Mkhitaryan

I use jfreechart,

I'm generating the chart in the page's servlet (where the html is
generated),
I'm putting the image's url so that it is mapped to the chart viewer
servlet.

See examples of jfreechart, it's too simple.

Best,
Aram

Aram Mkhitaryan

52, 25 Lvovyan, Yerevan 375000, Armenia

Mobile: +374 91 518456
E-mail: [EMAIL PROTECTED]

Re: Is Struts still a better choice over JSF as on today ?

2007-07-26 Thread Frank W. Zammetti

souravm wrote:
Regarding going for JSF due to componentization, I'm again not sure what additional componentizations JSF does compared to struts.

JSF is inherently a component-based framework, meaning you aren't really
thinking in terms of pages, your thinking in terms of components of a
"view". Struts doesn't really offer this, although S2 gets closer to it
in many ways (and yes, there's some JSF support in S2 is you want it,
although I'm not too familiar with it myself).

> Apart from the fact that JSF does not need a layer like Action
Classes, all other components (validator, managed bean, html tag libs
etc.) are already there in Struts. May be I'm missing something here.

I think your looking at the pieces and comparing them rather than
looking at the overarching paradigm of one framework vs. the other. The
distinction has been diminished a bit with S2, but it's still there.

A component-based approach means your looking at individual elements
that make up a a particular view and thinking in terms of the
interactions the user can have with each. You don't think in terms of
state transitions, you think in terms of events.

With Struts, it's about state transitions. The user submits a form and
transitions to a new application state entirely. I'm throwing AJAX out
of this for the moment of course :)

Also, I'm yet to appreciate the real value add event handling mechanism of JSF can bring in a web application scenario.

It's the ease, in theory, that it provides, and the fact that your
inherently thinking along those lines, rather than shoe-horning it in.
That's the value-add IML (in theory!)

> Especially given the fact that all those events (associated with a
single http request) would be fired only in a sequential way at server
side.

I'm not quite sure what you mean by that...

>
I really cannot think a usage scenario of multiple event handler feature
of JSF. Even in case of RIAs, I believe what is more required feature is
dynamic loading of part of a html page (which is currently the space
where AJAX is becoming popular). So any further explanation/example on
how you have found this feature of JSF to be useful for RIAs would be
helpful for me to understand your point.

It's not just about partial page loads, although that's clearly a big
part of it. As I was describing before, it's more about the approach to
developing the application.

Are you familiar at all with Visual Basic? If so, let me try and make
this analogy... working with JSF is more akin to developing in VB than
in Struts because your creating a given view that is a collection of
components, and then determining what events each component can trigger,
and coding for them. When you write a VB app, you aren't typically
thinking in terms of this form leads to that form which leads to another
form (unless your talking a wizard flow, but that's a specialized case).
With Struts, it's always about a transition from one view to another,
from one form to another in VB, triggered by some user input (again,
putting AJAX aside for the moment). The VB paradigm, is frankly more
logical to most developers. It's more like Swing too if you think about it.

Now *with* AJAX in the mix, and with client-side component libraries
coming fast and furious, a lot of what made JSF potentially attractive
has, again IMO, been significantly diminished. People have realized
that you don't need the full JSF stack, so to speak, and you can do
components without JSF too, so maybe it's not as valuable. Now, JSF
still provides value there because it gives you a standardized component
model, something that is sorely lacking in client-side component
libraries these days (i.e., Dojo widgets and YUI widgets and APT widgets
aren't generally compatible, and certainly aren't designed to some
common pattern).

That's kind of what's happened in Struts land too... there's been a bit
of a melding of the component paradigm and the non-component paradigm,
largely with AJAX as the catalyst.

Regards,
Sourav

Frank

--
Frank W. Zammetti
Founder and Chief Software Architect
Omnytex Technologies
http://www.omnytex.com
AIM/Yahoo: fzammetti
MSN: [EMAIL PROTECTED]
Author of "Practical Ajax Projects With Java Technology"
(2006, Apress, ISBN 1-59059-695-1)
and "JavaScript, DOM Scripting and Ajax Projects"
(2007, Apress, ISBN 1-59059-816-4)
Java Web Parts - http://javawebparts.sourceforge.net
Supplying the wheel, so you don't have to reinvent it!

72 matches

Mail list logo