This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | Import Creator 2 projects | ||
---|---|---|---|
Product: | obsolete | Reporter: | Mark Dey <markdey> |
Component: | visualweb | Assignee: | _ potingwu <potingwu> |
Status: | RESOLVED FIXED | ||
Severity: | blocker | CC: | jbaker, sanjaydhamankar |
Priority: | P1 | Keywords: | UI, UMBRELLA |
Version: | 5.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Exception Reporter: | |
Bug Depends on: | |||
Bug Blocks: | 90450 |
Description
Mark Dey
2006-12-01 19:54:45 UTC
6.0M8 is for importing the project itself. 6.0M9 will be for 'auto-resolve', 1. data source 2. web service 3. EJB Creator 2 users must migrate to Creator 2 Update 1 before importing their project into NetBeans 6. Importing Creator 2 Update 1 Web Application projects that connect to databases works nearly seamlessly (little or no user action) using Milestone 9 builds. For Milestone 10, importing the database projects will be completely seamless. With the exception of supporting Projects that contain Web Services, EJBs or are Portlet application. Others can comment here. In M9, importing projects that contain databases isn't completely seamless if the user doesn't open any pages in the project. In this case the project doesn't get modeled so dataconnectivity isn't aware of any data sources in the project. For M10, modeling will be done as a background task, when the project opens Done! Minor issues will be handled by the sub-components issues. This is an umbrella task and there are some sub-tasks to do for M10 (see dependency list). I don't think this task should be marked as Resolved. I misunderstood this purpose of this issue. Please disregard my previous comments |