On 13/08/2013 22:58, Arjan Tijms wrote: > markt wrote >>> we are contacting standalone and EE web profile Servlet containers >> [...] >> The has been very little demand from the Apache Tomcat user community to >> support the Java EE web profile. > > I guess Ron meant Tomcat with the "standalone Servlet container" and didn't > ask for Tomcat to implement the EE web profile ;)
Had you not cut all the context, it would be clear that Ron's question was: <quote> Does the Tomcat community support the inclusion of the Servlet profile of JSR 196 in the EE web Profile? </quote> Hence my response. I don't think the Tomcat developers are in a position to pass judgement on what should or should not be in the web profile as we have little to no visibility into what users want from the web profile. Since I wrote that original response, there have been a handful of users on the users list asking questions about the Tomcat part of TomEE but nothing to change my view that there has been very little demand for web profile support from the Tomcat user community. What I don't have visibility of is the mix of TomEE users between Tomcat users wanting more and J2EE container users wanting less. From $dayjob, I see more of the later: folks currently using full J2EE wanting to move to the web profile or Tomcat. > markt wrote >> JASPIC was on the TODO list for Tomcat 7 for a while but it dropped off >> because a) it wasn't a mandatory requirement for Servlet containers and >> b) there was very little (no references at all on the users list) for it. > > Maybe the last point is because of the classic chicken & egg problem? People > are not writing portable authentication modules, since they know Tomcat > doesn't support them. Because of that few of them are being written and thus > other people do not ask for it. Maybe. On the other hand, look at the demand from the user community we saw for WebSocket. The only folks talking about JSR 196 have been either EG members like Ron or David, or Tomcat committers mentioning that JSR 196 support was being considered or might be a possible implementation solution for something. Not a single user has asked for JSR 196 support. > As Ron already demonstrated a bit, the Servlet Profile of JASPIC should be > relatively easy to support. It's not a complete new feature with a lot of > code that has to be build into Tomcat (like e.g. supporting CDI would > require). No-one said it would be difficult. TomEE has already done it. We'd just need to lift the code. Difficulty really doesn't come into it. If there is a demand for it, it will get implemented. If there isn't, it won't. At the moment the main driver for this, in my view, is to provide an API for folks that want to do things like this: https://issues.apache.org/bugzilla/show_bug.cgi?id=54503 JASPIC isn't on the TODO list for 8.0.x but it is still early enough to add it. Doing this for Tomcat 8 is on my "it would be nice to do this if I can find the time" list. > Instead, it's doing something that Tomcat already does, but (more or less) > layering some standardized interfaces on top of that. In fact Tomcat's > JAASRealm > (http://tomcat.apache.org/tomcat-8.0-doc/realm-howto.html#JAASRealm) is not > that far away from a JASPIC implementation. > > > markt wrote >> You'd obviously get a very different reaction if the Servlet spec was >> going to >> require JSR 196 support. > > Just out of curiosity, but what would you think the reaction might be if > that was going to happen? If the Servlet specification required JSR 196 support then it would get implemented. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
