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:||Shorten component edit-deploy-test cycle|
|Product:||obsolete||Reporter:||_ edwingo <edwingo>|
|Component:||visualweb||Assignee:||_ edwingo <edwingo>|
|Issue Type:||ENHANCEMENT||Exception Reporter:|
|Bug Depends on:|
Description _ edwingo 2007-02-01 22:34:33 UTC
Currently, there are tedious and manual steps required to develop a component for use in VWP (Visual Web Pack). This task will shorten the edit-deploy-test cycle for a component.
Comment 1 _ edwingo 2007-02-02 21:47:13 UTC
Until this can be fixed, here is a workaround. It assumes NetBeans 5.5 with VWP as the IDE. 1. Create a Library project (LP) that produces a complib with your component 2. Create a new Library Definition from the NB Library Manager of type "Component Library" * Add the runtime jars to the "classpath" tab. Use the output of the complib build in prior step. * Add the designtime jars to the "design" tab, you can optionally also add source and javadoc. 3. Next create a test app to test your component: 1. Import complib into IDE 2. Create a new test app Visual Web project (VP) 3. Add the imported component library to the project so components appear on the palette 4. Add the component to the test app 5. See a problem in the component that you want to fix 6. Remove the component library in the Projects Window 7. Add a "Library Reference" to the project with the Library Definition you created above 8. The VP project should now appear as before except that the palette items are missing 4. Make changes to the components in the complib project LP, build it, and the test app project WP should reflect those changes.