Jerry
It looks like the export did not export the data in the proper order. You are
trying to put mail into the mail table that is assigned to mailboxes that do
not exist yet. Three options:
1, create ‘dummy mailboxes’ for those messages to fall into. This may be the
faster workaround for the
Thanks so much for all of the advice. I think I've got a resolution.
1) First misassumption... mySQL makes no attempt to order tables based
on foreign key dependency. I just assumed the tables would be ordered
correctly (bad habit assuming). But due to possible cyclic
dependencies, mySQ
Nice,
Thanks for the feedback!
I believe writing a short blog-post that we could then share with the
community, once you get this up and running will be really valuable.
Regards,
Benoit
On 17/09/2019 00:27, Jerry Malcolm wrote:
> Thanks so much for all of the advice. I think I've got a resolu
Absolutely... will do. If I survive :-)
On 9/16/2019 9:24 PM, Tellier Benoit wrote:
Nice,
Thanks for the feedback!
I believe writing a short blog-post that we could then share with the
community, once you get this up and running will be really valuable.
Regards,
Benoit
On 17/09/2019 00
A couple of my mailets need to access a different database other than
the base james db. I've got the main db set up in the
james-database.properties file. Currently I'm just hardcoding the
database connection to the other db in the mailet. Just curious if
there's a better architected proces
Hi Jerry,
Are you speaking of JDBC mailets (whiteList for instance)
These mailets are currently deprecated (or will be) as they hard code
their database, are not standard, not tested and not documented. Note
that they are considered as 'experimental' ( cf
http://james.apache.org/server/dev-provid
No the main mailet in question is 100% custom. It is a mailet that
decides what folder to put the mail item in. I access a completely
separate client database and determine if the sender is a client vs. a
vendor vs. an employee and store the mail in a different folder based on
the result. Th
The fun just keeps happening I was finally able to bring up the new
installation of James 3.3.0 with a sandbox copy of my real database. I
created a new test email account in James and configured it in my local
Thunderbird instance. So far, so good. But now every time Thunderbird
contacts
Something that might be relevant to this problem, but the messages make
no more sense than the other one... A little earlier in the log, I have
a bunch of these messages:
174 James INFO [main] openjpa.Runtime - Starting OpenJPA 3.0.0
207 James INFO [main] openjpa.jdbc.JDBC - Using dicti
If I were you, I'd use only mailet configuration properties for this.
On 17/09/2019 10:18, Jerry Malcolm wrote:
> No the main mailet in question is 100% custom. It is a mailet that
> decides what folder to put the mail item in. I access a completely
> separate client database and determine if th
Hi Jerry,
To explain it shortly:
1. In OpenJPA NamedQuery are directly attached to the POJO being
persited, here AbstractJPAMailboxMessage
2. Using these annotations (named query) openjpa plugin enhance code
upon compilation
3. Then the magic happens
Here because openjpa do not load correctly
11 matches
Mail list logo