file, the bare beginnings of the Service Control Manager on the server side,
and the new "community left menu" on the client side (still controlled by the
existing feature mechanism, for now). The engine still needs to incorporate
the SCM in place of the old feature definitions. Also added some utility
classes (StockMessage, XMLLoader) to aid with loading XML data from the
config files (big help in the RenderConfig constructor and
VeniceEngineImpl.initialize!)
EnvUser, EnvCommunity, and EnvConference each need to keep a reference to their
own SecurityMonitor, we can't rely on getStaticMonitor() (but we still need it,
to make the other "wrapper" functions work)
defined in the JSP to the FindData object and eliminated the InternalStateError
throw. Lesson here, kids...just because you CAN do a thing doesn't mean you
SHOULD do a thing.
architecture--it's implemented at the global level and for communities,
conferences still use the old hard-coded implementation. The new
StaticSecurityMonitor is configured via XML data, which will be important
when we implement the new Community Services architecture
separated from the internal objects (as well as separating the internal
interfaces), some prep work for modularizing the SIG-to-service interface so
it'll be easier to add chat and stuff. Also fixed up a display issue with
1-character CDTextFormFields.
files as they are likely to change VERY infrequently; this simplifies a lot
of bits of code that would otherwise have to call through VeniceEngine, etc.
Also folded the LocaleFactory class method into the new International object
used for managing the lists.
of "properties" storage and editing for conferences, communities, users, and
the global system. In addition, the "global properties" editing screen got
implemented, because it wasn't there yet.
on XML config files...the implementation should now be much more customizable
and less klunky. Added a provision for implementing "generic" (JSP-driven)
sideboxes. Implemented the sidebox configure button on the front page
(finally!). Implemented a random password generator class which will be used
in a future implementation of reminder-driven automatic forgotten-password
changing. Fixed some minor funnies in SIG menu generation.
the underlying support) - incidentally, this is a lot of support for the SIG
logo as well, just need some front end work for that in the future
(of course, we now require JAI 1.1.1)
- added color customization in render-config.xml
- added ability to scale size of Venice logo in footer
- added ability to customize size of site logo, as well as add a hyperlink
- moved to use of LOG4J 1.1.3, LOG4J now installed in Venice lib directory
instead of in JRE extensions directory (only Java extensions should go in
JRE extensions directory)
- close to requiring JAXP 1.1 (will still work with 1.0 though)
