Did you ever wonder why your classes do not show a hint when hovering over it in your eclipse IDE?
Here is a quick solution to make your life a lot easier:
Just download the domino-javadoc-0.4-out.zip file linked from the following url, unzip it into any convenient directory (or generate the doc yourself, using the provided instructions), and link the newly created Notes7-pseudo-javadoc.zip to your Notes.jar by right-clicking it and selecting "Properties" in eclipse.
Link: http://domino-javadoc.sourceforge.net/
Lotus Domino / Notes and Java Enterprise in-depth technical insights, notes and nice-to know gems.
2/28/2012
11/28/2011
How To Set Dojo Timeout for Partial Updates and AJAX Calls
I recently had a hard time searching for a possibility to set the default for a call done by an XPage client side
script.
XPages-Dojo default is somewhere around 6 seconds (infinite for normal dojo), which is just not enough in some places (be sure to include a loading bar or dojo standby to signal the user you are still doing something for them in the backend).
After some research i found this link, whick is exactly what i needed, and now im reblogging it here to give it some more keywords for you to find it if you need it (because i did not).
The solution is: just add the following line to your XSP.addOnLoad() function:
XSP.submitLatency = 600 * 1000; // latency in milliseconds
The solution is: just add the following line to your XSP.addOnLoad() function:
XSP.submitLatency = 600 * 1000; // latency in milliseconds
9/27/2011
JPA, Eclipselink and Lotus Domino Integration
You might be curious, what my last post about doing geo-spatial queries in JPA has to do with Lotus Domino development - here is the answer, and a question:
After developing the classes for my spatial search along a specified route (tested perfectly well in the eclipse environment), now is the time to intregrate this beast with Lotus Domino server - this should be pretty simple - but only on first sight.
JPA stores its configuration inside a persistence.xml file in the /META-INF directory - but this does not seem to be available to the runtime - causing this error:
No Persistence provider for EntityManager named myPersistenceUnit
(LDD Bug Report X-Pages Forum Report)
Now - after some searching, it could be done theoretically (but does not work for me, and its russian, too - google translates it into a funny description):
Lotus Domino + JPA + GUICE
A rough description of the procedure:
grant {
permission java.security.AllPermission;
};
The downsides:
If you do all this, it works (but is still very hard to handle while develop, test and deploy), very slow to compile because all data has to be put to and from the database, not secure and not really possible to deploy in a productive customer environment.
Addidtionally, the whole server has to be restarted for every tiny change.
Is there any other possibility, to deploy this via jar?
So i guess it's time to set up a Glassfish Server along Domino to make it happen in a convenient way.
More work to do...
After developing the classes for my spatial search along a specified route (tested perfectly well in the eclipse environment), now is the time to intregrate this beast with Lotus Domino server - this should be pretty simple - but only on first sight.
JPA stores its configuration inside a persistence.xml file in the /META-INF directory - but this does not seem to be available to the runtime - causing this error:
No Persistence provider for EntityManager named myPersistenceUnit
(LDD Bug Report X-Pages Forum Report)
Now - after some searching, it could be done theoretically (but does not work for me, and its russian, too - google translates it into a funny description):
Lotus Domino + JPA + GUICE
A rough description of the procedure:
- Use Guice to inject your dependencies to the JPA Framework Implementation (eclipse in this case). Put all the code into a WEB-INF/src folder which is in the build path.
- Put the persistence.xml and orm.xml into WEB-IF/src/META-INF
- Put all the libraries you need into WEB-INF/lib
- Remove all security restrictions from java.policy in c:\Domino\jvm\lib\security by using
grant {
permission java.security.AllPermission;
};
The downsides:
If you do all this, it works (but is still very hard to handle while develop, test and deploy), very slow to compile because all data has to be put to and from the database, not secure and not really possible to deploy in a productive customer environment.
Addidtionally, the whole server has to be restarted for every tiny change.
Is there any other possibility, to deploy this via jar?
So i guess it's time to set up a Glassfish Server along Domino to make it happen in a convenient way.
More work to do...
Subscribe to:
Posts (Atom)