4th International Conference on Principles and Practices ... - MADOC

More documents

Recommendations

Info

Figure 10: Assignment of Permissions and Roles using the RBAC Management Mode Version 1.0.1, http://www.jcp.org/en/jsr/detailid= 12, 2004. [7] Java Community Process. JSR-243: Java Data Objects 2.0 - An Extension to the JDO specification, Final Release, Version 2.0, http://www.jcp.org/en/ jsr/detailid=243, 2006. [8] A. Korthaus and M. Merz. A Critical Analysis of JDO in the Context of J2EE. In A.-A. Ban, H. Arabnia, and M. Youngsong, editors, <strong>International</strong> <strong>Conference</strong> on Software Engineering Research and Practice (SERP ’03), volume I, pages 34–40. CSREA, 2003. [9] M. Merz. JDOSecure: A Security Architecture for the Java Data Objects-Specification. 15th <strong>International</strong> <strong>Conference</strong> on Software Engineering and Data Engineering (SEDE-2006), 6.-8. July, Los Angeles, California, USA, 2006. [10] M. Merz. Using the Dynamic Proxy Approach to Introduce Role-Based Security to Java Data Objects. 18th <strong>International</strong> <strong>Conference</strong> on Software Engineering and Knowledge Engineering (SEKE’06), 5.-7. July, San Francisco, California, USA, 2006. [11] S. Oaks. Java Security. The Java Series. O’Reilly & Associates, Inc., Sebastopol, CA, USA, second edition, 2001. [12] Sun Microsystems. JAAS Login Configuration File. http://java.sun.com/j2se/1.4.2/docs/guide/security/ jaas/tutorials/LoginConfigFile.html, 2002. [13] Sun Microsystems. The Java Language Specification. Addison-Wesley Professional, 3rd edition, 2005. [14] TheServerSide.COM. Craig Russell Responds to Roger Sessions’ Critique of JDO. http://www.theserverside.com/articles/article.tssl= RusselvsSessions, 2001. [15] TheServerSide.COM. A Criticism of Java Data Objects (JDO). http://www.theserverside.com/news/ thread.tssthread id=8571, 2003. 93
An Extensible Mechanism for Long-Term Persistence of JavaBeans Components Chien-Min Wang 1 , Shun-Te Wang 1 , Hsi-Min Chen 2 and Chi-Chang Huang 1 1 Institute of Information, Academia Sinica Nankang 115, Taipei, Taiwan, R.O.C. 2 Department of Computer Science and Information Engineering National Central University, Taoyuan, Taiwan, R.O.C. {cmwang, wangsd, seeme, hunter}@iis.sinica.edu.tw ABSTRACT Long Term Persistence for JavaBeans (LTP) is an API that supports a general mechanism for serializing JavaBeans into an XML-based text format and vice versa. As Java programming language does not currently support orthogonal persistence, a programmer can choose to convert the internal state of an application into a permanent storage and vice versa using the LTP API. In this paper, we propose a mechanism that is extensible and optional for LTP, without modifying the LTP specification, to maximize the flexibility and extendibility of Java applications. Our approach embeds scripts in an encoded XML text in order to reconstruct missing objects, or to create some additional helper objects during the subsequent decoding process. Moreover, as the decoding process may take too much time to instantiate certain heavyweight objects, the proposed mechanism also supports an optional cache pool to speed it up. Categories and Subject Descriptors I.7.2 [XML]: Document Preparation – format and notation, languages and systems, scripting languages. D.3.2 [Java]: Language Classifications – extensible languages, object-oriented languages General Terms Algorithms, Performance, Design, Experimentation, Languages. Keywords Persistence, JavaBeans, LTP, Java, XML, scripting, cache, serialization. 1. INTRODUCTION Object persistence has become an important requirement of modern object-oriented programming languages like C# and Java [11]. JavaBeans are reusable software components written in Java, and designed to be manipulated visually by an integrated development environment (IDE) for building applications [20]. Long Term Persistence for JavaBeans (LTP) is a persistence model for JavaBeans components [16]. The LTP specification was developed Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. To copy otherwise, or republish, to post on servers or to redistribute to lists, requires prior specific permission and/or a fee. PPPJ 2006 , August 30 – September 1, 2006, Mannheim, Germany. Copyright 2006 ACM …$5.00. through the Java Community Process, and has been included in Java 2 Standard Edition since release 1.4. The LTP persistence scheme can convert a tree or graph of JavaBeans objects into an XML-based text format and vice versa. Currently, the Java programming language does not support orthogonal persistence [14][17], which would preserve the states of any objects independent of their classes. Hence, a programmer can choose to convert the internal state of an application into a permanent storage and vice versa using the LTP API. The LTP API provides two critical classes for JavaBeans persistence: the XMLEncoder and the XMLDecoder. An instance of the XMLEncoder class is used to write text files representing JavaBeans components. The XMLEncoder clones the object graphs and records the steps taken so that the clone can be recreated at a later time. The XMLDecoder can read the XML documents created by the XMLEncoder, parse all the XML data of the given input stream, rebuild the object graphs, and place all the objects in a queue. When the readObject() method is called, an object is simply popped off the queue and returned. The use of the LTP API implies that any object can be made persistence dependent on its data type when encoded. For this purpose, the current implementation of the LTP API contains a set of PersistenceDelegates, organized according to the class of object. If there is no PersistenceDelegate for a given class, an instance of the DefaultPersistenceDelegate class is used to provide a default encoding strategy. However, exceptions may occur because, in this case, an object is assumed to be a JavaBean that follows the idioms laid out in the JavaBeans specification. In addition, the current LTP encoder cannot handle the persistence of anonymous inner classes, which results in object reference losses. This may lead to problems because the object graph is incomplete. Another interesting issue occurs when a class is implemented using the Singleton design pattern [10]. The current XMLEncoder/XMLDecoder paradigm cannot guarantee that a Singleton object will remain a true Singleton, i.e., not two distinct objects, during the decoding process. The reason is that a properly created Singleton cannot be saved using the XMLEncoder due to the absence of a public constructor for the Singleton. In other words, the current XMLEncoder/XMLDecoder paradigm is designed to save JavaBeans that are not meant to be Singletons. In this paper, we propose a mechanism that is extensible and optional for LTP, without modifying the LTP specification, the Java 94
Page 1 and 2:
Edited by: Ralf Gitzel, Markus Alek
Page 3 and 4:
Message from the Chairs Dear confer
Page 5 and 6:
Sam Midkiff, Purdue University (USA
Page 7 and 8:
Session F: Novel Uses of Java______
Page 10 and 11:
The Project Maxwell Assembler Syste
Page 12 and 13:
tomated assembler and disassembler
Page 14 and 15:
memory address offset mnemonic argu
Page 16 and 17:
5.2 Instruction Templates The assem
Page 18 and 19:
ange for a very short restart/debug
Page 20 and 21:
Tatoo: an innovative parser generat
Page 22 and 23:
In the grammar file an error termin
Page 24 and 25:
Figure 3: Push parsers and lexers L
Page 26 and 27:
eturn visit((Expr)p1, param); } R v
Page 28:
Session B Program and Performance A
Page 31 and 32:
Table 1: Use of interfaces and deco
Page 33 and 34:
Table 3: Comparison of the situatio
Page 35 and 36:
will trigger the creation of many n
Page 37 and 38:
Appendix A 10 9 8 7 6 5 4 3 2 1 0 1
Page 39 and 40:
Throughout this paper, we make no a
Page 41 and 42:
instrumented program and obtained t
Page 43 and 44:
Figure 5: Investigation of garbage
Page 45 and 46:
to the same category—again, this
Page 47 and 48:
Investigating Throughput Degradatio
Page 49 and 50: Figure 1: Apache. Throughput degrad
Page 51 and 52: Minor GC Full GC Workload # of Avg.
Page 53 and 54: Figure 6: Comparing memory and pagi
Page 55 and 56: GenRC on the other hand, allows the
Page 58: Session C Mobile and Distributed Sy
Page 61 and 62: ing a continuous buffer for raw dat
Page 63 and 64: the data arrival speed is more impo
Page 65 and 66: public class StreamingClient { publ
Page 67 and 68: importance of β in our aggregation
Page 69 and 70: Enabling Java Mobile Computing on t
Page 71 and 72: A strongly mobile thread has the ab
Page 73 and 74: a context switch occur. The invoked
Page 75 and 76: above phases. Now, the new stack ha
Page 77 and 78: 5 frames 15 frames 25 frames Pure d
Page 79 and 80: Juxta-Cat: A JXTA-based platform fo
Page 81 and 82: Figure 1: JXTA Architecture. 3. JUX
Page 83 and 84: • Send a discovery query to the p
Page 85 and 86: The best candidate is then the one
Page 87 and 88: Local Hosts=2 Hosts=4 Hosts=8 Hosts
Page 90: Session D Resource and Object Manag
Page 93 and 94: Enterprise Edition (J2EE). It enabl
Page 95 and 96: As pictured in Figure 4, JDOSecure
Page 97 and 98: Methods of a PersistenceManager, th
Page 99: Datenmodell abstrahiert user role,
Page 103 and 104: missing object references in the de
Page 105 and 106: 4.2 Mapping the name spaces of the
Page 107 and 108: (a) (b) ColorSliderPanel0 color
Page 109 and 110: 8. REFERENCES [1] Abu-Ghazaleh, N.,
Page 111 and 112: permission by process. In other wor
Page 113 and 114: The processor then refers to the en
Page 115 and 116: 1: // Protection domain 2: struct p
Page 117 and 118: Table 3: Frequency of JNI calls tha
Page 119 and 120: [13] Intel Corporation. IA-32 Intel
Page 121 and 122: 01 try { 02 ... 03 } finally { 04 t
Page 123 and 124: 2. FRAMEWORK The Framework for Unif
Page 125 and 126: ManagedInputStream ResourceGroup Ma
Page 127 and 128: 18. throw ‡ 1. release 17. cleanu
Page 129 and 130: 3. FUTURE WORK The ability to split
Page 131 and 132: 124
Page 133 and 134: UML sequence diagrams are among the
Page 135 and 136: diagrams, and behavioral (dynamic)
Page 137 and 138: the official scripting language for
Page 139 and 140: Apache's XML Graphics Project. A cu
Page 141 and 142: Java Debug Interface (JDI). In Revi
Page 143 and 144: 1.3 JML 1.3.1 Overview JML, the Jav
Page 145 and 146: The Usage of CANAPA is fairly strai
Page 147 and 148: *@non_null@*/ String str = attribut
Page 149 and 150: 142
Page 151 and 152:
parallel and distributed versions o
Page 153 and 154:
RingElem CextendsRingElem GenPolyno
Page 155 and 156:
RingElem +isZERO():bolean CextendsR
Page 157 and 158:
class constructors with the actual
Page 159 and 160:
plemented via a distributed hash ta
Page 161 and 162:
which are common nowadays. The reus
Page 163 and 164:
Derivative Contract Component Repos
Page 165 and 166:
stepwise execution create Derivativ
Page 167 and 168:
5.4.1 Structural Constraints Struct
Page 169 and 170:
into the conceptual foundation of n
Page 171 and 172:
different implementation and is mor
Page 173 and 174:
the service from the root. It allow
Page 175 and 176:
model: 1. Servlet [6] adapter compo
Page 177 and 178:
y possibly different service, where
Page 179 and 180:
or the fact that widgets extend ser
Page 181 and 182:
174
Page 183 and 184:
The idea of Java 5.0 type inference
Page 185 and 186:
Source := (class | interface)∗ cl
Page 187 and 188:
5. IMPLEMENTATION In order to prese
Page 189 and 190:
Infinite Streams in Java Dominik Gr
Page 191 and 192:
} private static LinkedStream fibon
Page 193 and 194:
of the f stream in order to compute
Page 195 and 196:
Interaction among Objects via Roles
Page 197 and 198:
(a) (b) (c) (d) (e) Figure 1: The p
Page 199 and 200:
class Printer { private int totalPr
Page 201 and 202:
Experiences of using the Dagstuhl M
Page 203 and 204:
Metric Definition Java .class files
Page 205 and 206:
scription of the metric values. Non
Page 207 and 208:
Figure 1: Results from the J-vestig
Page 209 and 210:
an error is subsequently generated
Page 211 and 212:
3. BASIC TERMINOLOGY As object-orie
Page 213 and 214:
• subtyping • (implementation)
Page 215 and 216:
Improving the Quality of Programmin
Page 217 and 218:
Results of online checks (shortened
Page 219 and 220:
212
Page 221 and 222:
214
Page 223 and 224:
Experiences With Hierarchy-Based Co
Page 225 and 226:
Sub View Child DataField 0..n Ke
Page 227 and 228:
Figure 8 - Actual State Charts elem
Page 229 and 230:
associations, which may result in r
Page 231 and 232:
M3PS: A Multi-Platform P2P System B
Page 233 and 234:
In following, we will explain in de
Page 235 and 236:
Figure 10. JDP in Windows XP. Figur
Page 237 and 238:
Mapping Clouds of SOA- and Business
Page 239 and 240:
the technical SOA events (from the
Page 241 and 242:
component and the business process
Page 243 and 244:
Figure 13. “Business Value of Dat
Page 245 and 246:
Solaris of SUN. This platform provi
Page 247 and 248:
status change of an application is
Page 249 and 250:
coming up, is presently discussing
Page 251:
ISBN: 3-939352-05-5 ISBN: 978-3-939
show all

4th International Conference on Principles and Practices ... - MADOC

Create successful ePaper yourself

Delete template?

Save as template?