Hey,
Only view this in the spirit of a bunch of people comparing notes on a cool
technology. Because it is absolutely not constructive for the Struts problems
I've read the last week.
I don't want to start a flame war in the middle of some poor soul getting help
on a problem, but it invariably may?
I've noticed that since I've used exclusively Tapestry, configuration and
troubleshooting conversations such as these have totally disappeared where I
work.
Maybe it's because Tapestry's error messages are specific. For instance,
Tapestry would tell you which line number in what file the property was
incorrect. In fact in Eclipse Spindle would highlite the bug. I think there
are Struts compilers that may do this also.
I am working on an applicaton that has 450 urls and 1500 subscreens, with about
as many entities in the DB. I could not even fathom doing this with anything
but Tapestry and Hibernate.
Anyway, if you have the option(and we hardly ever do), try the Tapestry demo,
your fresh Struts wounds will provide more insight.
good luck...
>
> From: Brian K Bonner <brian.bonner@xxxxxxxxxxxx>
> Date: 2004/12/14 Tue AM 03:10:47 GMT
> To: users@xxxxxxxxxx
> Subject: Re: [cinjug-users] struts question: No bean specified
>
> Look at your stderr/stdout log for a clue.
>
> It's probably that you don't have a form specified for an action (check
> struts-config.xml).
>
> Good luck.
>
> Brian
>
> Trey Howard <trey.howard@xxxxxxxxxxxxxxxx> wrote on 12/13/2004 04:26:13
> PM:
>
> > Hi All
> >
> > I'm working on a Struts application and just ran across a rather
> > unhelpful error message:
> > java.lang.IllegalArgumentException: No bean specified
> > at
> > org.apache.commons.beanutils.PropertyUtils.
> > getPropertyDescriptor(PropertyUtils.java:837)
> > at
> > org.apache.commons.beanutils.BeanUtils.setProperty(BeanUtils.java:934)
> > ... (none of my code specified in the stack trace)
> >
> > I have a JSP that submits to a servlet.
> > I'm pretty sure I have all my xdoclet/struts-config elements defined.
> > The JSP renders just fine, but when I submit any of the forms on the JSP
>
> > (all point to the same servlet), I get the above exception.
> > I tried putting a debug statement at the first line of the servlet's
> > execute() method, but that didn't print out.
> >
> > What are common causes for encountering this exception?
> > Any help would be appreciated.
> >
> > -Trey
> >
> >
> > ---------
> > You may unsubscribe from this mailing list
> > by sending a blank email addressed to:
> > users-unsubscribe@xxxxxxxxxx
> >
> > --
> > Find additional help by sending a blank email
> > addressed to:
> > users-help@xxxxxxxxxx
> >
>
>
> ---------
> You may unsubscribe from this mailing list
> by sending a blank email addressed to:
> users-unsubscribe@xxxxxxxxxx
>
> --
> Find additional help by sending a blank email
> addressed to:
> users-help@xxxxxxxxxx
>
>
|