You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Although I still think using ejb-jar.xml deployment descriptors to reconfigure automatic (@schedule) timers should be a rare one-off, because of the complexity it re-introduces in Java EE, now that it's out in public documentation, I want to make sure the docs are as accurate and clear as possible, while we're thinking of it.
There's an additional way to besides compiling the app to inject an edited ejb-jar.xml file into the application.
Also when I was assembling the documentation, I inserted the wrong sample file, which had a version problem, which would prevent the dataverse war file from deploying if the ejb-jar.xml file was inserted. I discovered this while re-testing some things after some issues had come up with the merge
The text was updated successfully, but these errors were encountered:
Although I still think using ejb-jar.xml deployment descriptors to reconfigure automatic (@schedule) timers should be a rare one-off, because of the complexity it re-introduces in Java EE, now that it's out in public documentation, I want to make sure the docs are as accurate and clear as possible, while we're thinking of it.
There's an additional way to besides compiling the app to inject an edited ejb-jar.xml file into the application.
Also when I was assembling the documentation, I inserted the wrong sample file, which had a version problem, which would prevent the dataverse war file from deploying if the ejb-jar.xml file was inserted. I discovered this while re-testing some things after some issues had come up with the merge
The text was updated successfully, but these errors were encountered: