Releases: phax/phase4
Releases · phax/phase4
phase4 0.9.11
- Updated to ph-web 9.1.10
- Propagating processing errors to the client (see issue #30) - thanks to https://github.com/RovoMe
- Replaced the unchecked
AS4BadRequestException
with the checkedPhase4Exception
(backwards incompatible change)
Dependencies required:
- ph-bc/ph-collection/ph-commons/ph-dao/ph-datetime/ph-jaxb/ph-json/ph-scopes/ph-security/ph-settings/ph-xml 9.3.9
- ph-xsds-xmldsig 2.2.3
- ph-http/ph-httpclient/ph-mail/ph-network/ph-servlet/ph-useragent/ph-web 9.1.10
- ph-oton-app/ph-oton-audit/ph-oton-html/ph-oton-security 8.2.2
- ph-css 6.2.1
- ph-masterdata/ph-tenancy 6.1.3
- peppol-commons/peppol-id/peppol-sbdh/peppol-smp-client 8.0.2
- peppol-bdve-peppol 5.2.6
- jakarta.mail 1.6.4
- jakarta.activation 1.2.1
- httpclient 4.5.11
- BouncyCastle 1.64
- WSS4J 2.2.4
- XMLSec 2.1.4
phase4 0.9.10
- Fixed a stupid error in the demo code that prohibits the correct receiver check activation - see 796c054 for the resolution
- Invoking the
AS4RequestHandler
error consumer also on asynchronous processing - Extended the error consumer interface of
AS4RequestHandler
fromConsumer
toIAS4RequestHandlerErrorConsumer
(backwards incompatible change) - Extended the message metadata class
AS4IncomingMessageMetadata
- Updated to ph-web 9.1.9
Dependencies required:
- ph-bc/ph-collection/ph-commons/ph-dao/ph-datetime/ph-jaxb/ph-json/ph-scopes/ph-security/ph-settings/ph-xml 9.3.9
- ph-xsds-xmldsig 2.2.3
- ph-http/ph-httpclient/ph-mail/ph-network/ph-servlet/ph-useragent/ph-web 9.1.9
- ph-oton-app/ph-oton-audit/ph-oton-html/ph-oton-security 8.2.2
- ph-css 6.2.0
- ph-masterdata/ph-tenancy 6.1.3
- peppol-commons/peppol-id/peppol-sbdh/peppol-smp-client 8.0.1
- peppol-bdve-peppol 5.2.6
- jakarta.mail 1.6.4
- jakarta.activation 1.2.1
- httpclient 4.5.11
- BouncyCastle 1.64
- WSS4J 2.2.4
- XMLSec 2.1.4
phase4 0.9.9
- Removed the methods deprecated in v0.9.8
- Updated to peppol-commons 8.x
- Extended
Phase4PeppolEndpointDetailProviderSMP
API - Added new subproject
phase4-peppol-server-webapp
with a demo server for receiving messages via Peppol - Extended
IAS4IncomingDumper
API with an "end request" notifier - The asynchronous response now also uses the outgoing dumper
- Merged two methods in class
IAS4ResponseAbstraction
into one (backwards incompatible change) - Invoking the outgoing dumper also for responses sent for incoming messages
Dependencies required:
- ph-bc/ph-collection/ph-commons/ph-dao/ph-datetime/ph-jaxb/ph-json/ph-scopes/ph-security/ph-settings/ph-xml 9.3.9
- ph-xsds-xmldsig 2.2.3
- ph-http/ph-httpclient/ph-mail/ph-network/ph-servlet/ph-useragent/ph-web 9.1.6
- ph-oton-app/ph-oton-audit/ph-oton-html/ph-oton-security 8.2.1
- ph-css 6.2.0
- ph-masterdata/ph-tenancy 6.1.3
- peppol-commons/peppol-id/peppol-sbdh/peppol-smp-client 8.0.0
- peppol-bdve-peppol 5.2.5
- jakarta.mail 1.6.4
- jakarta.activation 1.2.1
- httpclient 4.5.11
- BouncyCastle 1.64
- WSS4J 2.2.4
- XMLSec 2.1.4
phase4 0.9.8
- Added possibility to use external message ID in Peppol client
- Added new classes
AS4IncomingDumperSingleUse
andAS4OutgoingDumperSingleUse
for easier per-call dumping - Peppol client now has an additional callback to retrieve the AS4 URL where the message is send to
- No longer throwing an exception if
phase4.properties
is not available. Changed to a warning. - Added new class
AS4IncomingMessageMetadata
to hold metadata for each incoming message - The
IAS4ServletMessageProcessorSPI
API was modified to now includeIAS4IncomingMessageMetadata
(backwards incompatible change) - The
IPhase4PeppolIncomingSBDHandlerSPI
API was modified to now includeIAS4IncomingMessageMetadata
as well asPeppolSBDHDocument
,Ebms3UserMessage
andIAS4MessageState
(backwards incompatible change) - The
IAS4IncomingDumper
API was modified to now includeIAS4IncomingMessageMetadata
(backwards incompatible change) - Added the original (potentially encrypted) SOAP document into
IAS4MessageState
- Renamed type
ESOAPVersion
toESoapVersion
(backwards incompatible change) - Method names in
IAS4ClientBuildMessageCallback
changed to useSoap
instead ofSOAP
- Extended
IAS4ServletMessageProcessorSPI
with a possibility to process the response message send out - Renamed
AS4CryptoFactory
toAS4CryptoFactoryPropertiesFile
(backwards incompatible change)
Dependencies required:
- ph-bc/ph-collection/ph-commons/ph-dao/ph-datetime/ph-jaxb/ph-json/ph-scopes/ph-security/ph-settings/ph-xml 9.3.9
- ph-xsds-xmldsig 2.2.3
- ph-http/ph-httpclient/ph-mail/ph-network/ph-servlet/ph-useragent/ph-web 9.1.5
- ph-oton-app/ph-oton-audit/ph-oton-html/ph-oton-security 8.2.1
- ph-css 6.2.0
- ph-masterdata/ph-tenancy 6.1.3
- peppol-commons/peppol-id/peppol-sbdh/peppol-smp-client 7.0.6
- peppol-bdve-peppol 5.2.4
- jakarta.mail 1.6.4
- jakarta.activation 1.2.1
- httpclient 4.5.10
- BouncyCastle 1.64
- WSS4J 2.2.4
- XMLSec 2.1.4
phase4 0.9.7
- Removed the default configuration files from
phase4-peppol-client
- Added the new submodule
phase4-peppol-servlet
with the Peppol specific receiving stuff - Extracted interface
IAS4Attachment
fromWSS4JAttachment
for read-only access - Fixed NPE when receiving an attachment without a "Content-ID"
- Removed all deprecated and unused methods from previous versions
- Extracted
IAS4CryptoFactory
interface for broader usage - Added possibility to use a preconfigured receiver AP certificate and endpoint URL for the Peppol client
- Changed
IPhase4PeppolValidatonResultHandler
to be an empty interface andPhase4PeppolValidatonResultHandler
is the default implementation - The base class of
Phase4PeppolException
changed fromException
toPhase4Exception
- Incoming messages are checked via against the values configured in class
Phase4PeppolServletConfiguration
- For security reasons the dependency to the XML pull parser "woodstox" was removed
- For security reasons the dependency to the DNS library "dnsjava" was removed
- Added the new class
AS4CryptoFactoryInMemoryKeyStore
that takes an in-memory key store and trust store (see issue #28) - Updated to peppol-commons 7.0.6 with more flexible SMP client API
SOAPHeaderElementProcessorRegistry
is no longer a singleton- The Peppol client can now handle Receipts that are MIME encoded
- The Peppol client now verifies the signatures of the response messages
- The Peppol client now honors the "incoming dumper" for the response messages
Dependencies required:
- ph-bc/ph-collection/ph-commons/ph-dao/ph-datetime/ph-jaxb/ph-json/ph-scopes/ph-security/ph-settings/ph-xml 9.3.9
- ph-xsds-xmldsig 2.2.3
- ph-http/ph-httpclient/ph-mail/ph-network/ph-servlet/ph-useragent/ph-web 9.1.5
- ph-oton-app/ph-oton-audit/ph-oton-html/ph-oton-security 8.2.1
- ph-css 6.2.0
- ph-masterdata/ph-tenancy 6.1.3
- peppol-commons/peppol-id/peppol-sbdh/peppol-smp-client 7.0.6
- peppol-bdve-peppol 5.2.4
- jakarta.mail 1.6.4
- jakarta.activation 1.2.1
- httpclient 4.5.10
- BouncyCastle 1.64
- WSS4J 2.2.4
- XMLSec 2.1.4
phase4 0.9.6
- Removed the "ExceptionCallback" from
Phase4PeppolSender
- Changed the data types of "ResponseConsumer" and "SignalMsgConsumer" from
Phase4PeppolSender
to be able to throw exception (binary incompatible change) - Added the possibility to configure the keystore without the need of having the
crypto.properties
file - Extracted interface
IMPCManager
fromMPCManager
and using it internally - Extracted interface
IPModeManager
fromPModeManager
and using it internally - The method
IPModeManager.validatePMode
now throws a checkedPModeValidationException
exception (incompatible change) - Added the possibility to customize the outgoing dumper in class
Phase4PeppolSender
- Added specific
Phase4PeppolSMPException
for SMP lookup errors (incompatible change) - Extracted interface
IAS4DuplicateManager
fromAS4DuplicateManager
and using it internally - Added the possibility to send pre-build SBDH messages (see issue #22) (binary incompatible change)
- Added support for creating in-memory managers only, using the system property
phase4.manager.inmemory
- Parameter type of
IAS4IncomingDumper.onNewRequest
changed toHttpHeaderMap
(incompatible change) - Made
AS4RequestHandler
usage more flexible to not solely rely on the Servlet API - New logo thanks to Maria Petritsopoulou - http://stirringpixels.com/
Dependencies required:
- ph-bc/ph-collection/ph-commons/ph-dao/ph-datetime/ph-jaxb/ph-json/ph-scopes/ph-security/ph-settings/ph-xml 9.3.9
- ph-xsds-xmldsig 2.2.3
- ph-http/ph-httpclient/ph-mail/ph-network/ph-servlet/ph-useragent/ph-web 9.1.5
- ph-oton-app/ph-oton-audit/ph-oton-html/ph-oton-security 8.2.1
- ph-css 6.2.0
- ph-masterdata/ph-tenancy 6.1.3
- peppol-commons/peppol-id/peppol-sbdh/peppol-smp-client 7.0.5
- peppol-bdve-peppol 5.2.2
- jakarta.mail 1.6.4
- jakarta.activation 1.2.1
- httpclient 4.5.10
- BouncyCastle 1.64
- WSS4J 2.2.4
- XMLSec 2.1.4
phase4 0.9.5
- Enforcing the usage of
Phase4PeppolSender.builder()
by making the main sending method private - Updated to peppol-commons 7.0.4 (moved classes
PeppolCerticateChecker
andEPeppolCertificateCheckResult
there) (incompatible change) - Replaced the Peppol client "certificate consumer" type to be
IPhase4PeppolCertificateCheckResultHandler
(incompatible change)
Dependencies required:
- ph-bc/ph-collection/ph-commons/ph-dao/ph-datetime/ph-jaxb/ph-json/ph-scopes/ph-security/ph-settings/ph-xml 9.3.8
- ph-xsds-xmldsig 2.2.3
- ph-http/ph-httpclient/ph-mail/ph-network/ph-servlet/ph-useragent/ph-web 9.1.4
- ph-oton-app/ph-oton-audit/ph-oton-html/ph-oton-security 8.2.1
- ph-css 6.2.0
- ph-masterdata/ph-tenancy 6.1.3
- peppol-commons/peppol-id/peppol-sbdh/peppol-smp-client 7.0.4
- peppol-bdve-peppol 5.1.15
- jakarta.mail 1.6.4
- jakarta.activation 1.2.1
- httpclient 4.5.10
- BouncyCastle 1.64
- WSS4J 2.2.4
- XMLSec 2.1.4
phase4 0.9.4
- Updated to ph-commons 9.3.8
- Added OCSP/CLR check for Peppol certificates
- Added support for validation of outgoing Peppol messages using the default Peppol Schematrons
- Extended the Peppol client API a bit for client side validation (see issue #19)
- Outgoing messages now have the User-Agent HTTP header set (see issue #20)
- Fixed a typo in the short name of
EBMS_FAILED_DECRYPTION
(see issue #21) - Added a new
Builder
class for the Peppol AS4 client - usePhase4PeppolSender.builder()
to get started
Dependencies required:
- ph-bc/ph-collection/ph-commons/ph-dao/ph-datetime/ph-jaxb/ph-json/ph-scopes/ph-security/ph-settings/ph-xml 9.3.8
- ph-xsds-xmldsig 2.2.3
- ph-http/ph-httpclient/ph-mail/ph-network/ph-servlet/ph-useragent/ph-web 9.1.4
- ph-oton-app/ph-oton-audit/ph-oton-html/ph-oton-security 8.2.1
- ph-css 6.2.0
- ph-masterdata/ph-tenancy 6.1.3
- peppol-commons/peppol-id/peppol-sbdh/peppol-smp-client 7.0.3
- peppol-bdve-peppol 5.1.15
- jakarta.mail 1.6.4
- jakarta.activation 1.2.1
- httpclient 4.5.10
- BouncyCastle 1.64
- WSS4J 2.2.4
- XMLSec 2.1.4
phase4 0.9.3
- Updated to peppol-commons 7.0.3
- Added new subproject
phase4-peppol-client
to easily send AS4 messages to PEPPOL - Fixed default initiator URL (see issue #18)
Dependencies required:
- ph-bc/ph-collection/ph-commons/ph-dao/ph-datetime/ph-jaxb/ph-json/ph-scopes/ph-security/ph-settings/ph-xml 9.3.7
- ph-xsds-xmldsig 2.2.3
- ph-http/ph-httpclient/ph-mail/ph-network/ph-servlet/ph-useragent/ph-web 9.1.4
- ph-oton-app/ph-oton-audit/ph-oton-html/ph-oton-security 8.2.1
- ph-css 6.2.0
- ph-masterdata/ph-tenancy 6.1.3
- peppol-commons/peppol-id/peppol-sbdh/peppol-smp-client 7.0.3
- jakarta.mail 1.6.4
- jakarta.activation 1.2.1
- httpclient 4.5.10
- BouncyCastle 1.63
- WSS4J 2.2.4
- XMLSec 2.1.4
phase4 0.9.2
- Fixed an invalid assumption in the PEPPOL PMode validator.
Dependencies required:
- ph-bc/ph-collection/ph-commons/ph-dao/ph-datetime/ph-jaxb/ph-json/ph-scopes/ph-security/ph-settings/ph-xml 9.3.7
- ph-xsds-xmldsig 2.2.3
- ph-http/ph-httpclient/ph-mail/ph-network/ph-servlet/ph-useragent/ph-web 9.1.3
- ph-oton-app/ph-oton-audit/ph-oton-html/ph-oton-security 8.2.0
- ph-css 6.2.0
- ph-masterdata/ph-tenancy 6.1.3
- javax.mail 1.6.2
- httpclient 4.5.8
- BouncyCastle 1.63
- WSS4J 2.2.4
- XMLSec 2.1.4