• Post Reply Bookmark Topic Watch Topic
  • New Topic

Servlet limitation

 
Pradeep bhatt
Ranch Hand
Posts: 8933
Firefox Browser Java Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
One minor (I would say insignificatnt) limitation of servlet is does not provide for automcatic population of a Java bean with request parameter data. Is Sun planing on work on this?
 
Marty Hall
Author
Ranch Hand
Posts: 111
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
One minor (I would say insignificatnt) limitation of servlet is does not provide for automcatic population of a Java bean with request parameter data. Is Sun planing on work on this?

Actually, I think this is more than an insignificant deficiency. You can do this in a JSP page (using property="*" in jsp:setProperty), but the spec doesn't expose the API to the underlying code to let you do it in a servlet. Furthermore, I would argue that a servlet, not a JSP page, is usually the right place to do this.
So, I dug around in the BeanUtils of the Jakarta Commons library, found the associated reflection code that already did the heavy lifting, and boiled it down to a simple "BeanUtilities.populateBean" method that I sometimes use. This utility is described in my book, but you can help yourself to the code by going to
http://volume1.coreservlets.com/archive/ and visiting Chapter 4.
Cheers-
- Marty
 
Marty Hall
Author
Ranch Hand
Posts: 111
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
...Is Sun planning on work on this?

PS Don't forget that it is the Java Community Process, not Sun, that controls the JSP and servlet specifications.
Cheers-
- Marty
 
Pradeep bhatt
Ranch Hand
Posts: 8933
Firefox Browser Java Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Marty Hall:

PS Don't forget that it is the Java Community Process, not Sun, that controls the JSP and servlet specifications.
Cheers-
- Marty


Thanks!
 
Ko Ko Naing
Ranch Hand
Posts: 3178
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Marty Hall:

PS Don't forget that it is the Java Community Process, not Sun, that controls the JSP and servlet specifications.
Cheers-
- Marty

So, Marty, do u mean that the responsibility of those specs are totally on JCP? Does Sun have any right to do sthing with them?
Could you please explain about the interaction between Sun and JCP? Thank you in advance...
 
Pradeep bhatt
Ranch Hand
Posts: 8933
Firefox Browser Java Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Memebers have to pay memberships fees to join the JCP, isn't ?
 
Marty Hall
Author
Ranch Hand
Posts: 111
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
So, Marty, do u mean that the responsibility of those specs are totally on JCP? Does Sun have any right to do sthing with them?
Could you please explain about the interaction between Sun and JCP?

Please see the Java Community Process overview and the JSP 2.0 JCP page.
My understanding is that Sun is a part of the JSP committee (Mark Roth, the spec lead, works for Sun, of course). However, I believe that Sun officially has no bigger voice on the committee than anyone else, and is not some sort of super veto-holding member.
Cheers-
- Marty
 
Ko Ko Naing
Ranch Hand
Posts: 3178
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
My understanding is that Sun is a part of the JSP committee (Mark Roth, the spec lead, works for Sun, of course). However, I believe that Sun officially has no bigger voice on the committee than anyone else, and is not some sort of super veto-holding member.

So instead of "Sun Certified Web Component Developer" certificate, it should be "JCP Certified Web Component Developer", for instance... Shouldn't it be? Just kidding... :roll:
So now I got it... JCP is like J2EE alliance to compete with M$, isn't it?
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!