This is the apache javafaces spec api jar. This spec is weird in that it sort of requires that the implementation and spec jar be in the same classloader. For osgi purposes I cooked up a myfaces bundle that includes both myfaces-api and myfaces-impl so that in an osgi environment they actually will be in the same classloader. For non-osgi environments repackaging the api jar in the openejb api jar should be ok. It does mean the openejb api jar is not really usable in osgi with a javafaces implementation, but I don't consider that a big problem.
thanks david jencks On Oct 28, 2011, at 1:01 PM, David Blevins wrote: > We should probably yank the myfaces-api from the current javaee-api jar > snapshot. > > Seems this jar is really an implementation and if someone wanted to use a > different Faces implementation they would be unable to do so. > > > -David > > On Oct 28, 2011, at 12:53 PM, Matt Benson wrote: > >> On Fri, Oct 28, 2011 at 2:46 PM, David Blevins <[email protected]> >> wrote: >>> Quick question on the org.apache.myfaces.core:myfaces-api jar. >>> >>> Is it tied to MyFaces in some way? Guessing the answer is, yes, as it is >>> labeled "myfaces-api" and not something more generic like "faces-api" >>> >>> If the answer is, no, then the follow up is how often does its contents >>> change? >>> >>> If it is stable and only changed once in a while, we might include it in >>> the javaee-api jar we produce from OpenEJB/TomEE. We don't include >>> JavaMail for example as it really isn't an API but an actual >>> implementation. Seems like that is the case here. >> >> Nail on the head and all that. :) >> >> Matt >> >>> >>> >>> -David >>> >>> >
