Provide Java-backed URI::Fast support for CPAN compatibility
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
研究方向
Start by mapping the URI-Fast 0.55 public methods and upstream tests to candidate Java URI libraries, especially Apache HttpComponents Core 5 URIBuilder, and document mismatches in raw versus decoded fields, repeated or empty query values, IRI handling, resolution, and normalization. Then implement a PerlOnJava provider for the supported surface and decide how to handle the tests' URI::Encode::XS dependency. Done means the upstream suite passes under both PerlOnJava backends without native XS compilation, with focused regression coverage for the listed behaviors.
由索引模型根據 Issue 內容生成。
描述
Summary
Add Java-backed support for CPAN distribution URI-Fast so it can run under PerlOnJava without compiling its XS implementation. The current release, URI-Fast 0.55, is a useful compatibility target and failed in CPAN random run 20261118-104825-43075 because URI::Fast unconditionally calls XSLoader::load.
Evidence
- PerlOnJava installed the distribution's
.pmfiles but cannot compileFast.xs. All 19 test programs then failed before running assertions withno Java XS implementation available. - The system Perl oracle built the XS modules and passed both
URI::Encode::XSand the completeURI::Fasttest suite. URI::Fastimplements its main behavior in XS: parsing and component storage; raw and decoded accessors; percent encoding and decoding; query parameters and keysets; normalization; absolute/relative URI resolution; and IRI construction.- The tests also use the separate XS-only
URI::Encode::XSdistribution. AURI::Fastimplementation can avoid this dependency at runtime, but full upstream test compatibility may require supporting that module too or adapting the test dependency path. - Reverse dependencies (released distributions with a required runtime dependency; five-year window ending 2026-11-19):
URI::Fast: 2 total, 0 recent (Net-Curl-Parallel,WebService-Pokemon);URI::Encode::XS: 5 total, 3 recent (AnyEvent-InfluxDB,Bencher-Scenario-URIEscaping,Catalyst-Plugin-CachedUriForAction,HTTP-Promise,Opsview-RestAPI). - The failure requires no platform-specific native library beyond the XS build itself; PerlOnJava's inability to load these XS objects is sufficient to explain it.
Java library investigation
Apache HttpComponents Core 5 URIBuilder appears to be the most practical existing Java foundation to evaluate. It provides component mutation, path segments, query parameters, and normalization; Core 5.4 added an RFC 3986 encoding policy. The project does not currently bundle this dependency, and it is not a drop-in replacement for the Perl API. In particular, we need to check its exact handling of raw versus decoded fields, repeated/empty query values, IRI input, and URI::Fast's resolution and comparison behavior.
java.net.URI is already available but its documented normalization and resolution are based on RFC 2396 and it does not provide the mutable API. Kuri advertises an RFC 3986 Uri API accessible from Java, but it is a Kotlin dependency in the 0.x series and should be evaluated for maturity and packaging before adoption.
Proposed work
- Map the upstream
URI::Fasttests and public methods to Java library capabilities; record where the selected library matches and where PerlOnJava needs a compatibility layer. - Choose between Apache URIBuilder, another maintained Java implementation, or a focused project-owned adapter. Avoid making the selected library's API visible to Perl code.
- Add a Java provider for the supported
URI::Fastsurface, including the raw/decoded distinction and IRI behavior, and makeXSLoadercalls resolve to it under PerlOnJava. - Decide whether
URI::Encode::XSneeds an independent Java provider for its own compatibility, or whether it is only a test-time dependency for this distribution. - Preserve upstream tests and add project-owned regression coverage for any discovered PerlOnJava behavior gaps.
Acceptance criteria
- The URI-Fast 0.55 upstream suite passes under PerlOnJava's JVM and interpreter backends without native XS compilation.
- The
URI::Fastbehaviors listed above are covered, including repeated query keys, percent encoding, IRI handling, and RFC 3986 resolution/normalization. - System Perl remains the behavioral oracle, and Java library mismatches are documented and covered by focused regression tests.
- The implementation does not require exposing Java library types in the Perl-facing API.
- 主要語言
- Perl
- 星號
- 67
- 分支
- 8
- 平均合併
- 5 小時 12 分鐘
- 30 天內合併 PR
- 131
環境準備
- 提供 Dockerfile 或 Docker Compose 檔案
- 沒有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
fglock/PerlOnJava 的其他 Issue
-
area:cpan-port bug
難度 2/5 1-3 小時 新手友好度 70/100
fglock/PerlOnJava#2153 ·
維護者通常 1 天內回覆
-
area:cpan-port area:parser bug
難度 2/5 1-3 小時 新手友好度 68/100
fglock/PerlOnJava#2137 ·
維護者通常 1 天內回覆
-
area:backend area:cpan-port area:runtime bug
難度 2/5 1-3 小時 新手友好度 76/100
fglock/PerlOnJava#2071 ·
維護者通常 1 天內回覆
-
area:runtime documentation enhancement
難度 2/5 1-3 小時 新手友好度 72/100
fglock/PerlOnJava#1579 ·
維護者通常 1 天內回覆
-
area:cpan-port bug
難度 3/5 1-2 天 新手友好度 62/100
fglock/PerlOnJava#2157 ·
維護者通常 1 天內回覆
查看 fglock/PerlOnJava 的全部 Issue
相似的 Issue
-
Dev-output directory preparation accepts file-valued lib/include paths and fails on dangling links未關閉team-cli
難度 2/5 1-3 小時 新手友好度 70/100
維護者通常 2 天內回覆
-
難度 2/5 1-3 小時 新手友好度 66/100
-
難度 1/5 1 小時以內 新手友好度 93/100
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 73/100
inverse-inc/packetfence#9728 ·
維護者通常 1 天內回覆
-
fix(char-create): show the real reason a character is refused可能已有人在做 @baphomello 於 1 天前認領。 未關閉
難度 2/5 1-3 小時 新手友好度 84/100
維護者通常 1 天內回覆