| Hi Ramsey,
was think in the same lines. Started a test in main() right before calling EXRApplication.main(). Seems to work in dev mode. Will test in prod. Unfortunately (well, no really) I’ll be on vacation so I can only finish my work when I’m back. Will report here.
Jürgen,
That method was my entry point into searching for a solution. But this requires to dabble with the Wonder code itself which I dit not want to do, at least not for a start. Might get back to it after my vacation.
Thanks all that responded. Even if someone cannot provide an out-of-the-box solution discussing things here is extremely valuable. ---markus---
Have you tried scanning for your additional model names in a static{} block in your application class? That should happen very early and seems like it should have enough access to the classpath to find everything. I never really used additional model names and just used the d2w.d2wmodel/user.d2wmodel files.
From: WebObjects & WOnder Development on behalf of Markus Ruggiero (rucotec) Sent: Thursday, February 23, 2023 4:58 AM To: WebObjects & WOnder Development Subject: [WO-DEV] Re: Load additional D2W models?
Please tick [ ] Nobody knows anything [ ] Nobody ever had such an idea and does not care [ ] Nobody out there anymore
I found this property “er.directtoweb.ERD2WModel.additionalModelNames” that can be use to load additional D2W model files. I want to make this property dynamic so that its list of model names is built from a directory scan of the resources folder (or a subfolder) and all models found are loaded. This would allow to have models built around some grouping criteria like e.g. per entity without having to manually maintain the list of names in the properties file. I am in a prototype phase where I play extensively with a rather extensive EOModel, adding and removing entities. Such functionality would be great to have.
Anyone done something like this? When during app startup would be a good time to build this list? I think it must be done before D2W is initialized. Probably application.run() right before calling super.run() might already be too late?
Open for any tip, idea, help, code snippets, whatever.
Thanks a lot
---markus---
Markus Ruggiero
4051 Basel / Switzerland mobile +41 79 508 4701
Confidentiality Notice: This email, including all attachments and replies thereto, are covered by the Electronic Communications Privacy Act, 18 U.S.C. Sections 2510-2521 and are legally privileged. This information is confidential, and intended only for the use of the individuals or entities named above. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or the taking of any action in reliance on the contents of this transmitted information is strictly prohibited. Please notify us if you have received this transmission in error. Thank you.
Markus Ruggiero
4051 Basel / Switzerland mobile +41 79 508 4701
|