
![]() | General | ![]() |
![]() | Java | ![]() |
![]() | Linux | ![]() |
jamwiki
Wednesday, March 05, 2008
[INFO] artifact org.apache.struts:struts2-sitemesh-plugin: checking for updates from central
[WARNING] An error occurred during dependency resolution of the following artifact:
org.apache.struts:struts2-sitemesh-pluginnull
Caused by: Couldn't find a version in [2.0.11.1] to match range [2.0.11,)
org.apache.struts:struts2-sitemesh-plugin:jar:null
Is this a maven problem or a struts2 problem with the release artifact
Sunday, March 02, 2008
OpenProj is a free, open source project management solution. OpenProj is a complete replacement of Microsoft Project and other commercial project solutions.
Comments [0] Permalink
Thursday, January 10, 2008
Originally, I was looking for something that allowed me to refer to the package name from using the wildcard syntax.
This would allow me to template out my crud actions using a concise configuration and follow my pattern of development with zero-config/annonations did not.
With that not in place I found hope to solve my problem in a fairly similar fashion.
It involves use of a tag that has not made its way to the dtd.
"default-class-ref"
I am eagerly waiting for this simple tag to finally make its way to the struts2 dtd.
It was originally added to the xwork dtd, but lagged in finally getting it over to struts2.
Despite some resistance by Don Brown, I believe in many circumstances it is even more beneficial than the
One can forgo the wildcard, zero configuration, rest, or xyz plugin and use good ole fashion configuration inheritance.
consider the possibilities with templating out your abstract action, the substituting what class is used -->
<package name="Abstract-crud" extends="struts-default" abstract="true">
<!-- edit is often used as the create/view -->
<action name="edit" >
<result name="input" type="velocity">edit.vm</result>
<result name="success" type="velocity">edit.vm</result>
<result name="error" type="velocity">edit.vm</result>
</action>
<action name="save" >
<result name="input" type="velocity">edit.vm</result>
<result name="success" type="chain">list</result>
<result name="error" type="velocity">edit.vm</result>
<result name="cancel" type="redirect">list.action</result>
</action>
<action name="list" method="list">
<result name="success" type="redirectAction">list</result>
</action>
<action name="delete" method="delete">
<result name="success" type="redirectAction">list</result>
</action>
</package>
<package name="Example" extends="Abstract-crud" namespace="/example">
<default-class-ref class="org.ExampleAction" />
</package>
<package name="Example2" extends="Abstract-crud" namespace="/example2">
<default-class-ref class="org.Example2Action" />
<action name="override" class="org.Example2Action" method="override">
<result name="success" type="velocity">somethingelse.vm</result>
</action>
</package>
<package name="SubItem" extends="Abstract-crud" namespace="/example2/subItem">
<default-class-ref class="org.SubItemAction" />
</package>
Monday, January 07, 2008
I admit, early on in the process, the bar was set pretty high with Jive's Clearspace. Honestly I think it is awesome. Great layout, multiple wiki spaces, personal blogs, forums, polls, LDAP authenication and killer intergation with openfire chat server.
However Clearspace is not open source and its pricing is out of reach at this point in time. I am trying to introduce the wiki as a pilot to a techie and non techie work enviroment. (Maybe at a little point in time)
Look little at JSPWiki, overall I thought it was a little raw for a non-techie corporate enviroment.
XWiki seemed a little better in terms of features. I like the fact individual users can have their own blogs.
It also seems to have the concept of a discussion forum.
I wish it had more than one theme.
Its overall all look and feel is unpolished in some areas and acceptable in others. There are some very good features that are by default not obvious to the overall navigation.
The deal breaker is XWiki is "slop". Its not packaged together with care, just slopped together. This becomes obvious with one look at the WEB-INF\lib directory in recent downloadable .war archives.
Half of the jars is that directory are not need.
I am not intimate with the code, but just glancing the surface the following are build time only jars
Wednesday, December 12, 2007
Currently take a look at Lambda Probe
Seems to be pretty nice, though we have run into a couple problems while running it under an IBM box under a IBM 5.0 JVM. I'm curious what else is out there and also open source.
Sunday, September 02, 2007
Around work, I've seen applications where there are
several log4j configurations checked in along side each other(dev,
test, prod). Often, the only differences are location of where the log
files go.
A better solution would not require, .war files to be re-built in order
to only change log file destinations. Log4J will interpret variables
given to it.
e.g. ${LOG_HOME}/mylog.txt
<appender name="FILE" class="org.apache.log4j.FileAppender">
<param name="File" value="${LOG_HOME}/mylog.txt"/>
<param name="Append" value="false"/>
<layout class="org.apache.log4j.PatternLayout">
<param name="ConversionPattern" value="%d %-5p [%t] %C{2} (%F:%L) - %m%n"/>
</layout>
</appender>
To supply this value to tomcat set variable "CATALINA_OPTS". e.g.
CATALINA_OPTS=-DLOG_HOME=/usr/java/logs
export CATALINA_OPTS
(before calling catalina.sh run)
or on windows
SET CATALINA_OPTS=-DLOG_HOME=/usr/java/logs
(this can also be set via system environment settings in the control panel).
I like this solution better than hard coding the path or referring to ${CATALINA_HOME}, which would be specific to tomcat.
This can easily be construed to work with other app servers as well (jetty/glassfish).
Other notes, on windows I was able to just define LOG_HOME as an
environment variable, where on linux I had to supply it via
CATALINA_OPTS.
I know the above isn't rocket science, but perhaps we can make use of this generalization.
Tuesday, August 07, 2007
WebDrive
http://www.southrivertech.com/purchase/wdpricing.html
For 59.95, you too can have a copy of "webdrive" that allows you to map drive letters to sftp(ftp over ssh).
That kind of stuff has been built into linux for years.
sftp is one of the many kio slaves built into konqueror.
I can't believe people pay for this kind of stuff.
btw: for other examples of file systems people have been using with linux see: http://fuse.sourceforge.net/wiki/index.php/FileSystems