Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Weld 3.1.7.Final Proxy changes has broken mybatis-cdi support #207

Closed
hazendaz opened this issue Apr 4, 2021 · 1 comment
Closed

Weld 3.1.7.Final Proxy changes has broken mybatis-cdi support #207

hazendaz opened this issue Apr 4, 2021 · 1 comment
Assignees
@hazendaz

Comments

@hazendaz
Copy link
Member

hazendaz commented Apr 4, 2021

Update to 3.1.7.Final was reported broken for mybatis-cdi private usage.

This can be demonstrated in our current test set. Simply bump cdi 2.0 support weld up to 3.1.7.Final and run the build with cdi 2.0 profile.

mvn clean install -P"cdi-2.0"

[INFO] Running org.mybatis.cdi.FooServiceTest
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.107 s <<< FAILURE! - in org.mybatis.cdi.FooServiceTest
[ERROR] org.mybatis.cdi.FooServiceTest Time elapsed: 0.107 s <<< ERROR!

I believe this has to do with the proxy and use of interfaces. I haven't done any further research yet and this could be a bug with weld itself given they broke this on a patch level.
@hazendaz hazendaz self-assigned this Apr 4, 2021
@hazendaz
Copy link
Member Author

hazendaz commented May 8, 2021

Fixed via #211

@hazendaz hazendaz closed this as completed May 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@hazendaz hazendaz

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@hazendaz