Entity Proxies
1More
AtomServer 2.3.4 - - 0 views
-
"AtomServer is a generic data store implemented as a RESTful web service. It is designed as a GData-style Atom Store. It is based on the following concepts and protocols; REST. REST is a design pattern. It's not a technology like SOAP or HTTP. REST is a proven design pattern for building loosely-coupled, highly-scalable applications. There are important benefits to sticking to the REST design pattern; Simple. REST is incredibly simple to define. There are just a handful of principles and well defined semantics associated with it. Scalable. REST leads to a very scalable solution by promoting a stateless protocol and allowing state to be distributed across the web. Layered. REST allows any number of intermediaries, such as proxies, gateways, and firewalls. Ultimately REST is just a web site, albeit one that adheres to a design pattern, so one can easily layer aspects such as Security, Compression, etc. on an as needed basis. Atom. Fundamentally, Atom is an XML vocabulary for describing lists of timestamped entries. These entries can be anything, although because Atom was originally conceived to replace RSS, Atom lists are Feeds, and the items in the lists are Entries. Atom is a RESTful protocol. AtomServer stands on the shoulders of giants. It is built on top of several open source projects - most notably, Apache Abdera (a Java-based Atom Publishing framework) and Spring. AtomServer is an Atom Store. Thus, it requires a relational database to run. AtomServer currently supports; PostgresSQL, SQLServer, and HSQLDB. Using HSQLDB, AtomServer requires zero configuration and can run out-of-the-box. While this configuration is suitable for many applications, those that see significant load will likely require a database with better transactional semantics, such as PostgreSQL. AtomServer is easy to use. It deploys as a simple WAR file into any Servlet container. Or alternately, can be used out-of-the-box as a standalone server, running with
1More
Sapphire - 0 views
-
Sapphire - develop UI without wiring individual widgets Little has changed in the way Java desktop UI is written since the original Java release. Technologies have changed (AWT, Swing, SWT, etc.), but fundamentals remain the same. The developer must choose which widgets to use, how to lay those widgets out, how to store the data being edited and how to synchronize the model with the UI. Even the best developers fall into traps of having UI components talk directly to other UI components rather than through the model. Inordinate amount of time is spent debugging layout and data-binding issues. Sapphire aims to raise UI writing to a higher level of abstraction. The core premise is that the basic building block of UI should not be a widget (text box, label, button, etc.), but rather a property editor. Unlike a widget, a property editor analyzes metadata associated with a given property, renders the appropriate widgets to edit that property and wires up data binding. Data is synchronized, validation is passed from the model to the UI, content assistance is made available, etc. This fundamentally changes the way developers interact with a UI framework. Instead of writing UI by telling the system how to do something, the developer tells the system what they intend to accomplish. When using Sapphire, the developer says "I want to edit LastName property of the person object". When using widget toolkits like SWT, the developer says "create label, create text box, lay them out like so, configure their settings, setup data binding and so on". By the time the developer is done, it is hard to see the original goal in the code that's produced. This results in UI that is inconsistent, brittle and difficult to maintain.
1More
HowToConfigureExtendedWADL - Jersey: RESTful Web services made easy - wikis.sun.com - 0 views
wikis.sun.com/...HowToConfigureExtendedWADL
restful web jersey howtoconfigureextendedwadl wadl glassfish webservices jax
shared by Hendy Irawan on 04 Apr 11
- No Cached
-
"This page describes how you can get an extended WADL from your REST app. It aligns mostly with the extended-wadl-webapp sample and uses these features: Add additional doc tags to the WADL Create JAXB beans from xsd - you might also create the schema from your beans Add the grammars element that includes the xsd file from which JAXB beans were generated to the WADL Add javadoc from your resource classes to the WADL, using most of the supported javadoc tags For getting the extended WADL as described above these things have to be done: Configure the maven-jaxb-plugin to create JAXB beans from xsd - this is described here just to describe what's done in the sample. Add the application-doc.xml and application-grammars.xml to the build classpath Configure the maven-javadoc-plugin with the ResourceDoclet provided by the wadl-resourcedoc-doclet artifact to create the resource-doc.xml. Create a subclass of WadlGeneratorConfig that defines/configures the WadlGenerators to use Specify your custom WadlGeneratorConfig in the web.xml as the WadlGeneratorConfig"
1More
Ajax Push - Overview - ICEfaces - ICEfaces.org Community Wiki - 0 views
wiki.icefaces.org/...Ajax+Push+-+Overview
ajax push overview community icefaces application jsf java javaee web
shared by Hendy Irawan on 24 Apr 11
- No Cached
-
Ajax Push allows the application to incrementally update any part of the page at any time, for any group of clients. This is a small change in terms of the technical capabilities of Ajax applications, but it is a revolutionary change in terms of what applications can actually provide to users. Ajax Push is the key to building collaborative multi-user applications for the web. Under the Hood The intricacies of the Ajax Push implementation are completely transparent to the ICEfaces developer, as you work with a straightforward set of APIs. It is, however, useful to understand the basic mechanics. Ajax Push in ICEfaces 2.0 leverages an asynchronous notification mechanism call ICEpush. Simply put, ICEpush uses long polling to provide asynchronous notification over standard HTTP, using only standard browser capabilities. The sequence of events involved in Ajax Push is illustrated below.
1More
Getting started with Spring Data JPA | SpringSource Team Blog - 0 views
blog.springsource.com/...g-started-with-spring-data-jpa
spring hades persistence started spring-data data getting java query repository database DB JPA
shared by Hendy Irawan on 26 Apr 11
- No Cached
-
As we have just released the first milestone of the Spring Data JPA project I'd like to give you a quick introduction into its features. As you probably know, the Spring framework provides support to build a JPA based data access layer. So what does Spring Data JPA add to this base support? To answer that question I'd like to start with the data access components for a sample domain implemented using plain JPA + Spring and point out areas that leave room for improvement. After we've done that I will refactor the implementations to use the Spring Data JPA features to address these problem areas. The sample project as well as a step by step guide of the refactoring steps can be found on Github.
1More
Eclipse Gemini Blueprint - Home - 0 views
-
Eclipse Gemini Blueprint is the reference implementation for the OSGi Alliance Blueprint Service (chapter 121 of the OSGi 4.2 Compendium Specification). Gemini Blueprint project makes it easy to build Java applications that run in an OSGi framework. By using Gemini Blueprint, applications benefit from using a better separation of modules, the ability to dynamically add, remove, and update modules in a running system, the ability to deploy multiple versions of a module simultaneously (and have clients automatically bind to the appropriate one), and a dynamic service model. Gemini users may also be interested in Eclipse Virgo, an open source, completely modular, OSGi-based Java application server. Its documentation is considered a supplement to Gemini Blueprint as it explains in detail, how OSGi can be used in various development and production scenarios.
1More
twitter/finagle @ GitHub - 0 views
-
"Finagle is a library for building asynchronous RPC servers and clients in Java, Scala, or any JVM language. Overview Built atop Netty, Finagle provides a rich set of tools that are protocol independent. Finagle is flexible enough to support a variety of RPC styles, including request-response, streaming, and pipelining (e.g., HTTP pipelining and Redis pipelining). It also makes it easy to work with stateful RPC styles (e.g., those requiring authentication and those that support transactions)."
1More
Registering with us has lots of benefits. Try it now. - 0 views
-
By registering you can Write unlimited practise tests Track your progress and get a rank compared to other users Participate in various contests and win cash prizes and certificates Build your profile and create a resume in multiple formats Clarify your Java doubts over phone/email Use the easy online compiler
1More
How to become a Front-end developer in 2019 - 0 views
blog.edwisor.com/...-a-front-end-developer-in-2019
front-end development developers front end engineer frontend salary javascript
shared by marketngedwisor on 03 Aug 19
- No Cached
-
Front End Development or Client-Side Development is the practice of coding in technologies like HTML, CSS, and Javascript in a website. The practice involves converting Data into a Graphical Interface for a user to view and interact. Growth in Front-end development is excellent and there are plenteous opportunities available, especially because companies now want their customers to have a good experience while using their Web applications. Want to get hired as a Front End Developer in 2019? Acquire skills in Front End Development, Build live Projects and Get Guaranteed Interviews with edWisor.
1More
Oracle and IBM Collaborate to Accelerate Java Innovation Through OpenJDK - 0 views
-
Oct. 11, 2010 - Oracle and IBM today announced that the companies will collaborate to allow developers and customers to build and innovate based on existing Java investments and the OpenJDK reference implementation. Specifically, the companies will collaborate in the OpenJDK community to develop the leading open source Java environment.
1More
A Spoon-feed, step by step fast Spring Web MVC Tutorial - 0 views
www.adobocode.com/...a-spring-web-mvc-tutorial
spring mvc tutorial web application Model View Controller Tomcat Eclipse ant build jdk dynamic project
shared by Paul Sydney Orozco on 25 Nov 10
- No Cached
1More
meta beta: EMF and RAP and Virgo, oh my.. - 0 views
milesparker.blogspot.com/...f-and-rap-and-virgo-oh-my.html
beta meta emf eclipse RAP Virgo web server deploy build java
shared by Hendy Irawan on 03 Jan 11
- No Cached
-
"what if I just dropped the EMF bundles into the same place, modified the demo .plan file to include them, and.. No way that could possibly work, right? Not only did it work, but it actually worked before I thought it would. I was ready for endless rounds of editing, rebuilding, restarting, reloading, re.. But instead, I saved the changes to the .plan file and Equinox/Virgo automagically hot-loaded them and ran through the dependencies there and then. I cleaned a couple of things up, and then I navigated to the URL, and there it was. Seriously, I haven't been that impressed by a technology that "just worked" since the first time I built an EMF model and editor. I'll say it: The Virgo/RAP/EMF stack is going to be -- already is -- a kick-ass combination. Light-weight development, light-weight deployment, industrial strength, web-based MDSD."
151More
Getting Started with RequestFactory - Google Web Toolkit - Google Code - 0 views
-
- ...147 more annotations...
-
BigDecimal, BigInteger, Boolean, Byte, Enum, Character, Date, Double, Float, Integer, Long, Short, String, Void
-
Methods that return a Request object in the client interface are implemented as static methods on the entity
-
backing store (JDO, JPA, etc.) is responsible for updating the version each time the object is persisted,
-
On the client side, RequestFactory keeps track of objects that have been modified and sends only changes
-
automatically populates bean-style properties between entities on the server and the corresponding EntityProxy on the client,
-
It is not necessary to represent every property and method from the server-side entity in the EntityProxy
1More
Tycho reference card - Tycho - Confluence - 0 views
docs.sonatype.org/...Tycho+reference+card
reference tycho card maven eclipse build system project management plugin compiler pom
shared by Hendy Irawan on 28 Apr 11
- No Cached
‹ Previous
21 - 38 of 38