wood burning stoves
The moose likes JSF and the fly likes JSF 1.1 - problems with h:commandButton Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of REST with Spring (video course) this week in the Spring forum!
JavaRanch » Java Forums » Java » JSF
Bookmark "JSF 1.1 - problems with h:commandButton" Watch "JSF 1.1 - problems with h:commandButton" New topic

JSF 1.1 - problems with h:commandButton

Bruno Weninger

Joined: Apr 08, 2011
Posts: 2
Hello people, here's the deal: I have a fully-working JSF 1.1 app, but when I deploy it from Tomcat to Websphere 6.1, my h.commandButtons stop working. I wonder why does that happen. Do you have any idea?
Tim Holloway
Saloon Keeper

Joined: Jun 25, 2001
Posts: 17280

Depending on what service packs are in place, WAS 6.1 may have JSF built into it. In my case, I was using a newer JSF, so I had to override the default classloading sequence to prevent conflicts with the built-in JSF.

I recommend you ask over in the WebSphere forum, since it's a server-specific problem with a server-specific solution.

An IDE is no substitute for an Intelligent Developer.
Bruno Weninger

Joined: Apr 08, 2011
Posts: 2
I tried that, thanks. Still waiting for reply, though.
Shasi Mitra
Ranch Hand

Joined: Nov 27, 2008
Posts: 101

Did you deploy in websphere directly or import the application into RAD and then deployed? In the latter case, check your web.xml for any unwanted IBM's code. Also try changing the class loading mode to parent_last and see..hope your command button is enclosed in a form..try removing any rendered attribute for your command button and check..hope there are no validation errors..
I agree. Here's the link: http://aspose.com/file-tools
subject: JSF 1.1 - problems with h:commandButton
It's not a secret anymore!