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: | Visual EJB consumption for visual web apps | ||
|---|---|---|---|
| Product: | obsolete | Reporter: | Mark Dey <markdey> |
| Component: | visualweb | Assignee: | _ edwingo <edwingo> |
| Status: | RESOLVED FIXED | ||
| Severity: | blocker | CC: | edwingo |
| 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 20:32:48 UTC
hi! i'm really looking forward to this feature as it will make some web development we need to do much more streamlined. i'm guessing M9 will be out some time in the next week, is there any chance that this feature will make it? is it going into the daily builds? (i'm not even sure that there are daily builds of the VWP but anyway) thanks alot, matt EJB 2.1 D & D consumption is targetted for M10. Ouch, just noticed the 2.1 bit. Does that mean EJB3 won't be supported? Is it targeted for a later release? As I understand it, the goal is to migrate Creator 2 users to NetBeans 6. This means that EJB 2.1 consumption support in Creator 2 needs to be in NB6. Not sure about future plans. It either depends on management priorities or if someone wants to implement it on their own as it is an open source project. By EJB 3 support, could you explain what scenarios in particular you want supported? This task tracks migration of Creator 2 EJB 2.1 consumption in NetBeans 6. As for EJB 3 support, I believe NB6 has the "Call EJB" action in web projects context menu. Visual Consumption of EJB 2.1 in Visual web apps 90455 is supported in NetBeans 6 as a migration path for Creator users. Creator ships with a bundled Sun App Server where web apps are test deployed to. This feature allows the web app to consume Session EJBs hosted on other app servers such as Sun, WebLogic, and WebSphere; however a limitation still remains, the web app itself needs to be test deployed on a Sun app server for the automatic configuration to work. If you want to host the web app in another app server, you must manually configure the EJB reference to JNDI binding which is container specific. When deploying your web app on a production server using the export war feature, this manual configuration step is part of the Java EE deployment process which is container specific. Hi guys, Sorry it was probably me not thinking through how it would work. I was thinking that the Visual Web component would need to understand the annotations from an EJB3 entity to define the data mapping but it will be loading the data model based on a deployed session bean I guess. I also wasn't sure how different an EJB3 session bean looked to the container. Judging by your confusion as to my question I'm guessing there's a cross-compatibility there. I've never really looked into the low levels of what goes on down there, all I know is EJB3 is 1000 times easier to code and if I can derive data models for visual components based on my EJB3 beans then it will be happy days indeed. Cheers, Matt matt_tricks: It sounds like you want to use JPA and Entity Beans. I know there are people who have written apps that do this and netbeans supports JPA and EJB3 OR mapping. I suggest you post to nbusers or do searches on the subject. I think there is a tutorial that shows how netbeans can generate Entity Beans from a DB. HTH. |