-* separate security into product and test where test depends on JPA 2.0 implementations
- and test is not deployed to the central maven repo.
-* move codestyle to separate svn project.
+* DatabaseUtils: deletion of tables must be more generic
+ First drop all constraints then drop all tables.
+ Or use JPA to drop the tables but that is a short-term solution
+* Get rid of use of detached objects in security
+ - Use only basic types in UserAdministration
+ - Put API in separate package
* add cdi subproject
-* refactor: Create jpa subproject with separate subprojects for api, hibernate,
- toplink-essentials and eclipselink
- Each subproject contains the required repo settings
* update mythtv project for java ee 6
-* add schemagen for user management part.
* reimplement photos application using wicket
-* JPA 2.0 implementation for security.
* change tracking for all projects with changes plugin
* maven sites for each subproject accessible through wamblee.org
* overview pages for separate areas
-* create passwords application
+* create user mgt application
*/
package org.wamblee.support.jndi;
-import static junit.framework.Assert.assertEquals;
+import static junit.framework.Assert.*;
import javax.naming.InitialContext;
+import javax.naming.NameNotFoundException;
import javax.naming.NamingException;
import org.junit.After;
import org.junit.Before;
import org.junit.Test;
-import org.wamblee.support.jndi.StubInitialContextFactory;
public class StubInitiaContextFactoryTest {
assertEquals("hallo", obj);
}
+ @Test(expected = NameNotFoundException.class)
+ public void testLookupFails() throws Exception {
+ StubInitialContextFactory.register();
+
+ InitialContext ctx = new InitialContext();
+ Object obj = ctx.lookup("a/b");
+ }
}