Thanks Ken,
GlassFish seems to not allow the use of '/' characters
in 'propertyValue' of a @ActivationConfigProperty.
Any reason for this?
thanks,
-Alexis
glassfish_at_javadesktop.org wrote:
> No, there is no standard for how a Java EE application server maps logical application
> dependencies to physical global resources. Same issue as Remote EJB JNDI names,
> JDBC Datasources, etc. It's true that in most cases it's just a simple name, which is
> why it should be easy for many vendors to support mappedName, but the exact syntax
> and semantics of the contents of the mappedName are not standard.
>
> However, despite the fact that mappedName is not required to be supported by all
> vendors there's no real downside to using it since it doesn't affect the semantics of your
> application at all. If it's supported by a given vendor it just means less vendor-specific
> configuration when you want to deploy. If it's not, the vendor will ignore it and you'll
> just need to do the same vendor-specific configuration you would have done if there
> weren't any mappedName. That configuration by definition must be possible without
> changing any of the standard contents of your app (deployment descriptors,
> application classes, etc.)
>
> Using mappedName isn't the same as relying on
> a vendor-specific API, which can actually prevent your application from running on
> a different implementation.
>
> --ken
> [Message sent by forum member 'ksak' (ksak)]
>
> http://forums.java.net/jive/thread.jspa?messageID=213415
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
--
Alexis Moussine-Pouchkine - Java Middleware Evangelism Team
http://blogs.sun.com/alexismp