unfortunately that does not solve the problems. the readme states that the app is not ready to run because there are portal-container specific configurations that are required - it comes packaged with jboss and liferay configurations. i find it odd that previous versions of the app can run without these configurations and the newer versions cannot. i think i will stick with 2.0 since it does not have the additional requirements, and my time schedule is too tight to try and develop the necessary websphere configuration files.
On 11/2/07, Nils-Helge Garli Hegvik <[EMAIL PROTECTED]> wrote: > > Seems like the 2.1.1-SNAPSHOT portlet app bundles servlet-api-2.3.jar. > Try removing it and see if that helps. > > Nils-H > > On 11/1/07, Brian Relph <[EMAIL PROTECTED]> wrote: > > this is the sample webapp downloaded from > > > http://people.apache.org/repo/m2-snapshot-repository/org/apache/struts/struts2-portlet/2.1.1-SNAPSHOT/ > > > > can i assume it was built with that struts2-portlet-plugin.jar on the > > classpath? > > > > On 11/1/07, Nils-Helge Garli Hegvik <[EMAIL PROTECTED]> wrote: > > > > > > The only real difference I can think of is that portlet support is a > > > plugin in 2.1. Is the struts2-portlet-plugin jar file in the classpath > > > of the application? > > > > > > Nils-H > > > > > > On 11/1/07, Brian Relph <[EMAIL PROTECTED]> wrote: > > > > Downloading and installing the struts2 portlet application 2.0.12works > > > > fine. The differences between 2.0.12 and 2.1.1 are minimal: > > > > > > > > web.xml has no difference ( i did not uncomment the dispatcher > servlet ) > > > > portlet.xml has no difference > > > > struts.xml includes struts-portlet-default.xml in 2.0.12 but not in > > > 2.1.1 > > > > struts.properties exists in 2.0.12 > > > > > > > > what other files could possibly contribute to the action mapping > > > > definitions? > > > > > > > > > > > > > > > > On 11/1/07, Brian Relph <[EMAIL PROTECTED]> wrote: > > > > > > > > > > I downloaded and installed the struts2 portlet application 2.1.1, > here > > > are > > > > > the logs - > > > > > > > > > > [11/1/07 14:59:22:785 CDT] 00000022 ApplicationMg A WSVR0200I: > > > Starting > > > > > application: struts2-portlet-2_1_1-SNAPSHOT_war > > > > > [11/1/07 14:59:22:801 CDT] 00000022 ApplicationMg A WSVR0204I: > > > > > Application: struts2-portlet-2_1_1-SNAPSHOT_war Application build > > > level: > > > > > Unknown > > > > > [11/1/07 14:59:22:910 CDT] 00000022 SibMessage I [:] > CWSID0017I: > > > > > Configuration reload is starting for bus RepositoryTopicBus. > > > > > [11/1/07 14:59:22:926 CDT] 00000022 SibMessage I [:] > CWSID0018I: > > > > > Configuration reload is complete for bus RepositoryTopicBus. > > > > > [11/1/07 14:59:22:941 CDT] 00000022 SibMessage I [:] > CWSID0019I: > > > > > Configuration reload is starting for messaging engine > > > > > CERN-BR014532Node02.server1-RepositoryTopicBus. > > > > > [11/1/07 14:59:23:019 CDT] 00000022 SibMessage I [:] > CWSID0020I: > > > > > Configuration reload is complete for messaging engine > > > > > CERN-BR014532Node02.server1-RepositoryTopicBus. > > > > > [11/1/07 14:59:23:035 CDT] 00000022 SibMessage I [:] > CWSIS1569I: > > > > > Messaging engine CERN-BR014532Node02.server1-RepositoryTopicBus is > > > using a > > > > > file store. > > > > > [11/1/07 14:59:23:487 CDT] 00000022 WebGroup A SRVE0169I: > > > Loading > > > > > Web Module: struts2-portlet-2.1.1-SNAPSHOT.war. > > > > > [11/1/07 14:59:23:893 CDT] 00000022 WebApp A SRVE0180I: > > > > > [struts2-portlet-2_1_1-SNAPSHOT_war#struts2- > portlet-2.1.1-SNAPSHOT.war > > > ] > > > > > [/struts2-portlet-211] [Servlet.LOG]: Initializing Spring root > > > > > WebApplicationContext > > > > > [11/1/07 14:59:24:252 CDT] 00000022 VirtualHost I SRVE0250I: > Web > > > > > Module <null> has been bound to > > > > > > > > > default_host[*:9081,*:80,*:9444,*:5060,*:5061,*:443,*:9088,*:9451,*:5073,*:5072,*:9083,*:9446,*:5063,*:5062,*:9084,*:9447,*:5065,*:5064]. > > > > > > > > > > [11/1/07 14:59:24:268 CDT] 00000022 ApplicationMg A WSVR0221I: > > > > > Application started: struts2-portlet-2_1_1-SNAPSHOT_war > > > > > > > > > > [11/1/07 15:01:54:195 CDT] 00000022 SystemOut O 15:01:54,195 > ERROR > > > [ > > > > > org.apache.struts2.dispatcher.Dispatcher ] Could not find action > or > > > result > > > > > There is no Action mapped for action name StrutsPortlet/. - > [unknown > > > > > location] > > > > > at com.opensymphony.xwork2.DefaultActionProxy.prepare( > > > > > DefaultActionProxy.java:185) > > > > > > > > > > I am accessing the portlet with > > > > > http://localhost:9081/struts2-portlet-211/StrutsPortlet/ > > > > > > > > > > > > > > > On the struts2 wiki, there is a comment under the tutorial section > for > > > > > portlets, that mentions a WAS 6.1 bugfix - I am running Was > 6.1.0.11, > > > and > > > > > i applied the custom property > > > > > > > > > > com.ibm.ws.webcontainer.invokefilterscompatibility=true > > > > > > > > > > to both the webserver container and the portlet container, but it > did > > > not seem to make a difference > > > > > > > > > > > > > > > On 11/1/07, Nils-Helge Garli Hegvik <[EMAIL PROTECTED] > wrote: > > > > > > > > > > > > Hi! > > > > > > > > > > > > In version 2.1, the portlet support was moved into a plugin. It > > > could > > > > > > be related to that. Can you find any exceptions or traces of > error > > > in > > > > > > the logs somewhere? > > > > > > > > > > > > Nils-H > > > > > > > > > > > > On 11/1/07, Brian Relph <[EMAIL PROTECTED]> wrote: > > > > > > > I was hoping to get help deploying a struts2 portlet. I have > been > > > > > > > developing based on the portlet archetype with the embedded > > > > > > jetty/pluto > > > > > > > portlet container as detailed at > http://portletwork.blogspot.com/ > > > > > > > > > > > > > > This archetype is based on struts 2.1.0, and developing with > it > > > has > > > > > > been > > > > > > > great. However, when deploying to a WAS 6.1 server, i would > get > > > > > > "Error 404: > > > > > > > There is no Action mapped for action name > > > > > > HealtheAdmin/", "HealtheAdmin" > > > > > > > being the name of my portlet. While trying to solve this > problem, > > > I > > > > > > > downloaded the same archetype with struts 2.0.9dependencies > /config, > > > > > > and it > > > > > > > deployed on my server no problem. So basically, I have been > > > > > > developing with > > > > > > > struts 2.1.0 b/c of how easy the embedded portlet container > makes > > > it, > > > > > > and > > > > > > > then deploying with 2.0.9. > > > > > > > > > > > > > > However, I would like to not have the mis-matched versions. I > was > > > > > > hoping > > > > > > > someone could help clarify the changes i need to make for my > > > 2.1.0portlet > > > > > > > to work so that i can get stop deploying with 2.0.9. I have > also > > > > > > looked at > > > > > > > the 2.1.1 portlet sample application, and tried deploying > it. I > > > built > > > > > > it > > > > > > > with no profiles, but got the same error as before ("Error > 404: > > > There > > > > > > is no > > > > > > > Action mapped for action name HealtheAdmin/"). If i build it > with > > > the > > > > > > > "pluto" profile, I get several errors - first, the pluto > plugin > > > seems > > > > > > to > > > > > > > generate a web.xml that does not match the dtd, so it is > > > invalid. If > > > > > > i fix > > > > > > > that manually, my server complains about having matching > servlet > > > and > > > > > > portlet > > > > > > > names. > > > > > > > > > > > > > > Can anyone explain the differences between 2.0.9, 2.1.0, and > > > 2.1.1portlet > > > > > > > applications, how to build them, and where configuration > unique to > > > my > > > > > > > portlet & server should be? > > > > > > > > > > > > > > Thanks, > > > > > > > Brian > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > 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] > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
