I have deployed the struts-portlet example, and it works. I continue to
make comparison's between all of its configuration files, my own, and
other examples. For instance, your example does not specify a parent in
your pom.xml. The example does. The example pom.xml has no plugins.
Yours ha
avy-weight container, take a look at my two blog articles regarding
testing portlets with pluto and maven:
http://portletwork.blogspot.com/2007/07/mvnjetty-and-portlets.html
http://portletwork.blogspot.com/2007/08/maven-jetty-plugin-and-jsr168-portlets.html
On 8/15/07, Frederick N. Brier <[
How do you invoke your portlet application? Remember
that you can't access the portlet using regular urls, they all have to
go through the portlet container.
Nils-H
On 8/15/07, Frederick N. Brier <[EMAIL PROTECTED]> wrote:
I am pretty sure this is a configuration issue, probably in st
I am pretty sure this is a configuration issue, probably in struts.xml.
I am trying to create a JSR168 compliant portlet. I have been working
with the portletunit code to get it to execute in a unit test, as well
as running it with JBossPortal. The behavior is the same, so I am
hoping it is
I started out with an Appfuse project, but have customized it following
the Wiki directions on doing portlets with Struts2, specifically version
2.0.8 with XWork 2.0.3 integrating with Spring 2.0.6. The AppFuse
plugins have pulled in the struts2-spring-plugin, which contains the
class StrutsSp
I have been banging my head against an exception occurring during
deployment:
15:46:43,092 ERROR [STDERR] Caused by:
com.opensymphony.xwork2.inject.ContainerImpl$MissingDependencyException:
No mapping found for dependency [type=javax.servlet.ServletContext,
name='default'] in public void
org
6 matches
Mail list logo
