This is somehow connected to my question before on a migration guide, is
it needed?
There's no migration guide from 2.0.x to 2.1.x. I agree one will be needed
because you can't simply change jars over, but I don't think users should be
switching over on-mass anyway yet.
If you want to start writing a transition guide from your experiences on the
wiki I'll happily contribute a few pointers.
WARNING: [57:14.332] Could not find property [#attr.theme]
These are just warnings, not problems or errors. The "ability to log or
throw exceptions for expressions that contain non-existent
properties..." was recently added to OgnlValueStack. The purpose,
presumably, was to raise awareness that the implementation is making
requests for undefined properties on the value stack and allow
developers to do something about it when it matters.
2.1 is a developmental baseline and one consequence is that you'll
regularly encounter temporary unit test failures and build errors. It's
also unlikely that you'll receive much support on the users or dev list
for non-critical issues at the moment. I personally wouldn't recommend
using 2.1 yet unless you know how to recognise the significance of
issues and report or work-around them when necessary.
In this specific case, it's just a new warning about an existing
operation. You don't need to do anything about it, although someone
probably will when they tire of seeing the warnings.
regards,
Jeromy Evans
Pedro Herrera wrote:
I´m having the same problem to building struts 2.1.x trunk ... 'Could not
find property [#attr.theme]'
Herrera
Giovanni Azua-3 wrote:
hi,
While building Struts 2.1.x trunk branch test cases I get tons of this
kind of warnings:
WARNING: [57:14.332] Could not find property [#attr.theme]
WARNING: [57:14.364] Could not find property [#attr.templateDir]
WARNING: [57:14.365] Could not find property [#attr.theme]
The same happened when I flipped the jars from my current 2.0.9 version
to 2.1.x a
build I did myself from trunk .. what is the reason for this issue?
solutions? I had theme
and templateDir defined in struts.properties like this:
### Standard UI theme
### Change this to reflect which path should be used for JSP control tag
templates by default
struts.ui.theme=xhtml
struts.ui.templateDir=template
This is somehow connected to my question before on a migration guide, is
it needed?
TIA,
regards,
Giovanni
---------------------------------------------------------------------
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]
