I have the same problem. I have successfully deployed bigrez to a WLS 10.3.2, but I get the same class problem with Tiles when deploying to WLS 10.3.3.

I don't want to create a fresh domain, since I am testing this app in a broader environment. So my domain is already there. Any solution hints?

Hi Phil,

Sorry for my very late reply. I had some other priorities last months but I'm still curious why the demo app throws the error and I hope you will still help me with it.

Unfortunately it is not possible to test it in another domain.
Furthermore I forgot to mention that I also installed the OSB on the adminserver and SOA suite in the same domain but deployed on another managed server.
Maybe the problem is caused by different classpath of classloader order?

You can find the build at this dropbox link: http://dl.dropbox.com/u/582156/wrox-...x-wls-demo.zip
I also included my setDomainEnv and setSOADomainEnv scripts in the zip file.

regards,

David

Phil,

I created a new domain on my laptop. The bigrez sample app now deploys succesfully. So i guess installation of OSB on the admin server must be the reason bigrez failed to deploy.

Anyway, thanks for your time looking at this problem.

regards,

David

Execute() in the py script fails looking for a JDBC file.

Posted images here:

https://snt137.mail.live.com/default...0A3127C7%21419

Thanks for your help.

Ken

Ken, I don't have a windows live account. Can you post the error somewhere public?

Phil, I have forwarded it to you...

I think it may be a win2008 server permissions problem, even though I am using the admin account to deploy. I rebuilt the environment/app on win2003 server and the error went away. Some tests fail, but am happy the app deployed and works. Thanks for taking a look at the previous post so quickly.

I was just about to suggest checking disk space and file permissions :-)

I changed security on the C drive so "Everyone" had full control. The same error continues to happen. I am a security novice so am wondering what I may have missed. Thanks

I'd check that the security permission has been inherited correctly by the folder mentioned in the error message.