te')); return $arr; } /* 遍历用户所有主题 * @param $uid 用户ID * @param int $page 页数 * @param int $pagesize 每页记录条数 * @param bool $desc 排序方式 TRUE降序 FALSE升序 * @param string $key 返回的数组用那一列的值作为 key * @param array $col 查询哪些列 */ function thread_tid_find_by_uid($uid, $page = 1, $pagesize = 1000, $desc = TRUE, $key = 'tid', $col = array()) { if (empty($uid)) return array(); $orderby = TRUE == $desc ? -1 : 1; $arr = thread_tid__find($cond = array('uid' => $uid), array('tid' => $orderby), $page, $pagesize, $key, $col); return $arr; } // 遍历栏目下tid 支持数组 $fid = array(1,2,3) function thread_tid_find_by_fid($fid, $page = 1, $pagesize = 1000, $desc = TRUE) { if (empty($fid)) return array(); $orderby = TRUE == $desc ? -1 : 1; $arr = thread_tid__find($cond = array('fid' => $fid), array('tid' => $orderby), $page, $pagesize, 'tid', array('tid', 'verify_date')); return $arr; } function thread_tid_delete($tid) { if (empty($tid)) return FALSE; $r = thread_tid__delete(array('tid' => $tid)); return $r; } function thread_tid_count() { $n = thread_tid__count(); return $n; } // 统计用户主题数 大数量下严谨使用非主键统计 function thread_uid_count($uid) { $n = thread_tid__count(array('uid' => $uid)); return $n; } // 统计栏目主题数 大数量下严谨使用非主键统计 function thread_fid_count($fid) { $n = thread_tid__count(array('fid' => $fid)); return $n; } ?>java - Issue with Quarkus exception handling extension not capturing exceptions - Stack Overflow

科技改变生活-雨落星辰 - 所有的伟大,都源于一个勇敢的开始

    最新消息：雨落星辰是一个专注网站SEO优化、网站SEO诊断、搜索引擎研究、网络营销推广、网站策划运营及站长类的自媒体原创博客
    你的位置： 首页>programmer>java - Issue with Quarkus exception handling extension not capturing exceptions - Stack Overflow

    java - Issue with Quarkus exception handling extension not capturing exceptions - Stack Overflow

    programmeradmin2浏览0评论

    I’m working on several Quarkus APIs that communicate via REST within a Kubernetes cluster. I’ve implemented an exception handling mechanism that captures exceptions, formats them to match a standard, and returns them. The solution is based on the implementation of the ResponseExceptionMapper and ExceptionMapper interfaces from JAX-RS. As shared code between the APIs, it works perfectly fine.

    Recently, with the increasing number of APIs, I decided to refactor the exception handling into a Quarkus extension that can be deployed alongside all my APIs. The extension seems to load correctly in our Quarkus APIs, but exceptions are not being captured. When an exception is thrown, the code in the extension is not executed. As a result, a 500 error occurs.

    I’ve tried implementing a Recorder, but it hasn’t worked. I’m still relatively new to Quarkus, and AI tools haven’t been very helpful. I’m sure the issue is simple, but I can’t seem to figure it out. I’d really appreciate any help you can offer!

    Here’s a link to a quickly created GitHub project that contains the code for the extension: GitHub - Quarkus Exception Handler

    Thanks in advance for your kind assistance!

    I’m working on several Quarkus APIs that communicate via REST within a Kubernetes cluster. I’ve implemented an exception handling mechanism that captures exceptions, formats them to match a standard, and returns them. The solution is based on the implementation of the ResponseExceptionMapper and ExceptionMapper interfaces from JAX-RS. As shared code between the APIs, it works perfectly fine.

    Recently, with the increasing number of APIs, I decided to refactor the exception handling into a Quarkus extension that can be deployed alongside all my APIs. The extension seems to load correctly in our Quarkus APIs, but exceptions are not being captured. When an exception is thrown, the code in the extension is not executed. As a result, a 500 error occurs.

    I’ve tried implementing a Recorder, but it hasn’t worked. I’m still relatively new to Quarkus, and AI tools haven’t been very helpful. I’m sure the issue is simple, but I can’t seem to figure it out. I’d really appreciate any help you can offer!

    Here’s a link to a quickly created GitHub project that contains the code for the extension: GitHub - Quarkus Exception Handler

    Thanks in advance for your kind assistance!

    • java
    • rest
    • exception
    • quarkus
    • quarkus-extension
    Share Improve this question asked Feb 17 at 17:40 Laurent_LDNRLaurent_LDNR 12 bronze badges New contributor Laurent_LDNR is a new contributor to this site. Take care in asking for clarification, commenting, and answering. Check out our Code of Conduct. 5
    • Is the code for the exception mapper in the runtime module? Also, does that module have an empty beans.xml file? – geoand Commented Feb 17 at 20:02
    • Yes, the code is in the runtime module. There is no beans.xml file. – Laurent_LDNR Commented Feb 18 at 8:25
    • None of those mappers have registered, because ExceptionFeature is not a registered extension. Add jakarta.ws.rs.ext.Provider annotation to ExceptionFeature class. – zfo Commented 2 days ago
    • You need to add an empty META-INF/beans.xml in src/main/resources of the runtime module. – geoand Commented 2 days ago
    • Thank you for your answer. I've already tried annotate ExceptionFeature with Provider but it didn't change anything. – Laurent_LDNR Commented 2 days ago
    Add a comment  | 

    1 Answer 1

    Reset to default 0

    Thanks for your advice, @geoand and @zfo:

    None of those mappers have registered, because ExceptionFeature is not a registered extension. Add jakarta.ws.rs.ext.Provider annotation to ExceptionFeature class.

    – zfo

    You need to add an empty META-INF/beans.xml in src/main/resources of the runtime module.

    – geoand

    The beans were not properly registered. Combining your solutions solved the issue. Everything works fine now!

    Thank you for your help!

    与本文相关的文章

    发布评论

    评论列表(0)

    1. 暂无评论