RE: FormAuthentication and Error Code 500
Hi Kazuhito, Unfortunately I haven't been able to spend any more time on this problem since my last post. If I get some time over the next few days I'll find out what exactly is going on and I'll let you guys know. Thanks, Setanta. -Original Message- From: Kazuhito SUGURI [mailto:[EMAIL PROTECTED] Sent: 20 November 2004 07:56 To: [EMAIL PROTECTED] Subject: Re: FormAuthentication and Error Code 500 Hi Setanta, Could you post server log? We need more detail to understand what's going on. In article [EMAIL PROTECTED], Thu, 18 Nov 2004 13:25:02 -, Setanta Mathews [EMAIL PROTECTED] wrote: smathews The authentication must be working. Part of the test in question calls an smathews EJB that does the following check: smathews smathews principal = sessionContext.getCallerPrincipal(); smathews name = principal.getName(); smathews System.out.println(User Id: + name); smathews if (name.equals(anonymous) || name.equals(guest)) smathews throw new PrincipalException(Principal must be authenticated); smathews smathews Without the begin method in my test the principal name is guest and a smathews PrincipalException will be thrown. With the begin method the principal name smathews is 0 (so authentication must have happened) and no exception is thrown. If the purpose of the authentication is to get a principal name, and you think the FormAuthentication goes worng, you might try to use the BasicAuthentication for your unit-testing of EJBs. smathews I agree that setting the expected response code to 500 is dangerous smathews but I can't spend too much more time trying to get my tests running. I don't think that is a good idea. It may take long time to solve your problem with FormAuthentication, but it cannot be a reason to bypassing the problem by such unusual approach. I suggest you to use more simple authentication for your tests. Regards, Kazuhito SUGURI mailto:[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]
RE: cactus and weblogic8.1
Vincent Thanks for your reply. The problem is with the Filter Redirector sections of web.xml. If I comment them out, then I don't have a problem and my ServletTests run, but with Filter Redirector section in, I get the error listed below. Greg. -Original Message- From: Vincent Massol [mailto:[EMAIL PROTECTED] Sent: Saturday, November 20, 2004 10:46 AM To: 'Cactus Users List' Subject: RE: cactus and weblogic8.1 Hi Greg, Are you saying that if you manually build your WAR and then use it with cactus it works fine but if you use cactifywar and then cactus it doesn't work? Note that I have now started the Cargo project (http://cargo.codehaus.org) that supports WL 8.x. You should be able to use Cargo instead of the cactus task. But if your problem is in the cactifywar task, it won't help. Thanks -Vincent -Original Message- From: Greg Kubaczkowski [mailto:[EMAIL PROTECTED] Sent: vendredi 19 novembre 2004 21:40 To: '[EMAIL PROTECTED]' Subject: cactus and weblogic8.1 Hi all I'm having problem deploying cactified apps to weblogic. I have seen the references to this problem on the list, but did not find an answer to it. The problem is that when I'm trying to deploy my cactified war I get the following error: Nov 19, 2004 2:30:34 PM EST Warning DRS BEA-002506 The current version 149 for DataIdentifier DataIdentifierID: 1 does not match with incoming version 157 for a one-phase update. Nov 19, 2004 2:30:34 PM EST Warning Deployer BEA-149004 Failures were detected while initiating Deploy task for application contactcapture-cactus. Nov 19, 2004 2:30:34 PM EST Error Deployer BEA-149201 Failed to complete the deployment task with ID 11 for the application contactcapture-cactus. weblogic.management.DeploymentException: Exception:weblogic.management.ApplicationException: start() failed. Module: contactcapture-cactus Error: java.lang.ExceptionInInitializerError at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(Slave De ployer.java:2354) at weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.j av a:2136) at weblogic.management.deploy.slave.SlaveDeployer$Task.checkAutoCommit(SlaveD ep loyer.java:2235) at weblogic.management.deploy.slave.SlaveDeployer$Task.prepare(SlaveDeployer. ja va:2130) at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveD ep loyer.java:2315) at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDep lo yer.java:866) at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer. ja va:594) at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer .j ava:508) at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler. ja va:25) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178) --- nested within: -- weblogic.management.ManagementException: - with nested exception: [weblogic.management.DeploymentException: Exception:weblogic.management.ApplicationException: start() failed. Module: contactcapture-cactus Error: java.lang.ExceptionInInitializerError ] at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveD ep loyer.java:2327) at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDep lo yer.java:866) at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer. ja va:594) at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer .j ava:508) at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler. ja va:25) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178) Now, if I create my war manually (as opposed via ant cactifywar task), and comment out the Filter Redirector sections (both filter and filter- mapping), everything works fine. Any thoughts? I'm using cactus 1.6.1, weblogic 8.1 sp3. Greg Kubaczkowski Senior Java Developer Enterprise DW Solutions, I.T. Loyalty Management Group - 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]
RE: cactus and weblogic8.1
-Original Message- From: Greg Kubaczkowski [mailto:[EMAIL PROTECTED] Sent: lundi 22 novembre 2004 15:30 To: 'Cactus Users List' Subject: RE: cactus and weblogic8.1 Vincent Thanks for your reply. The problem is with the Filter Redirector sections of web.xml. If I comment them out, then I don't have a problem and my ServletTests run, but with Filter Redirector section in, I get the error listed below. Ok, I understand. I have no idea what's causing the problem. Maybe it's something from WL 8.x. It was working fine for me when I was using WL 7.x. In any case, WL 8.x is unfortunately not yet supported by Cactus (meaning it's not integrated in our code nor in our test suite). It's simply a lack of time. For the past month, I have been working on Cargo with the will to migrate the Cactus Ant code to Cargo. This is where all my efforts are being spent today. So hopefully, in the not too far future, we should be able to get WL 8.x support (through Cargo) for Cactus. Thanks and sorry -Vincent Greg. -Original Message- From: Vincent Massol [mailto:[EMAIL PROTECTED] Sent: Saturday, November 20, 2004 10:46 AM To: 'Cactus Users List' Subject: RE: cactus and weblogic8.1 Hi Greg, Are you saying that if you manually build your WAR and then use it with cactus it works fine but if you use cactifywar and then cactus it doesn't work? Note that I have now started the Cargo project (http://cargo.codehaus.org) that supports WL 8.x. You should be able to use Cargo instead of the cactus task. But if your problem is in the cactifywar task, it won't help. Thanks -Vincent -Original Message- From: Greg Kubaczkowski [mailto:[EMAIL PROTECTED] Sent: vendredi 19 novembre 2004 21:40 To: '[EMAIL PROTECTED]' Subject: cactus and weblogic8.1 Hi all I'm having problem deploying cactified apps to weblogic. I have seen the references to this problem on the list, but did not find an answer to it. The problem is that when I'm trying to deploy my cactified war I get the following error: Nov 19, 2004 2:30:34 PM EST Warning DRS BEA-002506 The current version 149 for DataIdentifier DataIdentifierID: 1 does not match with incoming version 157 for a one-phase update. Nov 19, 2004 2:30:34 PM EST Warning Deployer BEA-149004 Failures were detected while initiating Deploy task for application contactcapture-cactus. Nov 19, 2004 2:30:34 PM EST Error Deployer BEA-149201 Failed to complete the deployment task with ID 11 for the application contactcapture-cactus. weblogic.management.DeploymentException: Exception:weblogic.management.ApplicationException: start() failed. Module: contactcapture-cactus Error: java.lang.ExceptionInInitializerError at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(Slave De ployer.java:2354) at weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.j av a:2136) at weblogic.management.deploy.slave.SlaveDeployer$Task.checkAutoCommit(SlaveD ep loyer.java:2235) at weblogic.management.deploy.slave.SlaveDeployer$Task.prepare(SlaveDeployer. ja va:2130) at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveD ep loyer.java:2315) at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDep lo yer.java:866) at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer. ja va:594) at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer .j ava:508) at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler. ja va:25) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178) --- nested within: -- weblogic.management.ManagementException: - with nested exception: [weblogic.management.DeploymentException: Exception:weblogic.management.ApplicationException: start() failed. Module: contactcapture-cactus Error: java.lang.ExceptionInInitializerError ] at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveD ep loyer.java:2327) at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDep lo yer.java:866) at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer. ja va:594) at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer .j ava:508) at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler. ja va:25) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219) at
