Hi, again, Ray.
Note that the Java Web Start-launched app client container no longer
honors the policy setting option you have been specifying on the URL.
This was determined to be a security risk because code from an arbitrary
source could try to grant itself elevated permissions this way.
As for setting DBHome... You should be able to add to the query string
in the URL something like this
prop=DBHome=correctValue
separated using an ampersand ('&') from any other argument or property
settings in the query string. This blog entry
http://blogs.sun.com/quinn/entry/command_line_arguments_and_properties
has more details.
Could you try that and see if it gets you farther?
- Tim
Martin, Ray wrote:
> Because i am not able to get appclient/JWS to 'play nice' with my security
> policy, i commented out code that causes a SecurityManager to be required.
> i took out all the getClassLoader calls - they were just for learning
> experience. i commented out all setProperty methods - now i cannot set
> DBHome - not a good thing.
>
> So, now i am back to seeing how well appclient/JWS will run my application.
> It keeps coughing up the error, javax.persistence.PersistenceException: No
> Persistence provider for EntityManager named SVG_drawings. This raises the
> question of why appclient/JWS cannot see META-INF/persistence.xml in my
> application jar file - while on the other hand, 'appclient only' fails on
> the same line (the creation of EntityManagerFactory), but the error report
> is totally different - 'appclient only' kicks out the currentLoaderNotValid
> error.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>