|
|
|
http://jira.codehaus.org/browse/CARGO-286
http://jira.codehaus.org/browse/CARGO-373 All have the same issues with the expanded war. I've tested a JBoss 4.0.5 existing server & standalone configuration setup. One thing that has changed in at least JBoss 4.0.5 is that out-of-the-box, remote mbean-invocations require authentication, so the shutdown command fails.
" Hi Mikko,
The problem is that you're using a RemotePropertySet property for a local container. This isn't logical. I think we have 2 options: I think 2) is the best. If you"re interested in taking this further I'd suggest creating a JIRA issue for renaming the remote username/password properties and fixing this first and then we could apply the fix for this issue. WDYT? Thanks Hi Vincent,
Yep, I was aware that the naming might be a bit confusing. Problem was that RemotePropertySet is container-agnostic and used by at least Geronimo, JBoss and Tomcat. Without commit access, the patch would be pretty. And even more serious, would break all existing configs if I rename the property keys "cargo.remote.username" and "cargo.remote.password". To preserve backward compatability, I suppose leaving RemotePropertySet user & pass in place would be OK? As a more unintrusive fix, I could add something like "cargo.jboss.username" & "cargo.jboss.password" in JBossPropertySet, thereby making it JBoss specific? But then what about remote JBoss'es, should they also use these? Now, what do you think? (Oh why doesn't jira allow comment editing...)
sed "s/"the patch would be pretty."/"the patch wouldn't be pretty."/g" Patch to:
Applied (added modifications for the m1 build).
Mikko, let's continue the discussion on the cargo list (I know you've answered there and I haven't replied yet...). We'll create a new issue if need be.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Failed with 4.0.3SP1, 4.0.4.GA
Extrait from the test report: