Bug 83475

Created attachment 33279 [details]
exception

Ok, I'll test w/8.2. If you have the full stack trace from app server log can
you attach it? Thanks.

Created attachment 34158 [details]
server.log

I see a space in class problem from app server. Can you create a project in a
different location w/o space and verify this? Thanks.

again, can you please test as I suggested? thanks

There's bigger problem now - I tested it also with non-space path and result was
the same - in last build deploying of web application with JSF pages from entity
class results in Http status 404 error.I used NB5.5 dev build 200609240000 and
all  other remained the same.Web module is deployed,according to Output tab and
even Appserver admin console,when I open it in browser.Still,I see in browser
error page and there's plenty of exceptions in server.log. I'm attaching
server.log, along with screenshots of error in browser and admin console of
appserver.
I think this issue was caused by some last time changes,maybe issue 82048 fix.

NOTICE: I tried to run web module with basic support - only welcomeJSF page and
it worked O.K.

Created attachment 34442 [details]
Error in browser

Created attachment 34443 [details]
Appserver admin console

Created attachment 34444 [details]
server.log

This last problem is caused by the fact that after unchedking the "Set source
level to 1.4" checkbox in the wizard, the source level is set to 1.6 - should be
1.5. I filed a separate issue 85672 for that (should that be a P2 or P3?).

The workaround is to change source level to 1.5 in project properties and then
Clean & Build the project - after that I am getting the original FacesException.

After applying the workaround for issue 85672 on an application without space in
path, the problem still happens.

I guess the original (java.lang.RuntimePermission createClassLoader) is caused
by default SUN server policy settings which does not allow classloaders within
webapplications. See e.g.: http://www.w4toolkit.com/forum/read.php?21,6482,13821 .

This workaround works fine.

Mentioned workaround is to replace original contains of server.policy file with
this:

grant {
// Allow everything for now
permission java.security.AllPermission;
}; 

So, what should be the right fix? I think we cannot changed automatically the
server.policy file.

Ludo, any ideas?

If I  understand correctly, you are foing EJB3 JPA apps in a web app for AS 8.2

I am not sure many people tried that, but I guess the JPA runtime is doing
things that by default are not allowed by the 8.2 security manager. 
8.2 is by default very conservative and secured by default.
We remove this constraint for 9.0
If you google this subject 81, 82 and security manager, you'll se that many Web
frameworks need extended security seeting in order to run on 8.2.

So I guess this is the same for JPA framework and AS 8.2. 
I'll also ask the JPA group, but if this is the case, this bug can be fixed via
release notes. Changing server.policy has to be a user decision and we do not
offer AS admin api for that.

I also think, that there is not a way how to fix it correctly. Which module will
alter the server.policy file? Persistence, jsf support or the server plugin? I
think it should be done by the servlet plugin, but as Ludo wrote, there is no
api how to do it now?

There was a suggestion from Marina how to fix this:

> I need to see the stack trace of the classloader exception, but they
> probably need to add toplink.weaving property and set it to false. 

However, when I added the following line into persistence.xml, it did not help
and I got the same exception:

<property name="toplink.weaving" value="false"/>

I suggest we waive this issue for NetBeans 5.5.

Changing priority to P3 per team agreement.

Closing as WONTFIX, needs to be documented in FAQ.