Re: Pls help on shopping cart App
A little off topic .. but does weblogic actually cost money? Sounds worse then Jrun to me. Anyway if I understood the problem, if weblogic struts which I assume is struts 1.0 doesn't support indexed=true (as struts 1.0 doesn't) then you have to put the index in youself logic:iterate id=item name=basketForm property=items indexId=index % java.lang.String item = item[+ java.lang.Integer.toString(index) +]; pageScope.setAttribute(item,item); % html:text name=%= item % property=price / /logic:iterate Again, perhaps I didn't understand the question, or perhaps things look more like this. logic:iterate id=item name=basketForm property=items indexId=index % java.lang.String price = price[+ java.lang.Integer.toString(index) +]; pageScope.setAttribute(price, price); % html:text property=%= price % / /logic:iterate I assume this is how matey boy fixed his weblogic struts problem. On 20 Mar 2004, at 06:06, Prakasan OK wrote: Hi, I am also facing the same problem.. Can u explain how you have solved it? On Thu, 18 Mar 2004 sougata wrote : No it is not like that since I am using weblogic's struts .Anyway I solved that.Thanks for your reply Sougata -Original Message- From: Mark Lowe [mailto:[EMAIL PROTECTED] Sent: Thursday, March 18, 2004 1:36 PM To: Struts Users Mailing List Subject: Re: Pls help on shopping cart App Do your html:text have the indexed=true attribute? On 18 Mar 2004, at 07:07, sougata wrote: Hi All, I have a shopping cart apps.When the user is buying items it is coming to mycart .In my mycart page I am showing all the products and the beside that I have a update button by which I can update the quantity of my each item which is in a textbox.I am follwing struts for that.My text box name is same in every row(say quantity).if its name is quantity in servlet I am getting a String array of quantity.But when I am coming to the same page its showing value=[Ljava.lang.String;@1765ae which is the reference of my string array.How to get the original value Pls let me know ASAP. Thanks Sougata - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Mapping Forward to new form
If you form is scoped to request you can also set redirect=true in
the action forward.
On 19 Mar 2004, at 20:03, Saul Q Yuan wrote:
You can call ((UserForm) form).reset() before forwarding.
Saul
-Original Message-
From: Ciaran Hanley [mailto:[EMAIL PROTECTED]
Sent: Friday, March 19, 2004 1:52 PM
To: Struts User Mailing List
Subject: Mapping Forward to new form
Hey,
I am adding user details to the DB through a form, on a
successful insert I would like to map forward to the same form.
The problem is when I use the action forward the form on the
forwarded page is filled with the details from the user I just added.
if(addUser((UserForm) form, request, response))
{
return (mapping.findForward(adduser));
}
I would like to map to a new blank form, how do I do this?
Thanks
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Recommend file upload progress bar
I have a requirement to display a progress bar while performing file uploads. I've found several frameworks that provide this functionality. However, can you recommend an existing *best* solution -- preferably off-the-shelf -- for use with Struts? Thanks, Frank - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
version 1.2
Hi, I am currently working with the 1.1, is there a good reason to move to 1.2? Is it going to be released sometime soon? Thanks, Erez
Job Posting
We are looking for Project Manager, Sr. Software Engineers and Graphic Designers for our Cochin operation. We will be providing best compansation of the industry. Project Manager Eligibility: 7-10 Years experience in which atleast 3 years pure project management experience, Fluency in communication, Well aware of different software life cycles, Able to handle around 25 people team with various projects. Working knowledge of UML Tools(ie. Rational Rose) Sound analyzing skill Sr. Software Engineer Eligibility: 3-6 Years of experience in J2EE technology and Java Script Well versed in Struts framework, Working experience of Weblogic or atleast one application server, Having exposure of Eclipse tool, Posses good knowledge of Oracle database Web Graphic Designer: Possess innovative nature, Working knowledge of Flash MX, Exposure to DHTML Interested candidate please apply to [EMAIL PROTECTED] will be scheduled soon. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
ValidatorForm.getServlet() == null !!
Hello, I need the ServletContext in one of my forms, which I'm trying to get with : getServlet().getServletContext() Unfortunately I get a NullpointerException, because the servlet is null. How could this be, is there a workaround ? Thx berger - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Recommend file upload progress bar
See the thread File-Upload: Progress-Bar that has been going on over the last few days. -Max - Original Message - From: Frank Burns [EMAIL PROTECTED] To: Struts Users Mailing List [EMAIL PROTECTED] Sent: Saturday, March 20, 2004 1:57 AM Subject: Recommend file upload progress bar I have a requirement to display a progress bar while performing file uploads. I've found several frameworks that provide this functionality. However, can you recommend an existing *best* solution -- preferably off-the-shelf -- for use with Struts? Thanks, Frank - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
base URL in Action
How can I get the base URL of the request (http://domainname) inside my Action class??? Dean Hoover - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: version 1.2
At 1:14 PM +0200 3/20/04, Erez Efrati wrote: Hi, I am currently working with the 1.1, is there a good reason to move to 1.2? Is it going to be released sometime soon? Struts 1.2.0 was released a few weeks ago using the new Tomcat-style version numbering. That means that a numbered release may or may not be considered a production quality release. There has not been a formal vote on the status of 1.2.0, but I think we'd cut another release rather than vote 1.2.0 as production-quality. If you're satisfied with Struts 1.1, you may as well stick with it. If you like to keep up with Struts while its evolving, you might be just as well off building from CVS Head as using Struts 1.2.0. That way you'd roll in recent bug fixes and be in a position to fix other bugs yourself if you find them (or just update from CVS and apply fixes and changes as they come in.) There aren't anywhere near the number of structural changes between 1.1 and 1.2 that there were between 1.0 and 1.1. Many deprecated members from 1.1 have been removed, so if you were ignoring the deprecation warnings all this time, you'll finally have to catch up. Also, if I recall correctly, there are some changes in the JSP tag libraries that may be hard to find until you compile the JSPs. Hope that helps, Joe -- Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com Imagine if every Thursday your shoes exploded if you tied them the usual way. This happens to us all the time with computers, and nobody thinks of complaining. -- Jef Raskin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
bean:message prints the KEY, not the MESSAGE
All I'm somewhat new to Struts. Using iPlanet 6.0.5, when a page is rendered, the message KEY is being printed, not the message, like so: This is what appears on the HTML page: ???en_US.enterprise.program.name.label??? What I want is this: Program Name This renders OK in Tomcat/Apache but not in iPlanet. I've checked the docs for iPlanet, and tried to set the correct language setings, but that's not working. Any ideas? Thanks in advance, Ken - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: bean:message prints the KEY, not the MESSAGE
I'm encouraged to see that you are still looking at Struts. As I understand it, there is a property that I set in my distribution that displays the KEY when it cannot find the corresponding value. IPlanet 6.05 does not look for the resource files in the traditional (Struts) location. What this is saying is that it cannot find the resource for the label. -Original Message- From: Newcomer, Kenneth Sent: Saturday, March 20, 2004 10:45 AM To: Struts Mailing List (E-mail) Subject: bean:message prints the KEY, not the MESSAGE All I'm somewhat new to Struts. Using iPlanet 6.0.5, when a page is rendered, the message KEY is being printed, not the message, like so: This is what appears on the HTML page: ???en_US.enterprise.program.name.label??? What I want is this: Program Name This renders OK in Tomcat/Apache but not in iPlanet. I've checked the docs for iPlanet, and tried to set the correct language setings, but that's not working. Any ideas? Thanks in advance, Ken - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: bean:message prints the KEY, not the MESSAGE
hi david, yes still looking at struts. i wonder if it's better to place a copy(*ouch!*) of the resource files in iPlanet's preferred location (which would be ...?), or try to get iPlanet to look in the actual location. -Original Message- From: Fowler, David Sent: Saturday, March 20, 2004 10:59 AM To: Struts Users Mailing List Subject: RE: bean:message prints the KEY, not the MESSAGE I'm encouraged to see that you are still looking at Struts. As I understand it, there is a property that I set in my distribution that displays the KEY when it cannot find the corresponding value. IPlanet 6.05 does not look for the resource files in the traditional (Struts) location. What this is saying is that it cannot find the resource for the label. -Original Message- From: Newcomer, Kenneth Sent: Saturday, March 20, 2004 10:45 AM To: Struts Mailing List (E-mail) Subject: bean:message prints the KEY, not the MESSAGE All I'm somewhat new to Struts. Using iPlanet 6.0.5, when a page is rendered, the message KEY is being printed, not the message, like so: This is what appears on the HTML page: ???en_US.enterprise.program.name.label??? What I want is this: Program Name This renders OK in Tomcat/Apache but not in iPlanet. I've checked the docs for iPlanet, and tried to set the correct language setings, but that's not working. Any ideas? Thanks in advance, Ken - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: bean:message prints the KEY, not the MESSAGE
I couldn't get it to recognize paths from WEB-INF. I just don't think their web container complies with the spec. As I recall, it uses the class path of the application, hence codebase. -Original Message- From: Newcomer, Kenneth Sent: Saturday, March 20, 2004 11:05 AM To: Struts Users Mailing List Subject: RE: bean:message prints the KEY, not the MESSAGE hi david, yes still looking at struts. i wonder if it's better to place a copy(*ouch!*) of the resource files in iPlanet's preferred location (which would be ...?), or try to get iPlanet to look in the actual location. -Original Message- From: Fowler, David Sent: Saturday, March 20, 2004 10:59 AM To: Struts Users Mailing List Subject: RE: bean:message prints the KEY, not the MESSAGE I'm encouraged to see that you are still looking at Struts. As I understand it, there is a property that I set in my distribution that displays the KEY when it cannot find the corresponding value. IPlanet 6.05 does not look for the resource files in the traditional (Struts) location. What this is saying is that it cannot find the resource for the label. -Original Message- From: Newcomer, Kenneth Sent: Saturday, March 20, 2004 10:45 AM To: Struts Mailing List (E-mail) Subject: bean:message prints the KEY, not the MESSAGE All I'm somewhat new to Struts. Using iPlanet 6.0.5, when a page is rendered, the message KEY is being printed, not the message, like so: This is what appears on the HTML page: ???en_US.enterprise.program.name.label??? What I want is this: Program Name This renders OK in Tomcat/Apache but not in iPlanet. I've checked the docs for iPlanet, and tried to set the correct language setings, but that's not working. Any ideas? Thanks in advance, Ken - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Security FIlter Framework
Hi, We have a web app implemneted in struts and deployed in Weblogic 7.0.We are planning to implement/consider filter frameworks for allowing role based access into the web app.(may be including the security filter framework.)Any suggestions on how this can be done and design decisons Role based access meaning different users could get access only to different set of pages and anot all-trying tos eparate authentication from jsp's (business logic out of jsp's and into the filter framewrok/back end authentication mechanism) Thanks in advance. Sam. Do you Yahoo!? Yahoo! Finance Tax Center - File online. File on time.
Re: security framework!!!
Hi, Any sample code implemenattions for the same Thanks! Adam Hardy [EMAIL PROTECTED] wrote: JAAS won't help you any more than what you've got in tomcat. The use of roles operates on exactly the same principles. It's got to, because it's not JAAS that has to deal with the roles, it's the container. JAAS allows multiple login modules to be combined in a pluggable fashion. Say a user/password with a smartcard and a biometric scanner. (perhaps Sun are trying to sell it to the Pentagon!) I'm not helping much here, but I still don't get what the problem is. I read the bit about 'entity-based not system-wide' responsibilities and I get that, but I don't see what the issue is. You're deciding permissions: you have a user's identity (ID or login name) and you have a user's roles. In this case, your superuser wants to 'become' a normal user, so that means to me that the superuser wants to see exactly what the user sees, and be able to do exactly what the user can do. That means the superuser must borrow the user's identity and roles. To borrow the identity, you use some sort of session attribute containing the 'currently effective ID' and to borrow the roles, well you don't, you just have them already because you're superuser. Perhaps a concrete example would help. I assume you are talking about deciding on the presence / absence of form controls depending on the user viewing the page. Adam On 03/18/2004 09:34 AM Max Cooper wrote: David, I think it is unusual to design the security system such that you must switch identities to meet your requirements. It may be worth rethinking your security system design so that a user will remain who they are, but be allowed to access resources that fall under their responsibility. As a generic example, it is customary for a user who is a system administrator to be able to change the password for any user in the system. The administrator does not actually switch their identity in the process, but rather they are granted access to do the password change by virtue of having some kind of sysadmin role. I realize that your business domain is more complex than that, but I think it would be useful to think about it in terms of a user having access to things without having to switch their identity. Since you can't use simple system-wide roles like admin due to the structure of responsibilities dictated by your business domain (client can add and edit their employees, but not the employees of another client), you have to do something special. One option is to map (flatten) the complex domain to a flat set of roles. For example, client Bob has role client1234.client, where client1234 is the client that Bob is a client for. You might also have roles like admin, reseller33, customer128, client1234.employee, etc. The numbers in in the role names are the id of the entity they represent. This requires programmatic security in a sense, since you will need to determine what role to check for at runtime. But you will still be able to use the J2EE standard request.isUserInRole() call to determine membership for the currently authenticated user. Another option is to do thoroughly programmatic security, where you still use container-managed security for authentication (is this Bob?) and write code to do the authorization (Bob wants to edit a user account in the context of the client with id = 1234, is Bob allowed to do that?) without mapping it to a role name. Perhaps your realm could create Principal objects such that the application code can ask the Principal if they can do something. Bob will very likely have other responsibilties (the same stuff the employees do) that you might wish to control with a single role client1234.employee. In that case, Bob would have both the client1234.client and client1234.employee roles. Alternately, you could identify a set of roles that would allow a user to do that stuff: client1234.employee, client1234.client, customer128, reseller33, etc. where client1234 is under the customer128 account, which in turn is under the reseller33 account. If Bob had any of those roles, he would be allowed to do employee stuff in the context of client1234. A single user can have an unlimited number of roles, and you can write your own security realm to read that information from a variety of tables in the database. Or write a view in the database for your User_Role join table and use a standard realm. Be aware that you might end up wasting a lot of memory if each user ends up with a ton of roles and your realm loads them all into memory during authentication. I have not done anything with JAAS, so perhaps there is a better solution available using JAAS technology. It would be great to hear from someone that knows of a good JAAS-based solution. David's problem of entity-based (rather than system-wide) responsibilities is a very common one. -Max - Original Message - From:
Re: ValidatorForm.getServlet() == null !!
Hi Albrecht, The ActionServlet in an ActionForm is a private member with no accessor methods. So, try this in your form: this.servlet.getServletContext(); HTH, Curtis Albrecht Berger wrote: Hello, I need the ServletContext in one of my forms, which I'm trying to get with : getServlet().getServletContext() Unfortunately I get a NullpointerException, because the servlet is null. How could this be, is there a workaround ? Thx berger - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: version 1.2
Hi, do you mean struts-1.2 final? I cannot find that at: http://jakarta.apache.org/site/binindex.cgi Zsolt -Original Message- From: Joe Germuska [mailto:[EMAIL PROTECTED] Sent: Saturday, March 20, 2004 3:20 PM To: Struts Users Mailing List Subject: Re: version 1.2 At 1:14 PM +0200 3/20/04, Erez Efrati wrote: Hi, I am currently working with the 1.1, is there a good reason to move to 1.2? Is it going to be released sometime soon? Struts 1.2.0 was released a few weeks ago using the new Tomcat-style version numbering. That means that a numbered release may or may not be considered a production quality release. There has not been a formal vote on the status of 1.2.0, but I think we'd cut another release rather than vote 1.2.0 as production-quality. If you're satisfied with Struts 1.1, you may as well stick with it. If you like to keep up with Struts while its evolving, you might be just as well off building from CVS Head as using Struts 1.2.0. That way you'd roll in recent bug fixes and be in a position to fix other bugs yourself if you find them (or just update from CVS and apply fixes and changes as they come in.) There aren't anywhere near the number of structural changes between 1.1 and 1.2 that there were between 1.0 and 1.1. Many deprecated members from 1.1 have been removed, so if you were ignoring the deprecation warnings all this time, you'll finally have to catch up. Also, if I recall correctly, there are some changes in the JSP tag libraries that may be hard to find until you compile the JSPs. Hope that helps, Joe -- Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com Imagine if every Thursday your shoes exploded if you tied them the usual way. This happens to us all the time with computers, and nobody thinks of complaining. -- Jef Raskin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: version 1.2
Yes, I here so much of this version so I wondered if it was released or the CVS head version is stable enough for production. Erez -Original Message- From: Zsolt Koppany [mailto:[EMAIL PROTECTED] Sent: Saturday, March 20, 2004 10:58 PM To: Struts Users Mailing List Subject: RE: version 1.2 Hi, do you mean struts-1.2 final? I cannot find that at: http://jakarta.apache.org/site/binindex.cgi Zsolt -Original Message- From: Joe Germuska [mailto:[EMAIL PROTECTED] Sent: Saturday, March 20, 2004 3:20 PM To: Struts Users Mailing List Subject: Re: version 1.2 At 1:14 PM +0200 3/20/04, Erez Efrati wrote: Hi, I am currently working with the 1.1, is there a good reason to move to 1.2? Is it going to be released sometime soon? Struts 1.2.0 was released a few weeks ago using the new Tomcat-style version numbering. That means that a numbered release may or may not be considered a production quality release. There has not been a formal vote on the status of 1.2.0, but I think we'd cut another release rather than vote 1.2.0 as production-quality. If you're satisfied with Struts 1.1, you may as well stick with it. If you like to keep up with Struts while its evolving, you might be just as well off building from CVS Head as using Struts 1.2.0. That way you'd roll in recent bug fixes and be in a position to fix other bugs yourself if you find them (or just update from CVS and apply fixes and changes as they come in.) There aren't anywhere near the number of structural changes between 1.1 and 1.2 that there were between 1.0 and 1.1. Many deprecated members from 1.1 have been removed, so if you were ignoring the deprecation warnings all this time, you'll finally have to catch up. Also, if I recall correctly, there are some changes in the JSP tag libraries that may be hard to find until you compile the JSPs. Hope that helps, Joe -- Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com Imagine if every Thursday your shoes exploded if you tied them the usual way. This happens to us all the time with computers, and nobody thinks of complaining. -- Jef Raskin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: version 1.2
As Joe mentioned, we no longer use the beta-beta-beta-final versioning scheme. We now use an immutable versioning scheme, like that used by the Apache HTTPD project, Jakata Tomcat, and many others. Each release is a point release, meaning it's a three part number: major-minor-point. The most recent Struts point release is 1.2.0. The next will be 1.2.1. Each number is an integer, so there can be any number of point releases. Each point release is created exactly once. After the release is created, we vote as to whether to change its status from alpha to beta and/or general availability. We may also vote to demote a release, if we discover problems later. At this time, Struts 1.1 is the best available release. Struts 1.2.0 is also available, but still considered alpha quality. ** We encourage everyone to try running your applications against 1.2.0 and report any problems. ** Right now, there are a handful of problem tickets against 1.2.0. As soon as those are resolved, we will issue 1.2.1. Hopefully, that release will make GA status. Either way, the next 1.2.x release after 1.2.1 will be 1.2.2. -Ted. On Sat, 20 Mar 2004 23:20:39 +0200, Erez Efrati wrote: Yes, I here so much of this version so I wondered if it was released or the CVS head version is stable enough for production. Erez -Original Message- From: Zsolt Koppany [mailto:[EMAIL PROTECTED] Sent: Saturday, March 20, 2004 10:58 PM To: Struts Users Mailing List Subject: RE: version 1.2 Hi, do you mean struts-1.2 final? I cannot find that at: http://jakarta.apache.org/site/binindex.cgi Zsolt -Original Message- From: Joe Germuska [mailto:[EMAIL PROTECTED] Sent: Saturday, March 20, 2004 3:20 PM To: Struts Users Mailing List Subject: Re: version 1.2 At 1:14 PM +0200 3/20/04, Erez Efrati wrote: Hi, I am currently working with the 1.1, is there a good reason to move to 1.2? Is it going to be released sometime soon? Struts 1.2.0 was released a few weeks ago using the new Tomcat- style version numbering. That means that a numbered release may or may not be considered a production quality release. There has not been a formal vote on the status of 1.2.0, but I think we'd cut another release rather than vote 1.2.0 as production-quality. If you're satisfied with Struts 1.1, you may as well stick with it. If you like to keep up with Struts while its evolving, you might be just as well off building from CVS Head as using Struts 1.2.0. That way you'd roll in recent bug fixes and be in a position to fix other bugs yourself if you find them (or just update from CVS and apply fixes and changes as they come in.) There aren't anywhere near the number of structural changes between 1.1 and 1.2 that there were between 1.0 and 1.1. Many deprecated members from 1.1 have been removed, so if you were ignoring the deprecation warnings all this time, you'll finally have to catch up. Also, if I recall correctly, there are some changes in the JSP tag libraries that may be hard to find until you compile the JSPs. Hope that helps, Joe -- Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com Imagine if every Thursday your shoes exploded if you tied them the usual way. This happens to us all the time with computers, and nobody thinks of complaining. -- Jef Raskin -- --- To unsubscribe, e-mail: struts-user- [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: struts-user- [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: struts-user- [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: version 1.2
Ted, Thanks a lot for clearing this issue. Erez -Original Message- From: Ted Husted [mailto:[EMAIL PROTECTED] Sent: Sunday, March 21, 2004 1:22 AM To: Struts Users Mailing List Subject: RE: version 1.2 As Joe mentioned, we no longer use the beta-beta-beta-final versioning scheme. We now use an immutable versioning scheme, like that used by the Apache HTTPD project, Jakata Tomcat, and many others. Each release is a point release, meaning it's a three part number: major-minor-point. The most recent Struts point release is 1.2.0. The next will be 1.2.1. Each number is an integer, so there can be any number of point releases. Each point release is created exactly once. After the release is created, we vote as to whether to change its status from alpha to beta and/or general availability. We may also vote to demote a release, if we discover problems later. At this time, Struts 1.1 is the best available release. Struts 1.2.0 is also available, but still considered alpha quality. ** We encourage everyone to try running your applications against 1.2.0 and report any problems. ** Right now, there are a handful of problem tickets against 1.2.0. As soon as those are resolved, we will issue 1.2.1. Hopefully, that release will make GA status. Either way, the next 1.2.x release after 1.2.1 will be 1.2.2. -Ted. On Sat, 20 Mar 2004 23:20:39 +0200, Erez Efrati wrote: Yes, I here so much of this version so I wondered if it was released or the CVS head version is stable enough for production. Erez -Original Message- From: Zsolt Koppany [mailto:[EMAIL PROTECTED] Sent: Saturday, March 20, 2004 10:58 PM To: Struts Users Mailing List Subject: RE: version 1.2 Hi, do you mean struts-1.2 final? I cannot find that at: http://jakarta.apache.org/site/binindex.cgi Zsolt -Original Message- From: Joe Germuska [mailto:[EMAIL PROTECTED] Sent: Saturday, March 20, 2004 3:20 PM To: Struts Users Mailing List Subject: Re: version 1.2 At 1:14 PM +0200 3/20/04, Erez Efrati wrote: Hi, I am currently working with the 1.1, is there a good reason to move to 1.2? Is it going to be released sometime soon? Struts 1.2.0 was released a few weeks ago using the new Tomcat- style version numbering. That means that a numbered release may or may not be considered a production quality release. There has not been a formal vote on the status of 1.2.0, but I think we'd cut another release rather than vote 1.2.0 as production-quality. If you're satisfied with Struts 1.1, you may as well stick with it. If you like to keep up with Struts while its evolving, you might be just as well off building from CVS Head as using Struts 1.2.0. That way you'd roll in recent bug fixes and be in a position to fix other bugs yourself if you find them (or just update from CVS and apply fixes and changes as they come in.) There aren't anywhere near the number of structural changes between 1.1 and 1.2 that there were between 1.0 and 1.1. Many deprecated members from 1.1 have been removed, so if you were ignoring the deprecation warnings all this time, you'll finally have to catch up. Also, if I recall correctly, there are some changes in the JSP tag libraries that may be hard to find until you compile the JSPs. Hope that helps, Joe -- Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com Imagine if every Thursday your shoes exploded if you tied them the usual way. This happens to us all the time with computers, and nobody thinks of complaining. -- Jef Raskin -- --- To unsubscribe, e-mail: struts-user- [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: struts-user- [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: struts-user- [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Security FIlter Framework
Sam, If possible, I think that there are a lot of advantages to using container-managed security. However, it depends on how well you authorization needs fit. If you are using LDAP for your back end security data store, then Weblogic CMA works well with this. I have not used Weblogic CMA against RDBMS but I am sure it works well for this as well provided that your data model is a close match. However, if your authorization rqmts are based on more than just role (for example, let's say a user's role plus the department he belongs to) than making CMA fit becomes more difficult. That is where something SecurityFilter works well. I have researched SecurityFilter (http://securityfilter.sourceforge.net) and I think it can be quite useful in bridging the gap between container-provided security and a custom security policy. One thing for sure is that it will be more portable across App Servers, than say, providing a Weblogic Custom Realm. However, I have not SecurityFilter in a production environment so YMMV. Bill as as wrote: Hi, We have a web app implemneted in struts and deployed in Weblogic 7.0.We are planning to implement/consider filter frameworks for allowing role based access into the web app.(may be including the security filter framework.)Any suggestions on how this can be done and design decisons Role based access meaning different users could get access only to different set of pages and anot all-trying tos eparate authentication from jsp's (business logic out of jsp's and into the filter framewrok/back end authentication mechanism) Thanks in advance. Sam. Do you Yahoo!? Yahoo! Finance Tax Center - File online. File on time. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
