Call me the Apache Police if you like, but... We need to keep the discussions on this list focused on Apache Beehive, not Q&A about BEA's Workshop product. Questions that are specific to Workshop should go to: http://forums.bea.com/bea/category.jspa?categoryID=2005
There's obviously a lot of overlap here when it comes to the Workshop runtime; so it might be fair to use this list to help someone familiar with Workshop 8.1 to get up to speed with Beehive, but questions about the Workshop IDE should be directed to the BEA-focused mailing list. Cliff Mike Foster wrote on Thursday, October 14, 2004 9:50 AM: > Bala, > > I can speak to this in Workshop. Within the IDE, controls have 3 > states: > > 1) Unavailable -- not on the IDE classpath, not on the Insert menu > > 2) Available -- on the IDE classpath, may or may not be on the server > classpath. Insert can do one of 2 things -- a) Add the control jar > to the libraries of the application, putting it on the app > classloader b) Use the control jar from the system classloader, > assuming it's already on the server classpath > > 3) Installed -- generally this refers to 3rd party or custom > deliverable controls that get installed into the application > libraries > > When you select the default WebApp in the IDE, nothing special is > happening to "add" unwanted controls. It's just that those controls > are on the default WLW system classpath. > > Within Beehive, (and WLW 9.0) we will resolve this problem by tying > control binaries together in a more logical manner. I mentioned > before the concept of a ControlHaus Control "Pack". Initially, > should we release the 4 controls mentioned below, I'd propose a "SOA > Control Pack", and a "J2EE Control Pack": > > SOA Control Pack -- DB Control, Web Service Control (establishing > feature completeness of Beehive and Controls as an SOA framework) > J2EE Control Pack -- EJB Control, JMS Control (not specific to > WebLogic Server) > > These will be separate jars that can be added/removed from your > classpath as you see fit. > > -Mike > -----Original Message----- > From: Bala Sankar [mailto:[EMAIL PROTECTED] > Sent: Thursday, October 14, 2004 9:28 AM > To: Beehive Developers > Subject: RE: Data Control > > > Hi All, > > Our application is a simple web application with DataBase Control. > We don't need any EJB, JMS control. > We try to develop our application using WebLogic Workshop and deploy > it > to > The simple Servlet Containers like Weblogic Express. > > We are facing one big issue here. > As soon as we select a default WebApp in the Workshop, it adds all the > EJB, Timer & JMS Controls as default. > > This should be taken care of. > > We should be able to develop application to be deployed on Tomcat > without any EJB, JMS controls attached to it. > > Thanks > Bala > > -----Original Message----- > From: Ken Tam [mailto:[EMAIL PROTECTED] > Sent: Thursday, October 14, 2004 9:23 AM > To: Beehive Developers > Subject: RE: Data Control > > +1 > >> -----Original Message----- >> From: Mike Foster >> Sent: Thursday, October 14, 2004 9:13 AM >> To: Beehive Developers >> Subject: RE: Data Control >> >> Hi Bob, >> >> Agreed that the Controls runtime is not as useful without >> some core controls out of the box. I think shipping at least >> a DB control and a Web Service control in the Beehive >> distribution is a must, with EJB and JMS controls a close >> tier-two priority. For ApacheCon, I don't think we can >> deliver these in time, but we should start discussing a >> development and packaging strategy for Controls that should >> be part of the core. >> >> I know that BEA is interested in donating the 8.1 system >> controls code and continuing feature work for it in open >> source. This work should probably go on outside of Apache. >> It's a perfect fit for http://www.controlhaus.com. If we use >> ControlHaus for this, it also bootstraps that community as a >> place for anyone (not just Beehive committers) to do Control >> development. We'll have a place to point developers to when >> they come to us saying -- "I think the idea of a <foo> >> Control is great". Then, as a Beehive community, we can >> define some rules for inclusion of certain ControlHaus >> controls, or "packs" of them into the base Beehive distribution. >> >> If people like this idea, I'll write up a formal proposal, >> and circulate it. >> >> -Mike >> >> -----Original Message----- >> From: Bob Li [mailto:[EMAIL PROTECTED] >> Sent: Thursday, October 14, 2004 6:42 AM >> To: [email protected] >> Subject: Data Control >> >> >> Hi guys, >> >> I developed a web application by using WebLogic 8.1 Workshop >> and deployed to the 8.1 Platform. I am very amazed by how >> easy it is to develop by using Java Control and Page Flow >> technology especially the Data Control. That's why I come to >> Beehive site. >> >> But at this moment I feel it is almost useless because there >> is no Data Control here. If I have to write my own DAO >> classes by using JDBC API, why not I just write my own EJB classes? >> >> So is there any plan to include the Data Control into Beehive >> project? >> >> Regards, >> Bob >> >> >> >> _______________________________ >> Do you Yahoo!? >> Declare Yourself - Register online to vote today! >> http://vote.yahoo.com
