-
Notifications
You must be signed in to change notification settings - Fork 47
Comparing changes
Open a pull request
base repository: ebics-java/ebics-java-client
base: f537b24
head repository: ebics-java/ebics-java-client
compare: 9e45631
- 7 commits
- 17 files changed
- 3 contributors
Commits on Jul 6, 2026
-
Configuration menu - View commit details
-
Copy full SHA for fc09f77 - Browse repository at this point
Copy the full SHA fc09f77View commit details
Commits on Aug 24, 2026
-
feat(h005): support BTD download orders with service params and date …
…range Downloads sent the 3-letter order code as AdminOrderType with empty StandardOrderParams, which EBICS 3.0 banks reject for customer data. This mirrors the existing BTU upload path: optional EbicsDownloadParams produce AdminOrderType=BTD with a BTDOrderParams/Service block, container type and an optional DateRange. Also fixes the date range that fetchFile(file, orderType, start, end) accepted and dropped: without a service name the legacy order type is kept and the range goes into StandardOrderParams. Behaviour without params is unchanged. Dates are written as plain xs:date; passing a Calendar made XMLBeans append the local offset (2026-08-10+02:00), which shifts the reported day for a bank in another timezone. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 83129e0 - Browse repository at this point
Copy the full SHA 83129e0View commit details -
fix(h005): validate download arguments before any bank contact, use L…
…ocalDate Review round 1 on the BTD download support. - Reject a partial or reversed date range in the EbicsDownloadParams constructor, the one place every caller passes through. A half range used to be dropped when the request was built, on the launcher's legacy path without even a warning; a reversed range is schema-valid and comes back as EBICS_NO_DOWNLOAD_DATA_AVAILABLE, indistinguishable from a genuinely empty period. - Check every launcher argument before the first environment read, keystore access or bank call. It ran after loadUser/createUser and after --ini/--hia/--hpb, so an incomplete --btd order could still fire an INI request first, and INI is one-shot at most banks. - Carry the report period as LocalDate instead of Date. A calendar day read out of an instant depends on the machine's timezone: a UTC-midnight Date becomes the previous day west of UTC. The Date-taking overloads are kept and now document that. Adds createDateRange(LocalDate, LocalDate). - Upper-case the EBICS code list values (--service, --scope, --option, --container) so --container zip no longer aborts. Message names such as camt.053 stay as given. Tests 31 -> 36. New guards were each seen failing first. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for d1a02df - Browse repository at this point
Copy the full SHA d1a02dfView commit details
Commits on Aug 25, 2026
-
Merge pull request #52 from ebics-java/btd-download
feat(h005): support BTD download orders with service params and date range
Configuration menu - View commit details
-
Copy full SHA for 5563d62 - Browse repository at this point
Copy the full SHA 5563d62View commit details -
make getRootDir configurable via system property
- add fetchFile with defaultUser
Configuration menu - View commit details
-
Copy full SHA for fcac99a - Browse repository at this point
Copy the full SHA fcac99aView commit details -
Merge pull request #51 from ebics-java/jdk-http-client
refactor: replace Apache HttpClient with JDK java.net.http.HttpClient
Configuration menu - View commit details
-
Copy full SHA for 95483cc - Browse repository at this point
Copy the full SHA 95483ccView commit details -
Configuration menu - View commit details
-
Copy full SHA for 9e45631 - Browse repository at this point
Copy the full SHA 9e45631View commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff f537b24...9e45631