jakartaee / interceptors Goto Github PK
View Code? Open in Web Editor NEWJakarta Interceptors
Home Page: https://eclipse.org/ee4j/interceptors
License: Other
Jakarta Interceptors
Home Page: https://eclipse.org/ee4j/interceptors
License: Other
Hello; I just noticed this and didn't want it to get lost.
See https://github.com/eclipse-ee4j/interceptor-api/blob/master/spec/src/main/asciidoc/2_interceptor_programming_contract.adoc#timeout-method-interceptor-methods. The example involves calling getInfo()
on the timer object returned by InvocationContext#getTimer()
, which is of type Object
. Hence this won't compile.
Update Eclipse GlassFish to use the new version of your API (and implementation, if applicable) by submitting a PR to GlassFish.
Although a new version of GlassFish will not be released for Jakarta EE 8, we hope to release an update sometime later.
Jakarta release of this API has wrong value of OSGi Bundle-SymbolicName in MANIFEST.MF.
Current value is javax.interceptor-api but expected value could be jakarta.interceptor-api .
A requirement for the EE10 release is for API jars to include a proper module-info.class. Please create a service release to include this.
The mailing list URL in the specification is incorrect. It currently reads:
https://dev.eclipse.org/mailman/listinfo/interceptor-api-dev
…but the mailing list in question appears to reside elsewhere. PR coming shortly.
This is a place holder issue for Pull request from javaee/javax.interceptor#3
In order to prepare this project to engage in specification work, we need to convert it into a specification project as defined by the Eclipse Foundation Specification Process (EFSP). As part of this work, we will change the project name and the scope.
We'll use this issue to capture the work that needs to be done as part of this effort.
We need to create a release CI/CD pipeline for this project.
Use these documents as a reference:
This task is for creating a basic build CI/CD pipeline for this project on Eclipse infrastructure. More information is here: https://ci.eclipse.org/.
The question in $title came up recently and I failed to find any solid mention in interceptors specificatio and javadoc that would be either for or against the usage of repeating annotations as interceptor bindings.
I know that, for instance, Weld (CDI impl) allows you to do that. However, this doesn't seem to be backed by any specification. I'd be nice to have it written somewhere. WDYT?
Passing Release Review is a required step before making a first public release. Deadline for passing the review is Nov 30th, 2018. Release review takes some time to complete, so it makes sense initiating it as soon as possible.
Additional information:
I went looking for the spec doc the other day.
Turns out that the doc on website is 5 pages long and contains licences plus first paragraph of chapter one and that's it (for both, 1.2 and 2.x).
Same goes for when you try to build the doc from repo, at least on master branch.
Per the discussions on the Spec Committee and Platform Dev mailing lists, it's been discovered that many of the Javadoc and Spec references to the EFSL need updating. Please reference the following required updates and keep them in mind as your Spec Project is updating the files for Jakarta EE 9.
Note: Some Spec Projects have already started or even completed these updates. If so, just kindly return/close this Issue. Thanks!
Required EFSL updates for Javadoc
For javadoc, the EFSL.html located in src/main/javadoc/doc-files should be modified as follows:
<<url to this license>>
needs to be replaced with efsl.php link[1][title and URI of the Eclipse Foundation specification document]
needs to be replaced with the Specification Name and URL (Reference [2] for an example.)Required EFSL updates for Specifications
For specification, the license-efsl.adoc located in src/main/asciidoc should be modified as follows:
<<url to this license>>
needs to be replaced with efsl.php link[1][title and URI of the Eclipse Foundation specification document]
needs to be replaced with the Specification Name and URL (Reference [2] for an example.)[1] https://www.eclipse.org/legal/efsl.php
[2] https://jakarta.ee/specifications/enterprise-beans/4.0/
Background information:
https://waynebeaton.wordpress.com/2019/04/04/renaming-java-ee-specifications-for-jakarta-ee/
Checklist:
Update the scope statement for the project: https://projects.eclipse.org/projects/ee4j.jakartaee-platform/governance
See https://docs.google.com/spreadsheets/d/1FPLjo_DJDOQngVtdrYgaDk98d9NBG-0ODgdmOG3LOsI/edit?usp=sharing for examples.
Due, probably primarily, to the history of the Interceptors specification, the specification mentions "business method" 16 times but never defines it.
"Business method" is a well-defined term in the Jakarta EJB specification, from whose ancestor the original Interceptors specification evolved. I suspect that the definition found there is the one that should be included here.
Last CTS runs indicate no failures in this component. It's time to make a public release. Before the release make sure that Eclipse Release Review is passed and all dependencies have been released.
This is a place holder issue for Pull request from javaee/javax.interceptor#2
Tasks to complete the release:
Draft
to Final
.847c80c9c80bea4682006f186292b68acdd0ce9b239d998856c3a379c3a7be50
See here for detailed instructions.
This information is from the Weld CDI CCR.
Is your feature request related to a problem? Please describe.
Jakarta EE 9 is the next major release, with the main focus of moving from the javax
namespace to the jakarta
namespace.
Describe the solution you'd like
This issue will be used to track the progress of this work effort via the Jakarta EE 9 Project board.
Additional context
Jakarta EE Specification Process
Eclipse Project Handbook
Eclipse Release Record for Jakarta EE 9
ToDo
Hello,
recently we came across and interesting question which revolves around interception of default methods.
Currently, the specification doesn't really mention default methods. Therefore you can only imply what it should behave like.
One not so obvious aspect is inheritance rules for interceptor bindings in conjunction with default methods.
According to what the spec says right now, you do not inherit bindings from interfaces. However, that means that the only way to intercept a default method is to use a class-level binding on the implementing class.
I have seen this disputed by users (of Weld and Quarkus, both of which support default method interception) several times and I have to give them some credit for it. It is indeed not really intuitive. It also takes away some customization power because you cannot use method-level binding with default methods; you have to intercept all methods of the implementing class.
I realize changing this presents backward compatibility issues and I am not saying we should go that way. However, I'd like to hear some more opinions on how people perceive this, if the spec should perhaps mention this and what they think could/should be done in this regard.
I can not download the jar anymore: https://mvnrepository.com/artifact/javax.interceptor/javax.interceptor-api/3.1
I also tried it from Germany and with a proxy from US.
This was brought up in the CDI project as the following issue:
jakartaee/cdi#592
The basic idea is to add a series of getInterceptorBindings() default methods to the jakarta.interceptors.InvocationContext interface.
All current API libraries shipped must be distributed to Maven Central under a sub-package of the jakarta
groupId. Before the first release Maven coordinates of this project must be changed as it's described here.
75b2493a117e7f8fe775cc7e2e8a605a203611895091f4bb9aaabed57f813392
#13 must be finished before starting working on this task.
as is required and documented in https://www.eclipse.org/projects/handbook/#legaldoc
We need the 3.0.0 final release to be able to release the 2.2.0 final of interceptors
Create/Update CONTRIBUTING files
Per input from the Eclipse EMO, each Specification Project needs to ensure that a CONTRIBUTING.md or CONTRIBUTING.adoc file exists in each specification-related repository maintained by Specification Projects.
In addition, the CONTRIBUTING.md or CONTRIBUTING.adoc file needs to include the following text:
## Eclipse Development Process
This Eclipse Foundation open project is governed by the Eclipse Foundation
Development Process and operates under the terms of the Eclipse IP Policy.
The Jakarta EE Specification Committee has adopted the Jakarta EE Specification
Process (JESP) in accordance with the Eclipse Foundation Specification Process
v1.2 (EFSP) to ensure that the specification process is complied with by all
Jakarta EE specification projects.
* https://eclipse.org/projects/dev_process
* https://www.eclipse.org/org/documents/Eclipse_IP_Policy.pdf
* https://jakarta.ee/about/jesp/
* https://www.eclipse.org/legal/efsp_non_assert.php
Please do this at your earliest convenience.
Thank you!
-- EE4J PMC ([email protected])
Uptake new Eclipse versions of dependencies (if any). Use GlassFish 5.1 Release Tracker wiki to find components versions to use.
Release to OSSRH staging repository
Update GlassFish 5.1 Release Tracker with released version number.
In the steering committee we voted to moved all specification projects from eclipse-ee4j to jakartaee. As such this repo should move to in due time.
Moving is fairly automatic, and redirects will be automatically put in place from the current location here to the new location.
If there are no objections I'd like to move this repo soon.
To test Jakarta EE 8 compatibility we need to create a Jenkins job on project's Cloud Jenkins instance formally testing the API against the relevant TCK and as needed, relevant CTS subset tests.
For projects that do not already have automated testing, there is provided parameterized Jenkins job that can be invoked to perform these tests. User provides a link to an Eclipse GlassFish test build and sets the test sub-set parameters:
Additional instructions and guidance for using and directly running TCKs is available on this wiki. Also in the jakartaee-tck project repository.
This is a place holder issue for Pull request from javaee/javax.interceptor#1
The interceptor api declared 2 deps common-annotations
and ejb
in the pom.xml,
but none of them has been imported, so can we remove it?
https://github.com/eclipse-ee4j/interceptor-api/blob/8eb1e608ad81c06ddfd147a077c06cad2b46f9a2/pom.xml#L322-L334
➜ interceptor-api git:(EE4J_8) find . -name \*.java -exec grep "import javax" {} \;
➜ interceptor-api git:(EE4J_8)
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.