impl and api part of this spec are linked == the api jar can't be use with other impl (mojarra api + myfaces impl or the opposite wouldn't work)
Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2012/12/14 Harald Wellmann <hwellmann...@gmail.com>: > I don't get the point. Other Java EE Spec JARs also contain real > classes and not just interfaces. What's so special about the JSF API? > > 2012/12/14 Romain Manni-Bucau <rmannibu...@gmail.com>: >> yes, >> >> it is in myfaces-api. >> >> The JSF API contains...implementation..so it cannot be part of the >> main javaee-api otherwise you cannot override it anymore. >> >> Romain Manni-Bucau >> Twitter: @rmannibucau >> Blog: http://rmannibucau.wordpress.com/ >> LinkedIn: http://fr.linkedin.com/in/rmannibucau >> Github: https://github.com/rmannibucau >> >> >> >> 2012/12/14 Harald Wellmann <hwellmann...@gmail.com>: >>> When I came across this artifact >>> >>> <groupId>org.apache.openejb</groupId> >>> <artifactId>javaee-api</artifactId> >>> <version>6.0-4</version> >>> >>> I was hoping to have found a drop-in replacement for the infamous >>> javax:javaee-api containing mutilated bytecode. >>> >>> But it's not the complete Java EE API, javax.faces is missing for >>> instance. Any good reason for that? >>> >>> Best regards, >>> Harald
