About project

81-90 of 200Refresh
Tutorial
9

Step 6: Run the Java EE 6 Application

You can run the application now by right clicking the GuestServlet node (in the [Projects] window), selecting Run File, and then clicking OK (no need to change the servlet execution URI). Since we are using ObjectDB in embedded mode - the database file is created under the GlassFish directory (e.g
Tutorial
9

Step 6: Run the Java EE 6 Application

You can run the application now by right clicking the GuestServlet node (in the [Project Explorer] window) and selecting Run As > Run on Server > Finish: Since we are using ObjectDB in embedded mode - the database file is created under the GlassFish directory (e.g. at domains\domain1\eclipseApps
Tutorial
9

Step 6: Run the Web Application

You can run the application now by right clicking the GuestServlet node (in the [Project Explorer] window) and selecting Run As > Run on Server > Finish: Since we are using ObjectDB in embedded mode - the database file is created under the Tomcat directory. You can stop the Tomcat server and open
Tutorial
9

Step 6: Run the Web Application

You can run the application now by right clicking the GuestServlet node (in the [Projects] window), selecting Run File, and then clicking OK (no need to change the servlet execution URI). Since we are using ObjectDB in embedded mode - the database file is created under the Tomcat directory
Tutorial
9

Step 6: Set the Spring XML

node in the [Projects] window, select New > Other... and then choose the XML category, XML Document
Manual
9

What's next?

/JPA projects simply by modifying this sample program. Reading the Next Chapters
Issue
9

objectdb-2.6.9_06: Extended Persistence Context fails: 'Attempt to begin a new transaction when a transaction is active'

-B.tgz To reproduce the problem described below, simply download the test project, open in NetBeans8 ... -2.6.9_01. In the test case, only a single Project entity is used, and 2 project objects ... the building of 2 separate - usually large and complex - Projects, via the @Stateful ExtProjectBuilder
Issue
6

Explorer bug ? Objects seem to be missing from database in Class view, but are present as references

. It is marked knowingly as CRITICAL by me because it makes the ObjectDB system unusable for a real project ... it, which is just as bad. I attach a running project illustrating the problem, as well as screenshots. When the project runs it logs creation of objects. Please note that there are 2 Project objects, and note
Issue
5

After using the enhancer, Lazy loaded collections are no longer loading. They are set as null

, CascadeType.PERSIST}, mappedBy="account", fetch = FetchType.LAZY) @JoinColumn(name = "project_id", unique=true, nullable=false, updatable=false) protected List<Project> projects = new ArrayList<>(); public List<Project> getProjects() { return projects; } public void
Issue
5

Once served to JSF page via @EJB query bean, many list fields are null (but same query ok after fresh persist in @PostConstruct)

($i,"element",e); log_info($i,"element.project",e.getProject()); List ... =TestDeepValues][project=TEST: project 1][id=45][name=TEST: test deep values]) INFO: ConfigBean []: testQuery: element.project([class=Project][id=1][name=TEST: project 1]) INFO: ConfigBean []: testQuery