No h:commandButton actions are executing

[schevus.swosborne.magellanhealth.com]

I have gone and broken something badly this time. I was adding a dependency to my application (jcifs), and now none of my commandButtons are executing their action (method or jpdl string transition name). s:buttons are still working fine.

When I click the commandbutton, my page refreshes and I get dumped out of my seam conversation. This is happening application wide, with buttons that had been working fine and on pages that were not touched, so I am not going to post any specific code for the buttons themselves. I have confirmed with h:messages that this is not a validation issue, and my buttons do not even work with immediate set to true.

Has anyone else experienced anything like this?

[antibrumm.mfrey0.bluewin.ch]

Hi
I cannot really help you but i got the same issue once i've tried to integrate jcifs in my application.

Do you use a filter for the authentication? I think it has something to do with this one.

Once i've added the filter to the chain i had problems in IE that none of the commands where going down to the server.. After several days of trying i gave up for the moment.

However, we have jcifs running in another seam application but i had no time (budget) to investigate more..

[schevus.swosborne.magellanhealth.com]

Thanks for the response Martin. I will do some tinkering with the filter and see if I can't figure out what the issue is there. It's a help to know this is probably jcifs specific and not some other random problem.

[schevus.swosborne.magellanhealth.com]

Well, I removed the filter and I'm still experiencing the same issues, so it seems like it's got to be some kind of dependency/classloader conflict. Anyone else have any ideas?

[schevus.swosborne.magellanhealth.com]

I removed the jcifs dependency and confirmed my app was back to a working state. Then I re-added it and sure enough, just adding the dependency is causing the commandButtons to fail. I really hate incompatible dependency issues like this because they are never documented anywhere and I get no error message at all, so this has been a joy to diagnose.

Any ideas for a workaround?