Since JMS depends on Java EE APIs, it would make sense to place them in their own packages similar to how the db code is handled. I know they work fine as is, but it makes it easier to segregate optional dependencies. This would be useful for OSGi so that we can use the full set of metadata available without requiring all the optional dependencies in the Import-Package attribute.
-- Matt Sicker <[email protected]>
