You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@struts.apache.org by Rajesh M Vasudevan <ra...@neosoftsolutions.com> on 2003/09/27 08:24:53 UTC
[Question] Image path - Best way?
Hi
What is the best way to give image paths in JSP pages? I see that an image
path given in a certain way works for .jsp files, but the same path fails
for pages loaded through a .do and vice versa.
Is there a standard way that struts instructs by which images can be defined
in a resource configuration file and refer to them in the jsp pages as
resource strings, just like application resources? OR Is there a way to
refer to an image which works well for both .do or .jsp.
Please advise..
Regards,
Rajesh
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-user-help@jakarta.apache.org
Re: [Question] Image path - Best way?
Posted by James Mitchell <jm...@apache.org>.
Are you talking about something like this?
<bean:define id="myImg">
<bean:message key="my.img"/>
</bean:define>
<html:img page="<%=myImg%>"/>
...where you have something like this in your .properties file
my.img = /images/logo.gif
--
James Mitchell
Software Engineer / Struts Evangelist
http://www.struts-atlanta.org
678.910.8017
770.822.3359
AIM:jmitchtx
----- Original Message -----
From: "Rajesh M Vasudevan" <ra...@neosoftsolutions.com>
To: "Struts Users Mailing List" <st...@jakarta.apache.org>
Sent: Saturday, September 27, 2003 2:32 AM
Subject: Re: [Question] Image path - Best way?
> Hi guys,
>
> I tried the following, and it seems to work good:
> <img src="<%=request.getContextPath()%>/images/leiste_oben.jpg"
width="430"
> height="80" border="0" alt="">
>
> Is this the right way? Is there a way to specify it as a Resource? Can
you
> give me a tutorial link of how to do that..
>
> Thanks
> Rajesh
>
> > Hi
> >
> > What is the best way to give image paths in JSP pages? I see that an
> image
> > path given in a certain way works for .jsp files, but the same path
fails
> > for pages loaded through a .do and vice versa.
> >
> > Is there a standard way that struts instructs by which images can be
> defined
> > in a resource configuration file and refer to them in the jsp pages as
> > resource strings, just like application resources? OR Is there a way to
> > refer to an image which works well for both .do or .jsp.
> >
> > Please advise..
> >
> > Regards,
> > Rajesh
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: struts-user-help@jakarta.apache.org
> >
> >
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: struts-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-user-help@jakarta.apache.org
Re: [Question] Problem with bean:include.
Posted by Adam L <ad...@hotmail.com>.
Where's the connection between 'Head', 'headTemplate' and 'headTemp' ?
Perhaps it's the mismatch of names that's causing grief...
----- Original Message -----
From: "Rajesh M Vasudevan" <ra...@neosoftsolutions.com>
To: "Struts Users Mailing List" <st...@jakarta.apache.org>
Sent: Sunday, September 28, 2003 7:33 AM
Subject: [Question] Problem with bean:include.
> Hi,
>
> I am using the following code for including another jsp
> <bean:include id="Head" forward="headTemplate"/>
> This is working fine when I load a file with .jsp extension. But, when a
> jsp page loads following an action mapping, it fails to load. No
> exceptions, but the page doesnt appear.
>
> I've the following in the struts-config.xml
> <global-forwards>
> .................
> <forward name="headTemp" path="/pages/head.jsp"/>
> </global-forwards>
>
> Is there something I missed?
>
> Thanks for your help,
> Regards
> Rajesh
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: struts-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-user-help@jakarta.apache.org
[Question] Problem with bean:include.
Posted by Rajesh M Vasudevan <ra...@neosoftsolutions.com>.
Hi,
I am using the following code for including another jsp
<bean:include id="Head" forward="headTemplate"/>
This is working fine when I load a file with .jsp extension. But, when a
jsp page loads following an action mapping, it fails to load. No
exceptions, but the page doesnt appear.
I've the following in the struts-config.xml
<global-forwards>
.................
<forward name="headTemp" path="/pages/head.jsp"/>
</global-forwards>
Is there something I missed?
Thanks for your help,
Regards
Rajesh
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-user-help@jakarta.apache.org
Re: [Question] Image path - Best way?
Posted by Max Cooper <ma...@maxcooper.com>.
Struts has a tag that will put the context path on the front of the src URL
for you. Here's an example:
<html:img page="/images/leiste_oben.jpg" width="430" height="80" border="0"
alt=""/>
If you want to reserve the option to internationalize what image gets
displayed, Struts has good support for that, too. For instance, if you have
a button image with some text on it, and you want to be able to show
different images for different languages, you can put the image path in the
ApplicationResources.properties file and use something like this:
<html:img pageKey="button.clickMe.src"/>
You can also use the altKey attribute of the <html:img> tag to
internationalize the ALT, um, thingy.
<html:img pageKey="button.clickMe.src" altKey="button.clickMe.alt"/>
In your base ApplicationResources.properties file, you might have something
like this:
button.clickMe.src=/images/button_clickMe.jpg
button.clickMe.alt=Click Me
You can override these values for other languages in locale-specific
versions of the ApplicationResources.properties file.
One thing to be careful of with specifying images this way is that if you
set the size in the <html:img> tag (which is a good idea to speed rendering
performance in the browser), make sure that all the images for a given
button match the size that is specified.
They don't exist now, but it might be useful if heightKey and widthKey
attributes were added to the <html:img> tag to allow those to be looked up
in the properties file as well. That way you could specify different sizes
for the images if they happen to be different for different locales.
For complete documentation, see the online docs for <html:img>, here:
http://jakarta.apache.org/struts/userGuide/struts-html.html#img
-Max
----- Original Message -----
From: "Rajesh M Vasudevan" <ra...@neosoftsolutions.com>
To: "Struts Users Mailing List" <st...@jakarta.apache.org>
Sent: Friday, September 26, 2003 11:32 PM
Subject: Re: [Question] Image path - Best way?
> Hi guys,
>
> I tried the following, and it seems to work good:
> <img src="<%=request.getContextPath()%>/images/leiste_oben.jpg"
width="430"
> height="80" border="0" alt="">
>
> Is this the right way? Is there a way to specify it as a Resource? Can
you
> give me a tutorial link of how to do that..
>
> Thanks
> Rajesh
>
> > Hi
> >
> > What is the best way to give image paths in JSP pages? I see that an
> image
> > path given in a certain way works for .jsp files, but the same path
fails
> > for pages loaded through a .do and vice versa.
> >
> > Is there a standard way that struts instructs by which images can be
> defined
> > in a resource configuration file and refer to them in the jsp pages as
> > resource strings, just like application resources? OR Is there a way to
> > refer to an image which works well for both .do or .jsp.
> >
> > Please advise..
> >
> > Regards,
> > Rajesh
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: struts-user-help@jakarta.apache.org
> >
> >
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: struts-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-user-help@jakarta.apache.org
Re: Editorial on Struts vs JSF
Posted by James Mitchell <jm...@apache.org>.
----- Original Message -----
From: "Vic Cekvenic" <ce...@basebeans.com>
<snip/>
> Feel free to read the JSF spec and form an opinion for yourself.
+1
>
> .V
>
--
James Mitchell
Software Engineer / Struts Evangelist
http://www.struts-atlanta.org
678.910.8017
770.822.3359
AIM:jmitchtx
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-user-help@jakarta.apache.org
Re: Editorial on Struts vs JSF
Posted by Vic Cekvenic <ce...@basebeans.com>.
Many MVC frameworks market themselves with "we are like Struts, only
better", as does JSF.
-RI JSF is not open source, so if rendering does not emit HTML that
supports your/browser needs,...
-Also JSF implies that Java developers are doing more UI, something that
a Graphic Artist does for my clients. (I see JSF similar to JSP version
of ECS)
- The links imply that ASF will have an open source JSF... , I can't see it.
- I personally am not clear on what JSF licensing will be until it is
released.
- Not sure what support for JavaScript will be, until it is released.
To me ... people that use/like EJB will use JSF with it. (they are both
heavy; ... possibly on the way to .NET, since I see this combo inferior
to C#/DataGrids)
People that use/like iBatis/Hibrenate DAO types(light), will use Struts.
(and likely to stay on J2EE, since I see this combo better than .NET.
Displaytag, calendar tag, Struts Menu, and other tags are real nice and
proven to me)
I see JSF and Struts as opposite. One is heavy/commercial with IP owned
by Sun wanabe, the other is open/light, proven/popular standard. KISS
anyone?
I am hedging my bet w/Flash DataGrid, since it supports both .NET and
J2EE (FYI: MacroMedia pulled out of JSF).
Of course wait and see could be a good idea as well, maybe JSF v2 gets
proven in production, but people that do JSF now, IMO will get burned.
Even if JSF does have some market share... Struts is much to popular,
and it is open source (so as long as you have source) it can't go away.
So my prediction is Struts all the way.
And future UI would be client side scripting (Flash/.js), XUL and XForms
( and very little people using JSF to do same)
It remains to be seen if Craig can persuade his comity of vendors vs
what WinterFeld, Turner, Husted, Marting, Cedric, et all did, and
continue to do. Look at what is coming up for Struts 1.2 and 2.0.
Feel free to read the JSF spec and form an opinion for yourself.
.V
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-user-help@jakarta.apache.org
Re: [Question] : Close popup after Action has exited... -- SOLVED
Posted by Todor Sergueev Petkov <t....@basalmed.uio.no>.
Thanks a lot - the redirect to a page and onload=window.close() works
very well..
Raphaël di Cicco wrote:
> forward to a second page that self closes
> <BODY onload="javascript:window.close();">
>
> ----- Original Message -----
> From: "khote" <kh...@mminternet.com>
> To: "Struts Users Mailing List" <st...@jakarta.apache.org>
> Sent: Wednesday, October 01, 2003 12:38 PM
> Subject: Re: [Question] : Close popup after Action has exited...
>
>
>
>>in your <form .... onSubmit="self.close();"
>>
>>or document.window.close() or try variations on that. Sometimes the
>
> browser
>
>>will complain about, I'm not sure which one gets you past that.
>>
>>
>>----- Original Message -----
>>From: "Todor Sergueev Petkov" <t....@basalmed.uio.no>
>>To: "Struts Users Mailing List" <st...@jakarta.apache.org>
>>Sent: Wednesday, October 01, 2003 3:37 AM
>>Subject: [Question] : Close popup after Action has exited...
>>
>>
>>
>>>Hi,
>>>Does somebody know how I can close a popup window for which I have
>>>ActionForms and Action when some method in the action has performed its
>>>job ( exited )?
>>>Thanks
>>>
>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
>>>For additional commands, e-mail: struts-user-help@jakarta.apache.org
>>>
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
>>For additional commands, e-mail: struts-user-help@jakarta.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: struts-user-help@jakarta.apache.org
>
>
> .
>
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-user-help@jakarta.apache.org
Re: [Question] : Close popup after Action has exited...
Posted by Raphaël di Cicco <ra...@atosorigin.com>.
forward to a second page that self closes
<BODY onload="javascript:window.close();">
----- Original Message -----
From: "khote" <kh...@mminternet.com>
To: "Struts Users Mailing List" <st...@jakarta.apache.org>
Sent: Wednesday, October 01, 2003 12:38 PM
Subject: Re: [Question] : Close popup after Action has exited...
> in your <form .... onSubmit="self.close();"
>
> or document.window.close() or try variations on that. Sometimes the
browser
> will complain about, I'm not sure which one gets you past that.
>
>
> ----- Original Message -----
> From: "Todor Sergueev Petkov" <t....@basalmed.uio.no>
> To: "Struts Users Mailing List" <st...@jakarta.apache.org>
> Sent: Wednesday, October 01, 2003 3:37 AM
> Subject: [Question] : Close popup after Action has exited...
>
>
> > Hi,
> > Does somebody know how I can close a popup window for which I have
> > ActionForms and Action when some method in the action has performed its
> > job ( exited )?
> > Thanks
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: struts-user-help@jakarta.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: struts-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-user-help@jakarta.apache.org
Re: Editorial on Struts' Long Term Future
Posted by BaTien Duong <ba...@dbgroups.com>.
Craig R. McClanahan wrote:
> Yep. To have Struts take that long to become "legacy" is actually a
> compliment to how well it addresses the need area it went after. To
> have it become the underlying knowledge base of the experts building
> the "standardized" version of the technology is a compliment to the
> original developers being pretty much on the right track.
>
> Yet, the problem that John addresses here (also known as "The
> Innovator's Dilemna") is very real. You're told to go build
> something, and put it up on the web yesterday. It's going to be a
> mission critical for your company, and will itself have a fairly long
> shelf life, so you want to make sure that the technologies you base
> your app on are also going to be around. You look at the available
> standards-based technologies, and don't see what you need. So, what
> do you do?
>
> Open source developers (at least the good ones) tend to be pretty
> innovative, and that was certainly the case with Struts folks (yes,
> that includes me, and I'm very proud of what my little brainchild has
> grown into :-). It is not unusual to find that there is an open
> source package out there. But, is that package going to be around for
> the lifetime of my own app?
>
> Or, to put it another way, how many open source projects are hosted at
> SourceForge? How many of them have more than a couple of developers
> playing around in their spare time? How many of them have been
> downloaded even 100 times (Struts gets ~75,000 downloads per month
> nowdays)?
>
> I would submit that the supporting ecology around the technologies you
> choose (be they open source or not) is likely to be more critical to
> your success than the particular technical features of the package.
> It was certainly critical to some pretty large scale companies, and
> conservative industries, that have adopted Struts quite widely.
>
> Yet, it takes a while for that ecology to grow. And, there's no
> guarantees that it will *ever* happen. And, while the ecology is
> growing, the technology at the base can't evolve quite as quickly as
> it could before (ask all the guys who wrote books on the "moving
> target" that was Struts 1.1 :-).
>
> It's an interesting balancing act.
The direction of Struts-2 with Commons Chain proves that it can survive
the test of time through innovation and specialize in what it does best.
Struts committers have that clear vision and focus. I have no doubt that
we can continue to enjoy the fruits of Struts community efforts.
>
>> JSF scratches many of the same itches as struts, only better, and
>> given that
>> Craig is spec lead for JSF thats hardly a coincidence. Perhaps we could
>> consider struts the practice run? ;-)
>>
>>
> :-)
>
>> Craig & co. say that there will be a future for struts in the JSF
>> generation, but Im not sure I fully grok what that future is yet
>> (havent had
>> a chance to play with the jsf struts integrated stuff yet) but at the
>> least
>> it should involve an upgrade path for existing struts stuff?
>>
>>
> Keep in mind that the existing struts-faces integration library isn't
> finished yet (since JavaServer Faces isn't finished yet). But it will
> be.
>
> To the broader question, I would definitely say there is a future for
> Struts. Here's a quick summary of some things on my mind:
>
> * Part of the ecology of a successful open source project
> is staying up with the times, offerring new things to your
> existing customers. After all, there are many thousands of
> Struts based applications aready in existence -- and nobody
> is going to rewrite them all in the next couple of days, or even
> the next couple of years. Therefore, Struts needs to continue
> to support its existing features and functions, and add new ones.
>
> * Particular areas of future growth I'm interested in (other developers
> have their own thoughts as well):
>
> - Enable existing Struts-based applications to utilize new view
> technologies (like JavaServer Faces) with zero changes to their
> back-end business logic (isn't that one of the things we all like
> about MVC type designs? :-).
>
> - Make Struts equally useful in both a servlet and portlet (JSR-168)
> environment.
>
> - Refactor the insides of Struts so that the basic principles of
> "separation of concerns" can be used for "scripting" your back end
> business logic, interacting with XML data sources and outputs,
> and so on.
These are some key features to make Struts survive the test of time.
BaTien
DBGROUPS
>
> If we were just going to stay where we are, I'd be worried about the
> future of Struts (although, even if all development stopped tomorrow,
> there's too many people using it today for such a vacuum to exist for
> very long -- someone else would take up the gauntlet).
>
> Sadly, I don't have time at the moment to comment further ... maybe
> later, after putting in some "day job" hours :-).
>
> Craig
>
>> I
>
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-user-help@jakarta.apache.org
Re: Editorial on Struts' Long Term Future
Posted by "Craig R. McClanahan" <cr...@apache.org>.
Andrew Hill wrote:
>Yep. Quite interesting.
>
>Sorry if its a bit rambling - dont have time to edit it - but heres my 2
>cents worth:
>
>The article doesnt mention it but Scioworks is the company behind Camino , a
>powerful RAD tool for struts so its a good bet to say that he certainly
>knows the technology and the area quite well (unlike many commentators).
>
>
Trust me ... he does :-).
>Id have to say I agree with the opinion to a certain extent - though in my
>view 3 years is a very long time in IT! ;-)
>
>
Yep. To have Struts take that long to become "legacy" is actually a
compliment to how well it addresses the need area it went after. To
have it become the underlying knowledge base of the experts building the
"standardized" version of the technology is a compliment to the original
developers being pretty much on the right track.
Yet, the problem that John addresses here (also known as "The
Innovator's Dilemna") is very real. You're told to go build something,
and put it up on the web yesterday. It's going to be a mission critical
for your company, and will itself have a fairly long shelf life, so you
want to make sure that the technologies you base your app on are also
going to be around. You look at the available standards-based
technologies, and don't see what you need. So, what do you do?
Open source developers (at least the good ones) tend to be pretty
innovative, and that was certainly the case with Struts folks (yes, that
includes me, and I'm very proud of what my little brainchild has grown
into :-). It is not unusual to find that there is an open source
package out there. But, is that package going to be around for the
lifetime of my own app?
Or, to put it another way, how many open source projects are hosted at
SourceForge? How many of them have more than a couple of developers
playing around in their spare time? How many of them have been
downloaded even 100 times (Struts gets ~75,000 downloads per month nowdays)?
I would submit that the supporting ecology around the technologies you
choose (be they open source or not) is likely to be more critical to
your success than the particular technical features of the package. It
was certainly critical to some pretty large scale companies, and
conservative industries, that have adopted Struts quite widely.
Yet, it takes a while for that ecology to grow. And, there's no
guarantees that it will *ever* happen. And, while the ecology is
growing, the technology at the base can't evolve quite as quickly as it
could before (ask all the guys who wrote books on the "moving target"
that was Struts 1.1 :-).
It's an interesting balancing act.
>JSF scratches many of the same itches as struts, only better, and given that
>Craig is spec lead for JSF thats hardly a coincidence. Perhaps we could
>consider struts the practice run? ;-)
>
>
:-)
>Craig & co. say that there will be a future for struts in the JSF
>generation, but Im not sure I fully grok what that future is yet (havent had
>a chance to play with the jsf struts integrated stuff yet) but at the least
>it should involve an upgrade path for existing struts stuff?
>
>
Keep in mind that the existing struts-faces integration library isn't
finished yet (since JavaServer Faces isn't finished yet). But it will be.
To the broader question, I would definitely say there is a future for
Struts. Here's a quick summary of some things on my mind:
* Part of the ecology of a successful open source project
is staying up with the times, offerring new things to your
existing customers. After all, there are many thousands of
Struts based applications aready in existence -- and nobody
is going to rewrite them all in the next couple of days, or even
the next couple of years. Therefore, Struts needs to continue
to support its existing features and functions, and add new ones.
* Particular areas of future growth I'm interested in (other developers
have their own thoughts as well):
- Enable existing Struts-based applications to utilize new view
technologies (like JavaServer Faces) with zero changes to their
back-end business logic (isn't that one of the things we all like
about MVC type designs? :-).
- Make Struts equally useful in both a servlet and portlet (JSR-168)
environment.
- Refactor the insides of Struts so that the basic principles of
"separation of concerns" can be used for "scripting" your back end
business logic, interacting with XML data sources and outputs,
and so on.
If we were just going to stay where we are, I'd be worried about the
future of Struts (although, even if all development stopped tomorrow,
there's too many people using it today for such a vacuum to exist for
very long -- someone else would take up the gauntlet).
Sadly, I don't have time at the moment to comment further ... maybe
later, after putting in some "day job" hours :-).
Craig
>I dont really see what the fuss about 'protecting investment' is - its not
>like struts is rocket science to work with and unlike commercial products
>you've always got the source to look at if the docs arent clear enough! If
>the product your maintaining uses struts its still going to be a hell of a
>lot easier to maintain than one that went with a model 1 approach. After
>all, when struts was created there simply wasnt a suitable webapp framework
>standard to plug the gap between the low level servlet api stuff and higher
>level application oriented patterns, and if we extrapolate from this to
>other new areas where opensource is paving the way, are we to say that
>managers shouldnt use such opensource initiatives because they dont comply
>to standards that have yet to be drafted? What then? Homebrew frameworks? -
>if its early in the technology these may be the best way of meeting your
>needs while opensource efforts mature - but usually thats not the case.
>Ignore the new area till someone comes up with a standard framework? Not
>really an option given commericial pressures.
>
>At the end of the day its a case of going with whatever framework is
>available and choosing the one that will cost you the least and give you the
>most mileage. In hindsight for J2EE webapps that would be struts, and even
>right this second it would still be struts. JSF isnt ready for general use
>yet - so unless you want to delay your project till it is what are you going
>to do?
>
>The answer of course is to choose a framework that will give you the easiest
>upgrade path as new standards come along. A framework that quickly moves to
>support standards as they emerge.
>In the webapp arena this is of course struts - and in the past the upgrade
>path has always been there - for jstl there were both the struts-el library
>and of course the fact the jstl and struts play very nice with each other.
>With JSF I believe that whats been done to integrate struts and JSF will
>provide a good path. The next (or soon after) version of struts will I
>gather also play nice with the portlet spec, etc...
>
>Basically what the article is saying is that these are the issues that
>managers need to consider carefully. Its certainly not saying dont go with
>struts/opensource, but rather saying that one day they may be obsolete - but
>its not like theres a real alternative - so pick the one that looks like
>its going to cost you the least in the long term!
>
>To quote:
><snip>
>Am I suggesting shunning those open-source projects? Not at all. These are
>solutions you can deliver now, and the lack of support may happen in the
>future. I believe the value gained from using these open-source technologies
>outweighs the risk.
></snip>
>
>
>
>-----Original Message-----
>From: jlord@equiplease.com [mailto:jlord@equiplease.com]
>Sent: Wednesday, 1 October 2003 22:09
>To: Struts Users Mailing List
>Subject: Editorial on Struts' Long Term Future
>
>
>
>
>
>
>
>You may find this editorial on J2EE/JSF/Struts interesting.
>http://www.sdtimes.com/opinions/guestview_087.htm
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: struts-user-help@jakarta.apache.org
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: struts-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-user-help@jakarta.apache.org
RE: Editorial on Struts' Long Term Future
Posted by Andrew Hill <an...@gridnode.com>.
Yep. Quite interesting.
Sorry if its a bit rambling - dont have time to edit it - but heres my 2
cents worth:
The article doesnt mention it but Scioworks is the company behind Camino , a
powerful RAD tool for struts so its a good bet to say that he certainly
knows the technology and the area quite well (unlike many commentators).
Id have to say I agree with the opinion to a certain extent - though in my
view 3 years is a very long time in IT! ;-)
JSF scratches many of the same itches as struts, only better, and given that
Craig is spec lead for JSF thats hardly a coincidence. Perhaps we could
consider struts the practice run? ;-)
Craig & co. say that there will be a future for struts in the JSF
generation, but Im not sure I fully grok what that future is yet (havent had
a chance to play with the jsf struts integrated stuff yet) but at the least
it should involve an upgrade path for existing struts stuff?
I dont really see what the fuss about 'protecting investment' is - its not
like struts is rocket science to work with and unlike commercial products
you've always got the source to look at if the docs arent clear enough! If
the product your maintaining uses struts its still going to be a hell of a
lot easier to maintain than one that went with a model 1 approach. After
all, when struts was created there simply wasnt a suitable webapp framework
standard to plug the gap between the low level servlet api stuff and higher
level application oriented patterns, and if we extrapolate from this to
other new areas where opensource is paving the way, are we to say that
managers shouldnt use such opensource initiatives because they dont comply
to standards that have yet to be drafted? What then? Homebrew frameworks? -
if its early in the technology these may be the best way of meeting your
needs while opensource efforts mature - but usually thats not the case.
Ignore the new area till someone comes up with a standard framework? Not
really an option given commericial pressures.
At the end of the day its a case of going with whatever framework is
available and choosing the one that will cost you the least and give you the
most mileage. In hindsight for J2EE webapps that would be struts, and even
right this second it would still be struts. JSF isnt ready for general use
yet - so unless you want to delay your project till it is what are you going
to do?
The answer of course is to choose a framework that will give you the easiest
upgrade path as new standards come along. A framework that quickly moves to
support standards as they emerge.
In the webapp arena this is of course struts - and in the past the upgrade
path has always been there - for jstl there were both the struts-el library
and of course the fact the jstl and struts play very nice with each other.
With JSF I believe that whats been done to integrate struts and JSF will
provide a good path. The next (or soon after) version of struts will I
gather also play nice with the portlet spec, etc...
Basically what the article is saying is that these are the issues that
managers need to consider carefully. Its certainly not saying dont go with
struts/opensource, but rather saying that one day they may be obsolete - but
its not like theres a real alternative - so pick the one that looks like
its going to cost you the least in the long term!
To quote:
<snip>
Am I suggesting shunning those open-source projects? Not at all. These are
solutions you can deliver now, and the lack of support may happen in the
future. I believe the value gained from using these open-source technologies
outweighs the risk.
</snip>
-----Original Message-----
From: jlord@equiplease.com [mailto:jlord@equiplease.com]
Sent: Wednesday, 1 October 2003 22:09
To: Struts Users Mailing List
Subject: Editorial on Struts' Long Term Future
You may find this editorial on J2EE/JSF/Struts interesting.
http://www.sdtimes.com/opinions/guestview_087.htm
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-user-help@jakarta.apache.org
Editorial on Struts' Long Term Future
Posted by jl...@equiplease.com.
You may find this editorial on J2EE/JSF/Struts interesting.
http://www.sdtimes.com/opinions/guestview_087.htm
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-user-help@jakarta.apache.org
Re: [Question] : Close popup after Action has exited...
Posted by khote <kh...@mminternet.com>.
in your <form .... onSubmit="self.close();"
or document.window.close() or try variations on that. Sometimes the browser
will complain about, I'm not sure which one gets you past that.
----- Original Message -----
From: "Todor Sergueev Petkov" <t....@basalmed.uio.no>
To: "Struts Users Mailing List" <st...@jakarta.apache.org>
Sent: Wednesday, October 01, 2003 3:37 AM
Subject: [Question] : Close popup after Action has exited...
> Hi,
> Does somebody know how I can close a popup window for which I have
> ActionForms and Action when some method in the action has performed its
> job ( exited )?
> Thanks
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: struts-user-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-user-help@jakarta.apache.org
RE: [Question] : Close popup after Action has exited...
Posted by Andrew Hill <an...@gridnode.com>.
I do this by having the action forward to some html page with a little
javascript that closes the window.
-----Original Message-----
From: Todor Sergueev Petkov [mailto:t.s.petkov@basalmed.uio.no]
Sent: Wednesday, 1 October 2003 18:38
To: Struts Users Mailing List
Subject: [Question] : Close popup after Action has exited...
Hi,
Does somebody know how I can close a popup window for which I have
ActionForms and Action when some method in the action has performed its
job ( exited )?
Thanks
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-user-help@jakarta.apache.org
[Question] : Close popup after Action has exited...
Posted by Todor Sergueev Petkov <t....@basalmed.uio.no>.
Hi,
Does somebody know how I can close a popup window for which I have
ActionForms and Action when some method in the action has performed its
job ( exited )?
Thanks
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-user-help@jakarta.apache.org
RE: [Question] Checkbox multi select problem.
Posted by hari_s <ha...@indonesian-aerospace.com>.
u can give index for every checkbox and then access the value of the
records according to this index.....
it's simple with <html-el:checkbox property="chk[${idx}]".......
-----Original Message-----
From: Rajesh M Vasudevan [mailto:rajesh@neosoftsolutions.com]
Sent: Saturday, September 27, 2003 11:45 PM
To: Struts Users Mailing List
Subject: Re: [Question] Checkbox multi select problem.
Hi,
Can you help me with this..
I want to pass the record ids selected by the user using a checkbox, to
the
Action Bean, when the page is submitted.
Check Unique Rec Ids
X 1000
X 1001
X 1002
X 1003
The number of rows is dynamic, as it depends on the number of rows
retrieved
from the database.
Please advise how to do this?
Thanks very much,
Rajesh
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-user-help@jakarta.apache.org
Re: [Question] Checkbox multi select problem.
Posted by Rajesh M Vasudevan <ra...@neosoftsolutions.com>.
Hi,
Can you help me with this..
I want to pass the record ids selected by the user using a checkbox, to the
Action Bean, when the page is submitted.
Check Unique Rec Ids
X 1000
X 1001
X 1002
X 1003
The number of rows is dynamic, as it depends on the number of rows retrieved
from the database.
Please advise how to do this?
Thanks very much,
Rajesh
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-user-help@jakarta.apache.org
Re: [Question] Image path - Best way?
Posted by Rajesh M Vasudevan <ra...@neosoftsolutions.com>.
Hi guys,
I tried the following, and it seems to work good:
<img src="<%=request.getContextPath()%>/images/leiste_oben.jpg" width="430"
height="80" border="0" alt="">
Is this the right way? Is there a way to specify it as a Resource? Can you
give me a tutorial link of how to do that..
Thanks
Rajesh
> Hi
>
> What is the best way to give image paths in JSP pages? I see that an
image
> path given in a certain way works for .jsp files, but the same path fails
> for pages loaded through a .do and vice versa.
>
> Is there a standard way that struts instructs by which images can be
defined
> in a resource configuration file and refer to them in the jsp pages as
> resource strings, just like application resources? OR Is there a way to
> refer to an image which works well for both .do or .jsp.
>
> Please advise..
>
> Regards,
> Rajesh
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: struts-user-help@jakarta.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-user-help@jakarta.apache.org