| Hamilton, G., ed.: JavaBeans. Sun Microsystems, http://java.sun.com/beans/ (1997) |
....formulations of the SDH dimensioning problem. Future Goals By keeping each of our user interface components self contained, it is our intention that future versions of the software will cornform to one of the standard component architecures such as JavaBeans, Microsoft ActiveX or OpenDoc [12]. This will give us a toolkit of components which can be easily integrated with third party products such as spreadsheets or databases. We will also look at the possibility of using a relational database schema [6] to forrealize the storage of data connected with the model, as although our model ....
HAMILTON, G. (1997). JavaBeans. White paper, Sun Microsystems.
....asynchronous method invocations. Several extensions to Java have been proposed which enrich Java with a high level data and or task parallel programming model [39, 41, 60, 112,119, 125, 160, 182] Recently, higher level component and parallelism concepts have been introduced to Java. JavaBeans [103] define a software component model for Java that allows a high level management of coarse grained components as building blocks of an application. JavaSpaces [176] support high level distributed computing by introducing a Linda like shared object space. 7.3.1.2 Language Extensions High ....
G. Hamilton (Editor). JavaBeans V 1.01. SUN Microsystems, 1997.
....The last of these options allows the 3D environment developers to bundle a custom GUI with their application. A user s palmtop can then receive the GUI plug in automatically when first stepping into the VR system. The plug ins loaded by the Java GUI are implemented as JavaBeans (Beans) [5]. The Beans fall into one of four categories: 1. Service Beans 2. Viewer Beans 3. Panel Beans 4. Generic Beans Figure 1 Stuff in VR Figure 1 Palmtop in an immersive environment Service Beans encapsulate functionality that may be useful to core elements of the Tweek Java GUI or to ....
G. Hamilton (ed.), JavaBeans 1.01 Specification, Sun Microsystems, Mountain View, CA, 1997.
....followed by a receiving phase, the sequence of updates for the sending phase and the summary version for the subsequent receiving phase could be combined in one SyncMessage object. SyncMessage objects would be transmitted reliably through a wireless implementation of the Java Message Service API [Hap98] that the MNCRS working group on mobile communication recommended be supported on every MNCRS platform. A synchronization protocol can be built on top of HTTP. The principal attractions of HTTP are that it is ubiquitous and that it can pass through firewalls. Synchronization messages might be ....
Hamilton, Graham, ed. JavaBeans, version 1.01. Sun Microsystems, July 24, 1997. <URL: http://java.sun.com/beans/docs/beans.101.pdf>
....data replication, distributed mouse pointers etc. without re engineering the involved applications and extending the corresponding component specifications. OLE and OpenDoc are primary designed for compound documents, there is no support for static component integration. Sun s JavaBeans concept [6] takes up the above ideas and offers an open and flexible framework to develop components or to use third party components in your own Java applications. It is easy to follow a Bean s specification and to realise any kind of objects with a Bean, including objects for compound documents, but also ....
Hamilton G, Java Beans, Sun Microsystems, 1997
....through a WWW browser. Data is stored in a Lotus Notes server, and distributed sites use a replication strategy. Domino includes development tools for workflow development and tool integration, and workflows are actually deployed as applications. Domino s support for Java and Java components [11] allows for some post workflow deployment evolution by allowing the presentation or view of the workflow to be changed. However, the underlying workflow model typically does not evolve once the workflow application has been deployed. Domino provides some WWW interfaces for manipulating and ....
G. Hamilton, Ed. JavaBeans, revision 1.01. Sun Microsystems, July 1997. http://java.sun.com/beans/spec.html
....basis computation do, but which will use the scripting access to our parallel Grobner solver and the fractal Grobner walk component to perform the computations instead of using a local sequential computation. 3. 4 Use of Java Beans Currently, we have not provided our Java components as Java Beans [17] but as simple applets and stand alone Java programs and Java class libraries. Using Java Beans for graphical user interface had the advantage that frequent users could store their own default settings instead of using the ones provided by us. However, there are few default settings independent of ....
HAMILTON, G. JavaBeans. Sun Microsystems, July 1997. For Version 1.01. http:// java.sun.com/beans/.
....calls. Precompiling results can then simply be translated by the original Java compiler, thus the Java utilities can still be used. Addressing another direction, next versions of DreamTeam will make component concepts available for shared applications. We carefully examined Java s Beans concept [Hamilton 97] but in our opinion Beans cannot simply be made shareable in synchronous sessions. Beans are small isolated programs which offer a number of methods. The Bean developer determines which implementation details are made visible to the outside world. For our aims, it is necessary for a component to ....
Hamilton, G. (ed) (1997): Java Beans, Sun Microsystems, 1997
No context found.
Hamilton, G., ed.: JavaBeans. Sun Microsystems, http://java.sun.com/beans/ (1997)
No context found.
Hamilton, G.: JavaBeans 1.01 Specification, Sun Microsystems (1997)
No context found.
Hamilton, G., ed.: JavaBeans. Sun Microsystems, http://java.sun.com/beans/ (1997)
No context found.
Graham Hamilton, editor. JavaBeans. Sun Microsystems, http://- java.sun.com/beans/, July 1997.
No context found.
Graham Hamilton, editor. JavaBeans. Sun Microsystems, http://java.sun.com/- beans/, July 1997.
No context found.
Hamilton, G., ed.: JavaBeans. Sun Microsystems, http://java.sun.com/beans/ (1997)
No context found.
G. Hamilton, editor. JavaBeans. Sun Microsystems, http://- java.sun.com/beans/, July 1997.
No context found.
Graham Hamilton Ed., JavaBeans, Sun Microsystems, java.sun.com/beans
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC