The project proposal for Soteria should be submitted to the Eclipse Foundation this week. Then it takes a few weeks for Eclipse to vote on and approve the proposal. Then the repository and issues need

I hope everyone is clear on the difference between spec and implementation. Spec changes require use of the JCP, implementation changes do not. If there are bugs in the Soteria implementation of JSR 3

Will Hopkins wrote on 08/10/17 06:17 PM: No, the kinds of trivial changes that might be make between FAB and Final Release are a small subset of errata. As the page says: I would consider that a trivi

Arjan Tijms wrote on 08/ 2/17 02:05 PM: As Will explained, the materials submitted to the JCP aren't exactly the final versions since at least things like the license and the version number will chang

Using this across modules would introduce a tight coupling that probably isn't desirable. Roles really do seem like a better approach in that case. Or the module could provide an API that could be cal

Using JNDI-style names for resource names would be confusing. What's the use case for this method in general, and for using this method with a resource that's in another module? Arjan Tijms wrote on 0

Arjan Tijms wrote on 05/31/17 03:41 AM: I assume this is about hasAccessToWebResource... As I read the spec, the resource name is relative to the web module. If you're not in a web container, what nam

Will Hopkins wrote on 05/26/17 02:49 PM: Assuming you own the root package (e.g., javax.security.enterprise), classes at the root are fine, maybe even good. That's where I would expect to find most of

"javax" was originally for "extensions" that were not part of the JDK. Obviously that hasn't been the case for quite some time. It was never intended only for Java EE. I agree that we shouldn't put an

I fixed it. And I'll have a "talk" with whoever did it wrong to begin with. :-) Thanks for helping to spread the word. Will Hopkins wrote on 05/12/17 11:49 AM: