search

OxalisCommunity / oxalis

Oxalis - PEPPOL Access Point open source implementation - Core component
Other
129 stars 91 forks source link

Custom MessageRepository? #277

Closed ubrix closed 6 years ago

ubrix commented 7 years ago

Hello In oxalis-4.0.0-RC1 it’s possible to use the serviceLoader in MessageRepositoryFactory to use a custom MessageRepository. But this feature is removed in the RC2 branch. How do you setup a custom MessageRepository in RC2? RC1: oxalis/oxalis-commons/src/main/java/eu/peppol/persistence/RepositoryModule.java RC2: oxalis/oxalis-persistence/src/main/java/eu/peppol/persistence/guice/RepositoryModule.java

On a side note. When do you plan to release oxalis 4 final?

Best Regards

PeterOlausson65 commented 7 years ago

We also have an implementation which relies on the custom MessageRepository to persist inbound messages to an MQ queue. If this feature is removed, what will be the alternative to get inbound messages for processing in our integration system?

In the README file it is a bit confusing as it mentions: Persistence have been modularized so you can provide your own implementation if you need to send inbound messages to a message queue, a workflow engine, a document archive or others.

later it says: As of version 4.x Oxalis comes with the H2 SQL database embedded. In addition to the statistics, the message meta data is also stored into the database. The pluggable persistence has been removed.

What are the plans for persisting messages to be used in other systems?

I would also be interested to know more about the roadmap and planned release dates for the 4.x versions.

Best regards

steinarcook commented 7 years ago

The plan is to re-introduce this feature. It was removed because we were under the impression that nobody used it.

However, you are not the only one who have requested that this feature be returned to the code base :-)

Having said that, the new upcoming relase 4.0.0-RC2 is a major rewrite and will provide quite a few possibilities for writing your own plug-ins

  1. feb. 2017 kl. 08.37 skrev PeterOlausson65 notifications@github.com:

We also have an implementation which relies on the custom MessageRepository to persist inbound messages to an MQ queue. If this feature is removed, what will be the alternative to get inbound messages for processing in our integration system?

In the README file it is a bit confusing as it mentions: Persistence have been modularized so you can provide your own implementation if you need to send inbound messages to a message queue, a workflow engine, a document archive or others.

later it says: As of version 4.x Oxalis comes with the H2 SQL database embedded. In addition to the statistics, the message meta data is also stored into the database. The pluggable persistence has been removed.

What are the plans for persisting messages to be used in other systems?

I would also be interested to know more about the roadmap and planned release dates for the 4.x versions.

Best regards

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/difi/oxalis/issues/277#issuecomment-279629860, or mute the thread https://github.com/notifications/unsubscribe-auth/ABDq0dx9adcbb6Vd-hHI0vd4grdQmOPrks5rcVm2gaJpZM4LukC1.

Steinar Overbeck Cook Tlf: +47 90 66 57 93

klakegg commented 6 years ago

A new implementation of this feature was released in Oxalis 4.0.0.