Skip to main content

Home/ Java Development/ Group items tagged share

Rss Feed Group items tagged

anonymous

Bistro!: GlassFish equivalent to WebSphere's "shared libraries" - 0 views

  •  
    GlassFish equivalent to WebSphere's "shared libraries"
Hendy Irawan

Sonatype.org: Nexus - 0 views

  •  
    "Sonatype Nexus: Manage Artifacts Sonatype Nexus sets the standard for repository management providing development teams with the ability to proxy remote repositories and share software artifacts. Download Nexus and gain control over open source consumption and internal collaboration."
Hendy Irawan

Articles | OcpSoft - JSF2 | SEO | Bookmarking | Java | Best Practices | Agile - 0 views

  •  
    "The PrettyFaces team is currently working on an alternative way to configure URL mappings. PrettyFaces will soon allow to use annotations instead of the classic XML configuration file to declare mappings. We encourage everyone interested in PrettyFaces to take a look at this new way of configuration and share his or her opinion with us."
Rinav G

Java BluePrints : Model-View-Controller- J2EE Patterns - 1 views

  •  
    By applying the Model-View-Controller (MVC) architecture to a JavaTM 2 Platform, Enterprise Edition (J2EETM) application, you separate core business model functionality from the presentation and control logic that uses this functionality. Such separation allows multiple views to share the same enterprise data model, which makes supporting multiple clients easier to implement, test, and maintain.
  •  
    Java BluePrints Model-View-Controller
anonymous

Guide: Writing Testable Code (Miško Hevery) - 2 views

  •  
    "To keep our code at Google in the best possible shape we provided our software engineers with these constant reminders. Now, we are happy to share them with the world."
Hendy Irawan

Buckminster Project - Eclipsepedia - 0 views

  •  
    " Jump to: navigation, search Welcome to our Wiki. This is the Wiki home page for the Buckminster Component Assembly project, an Eclipse Tools sub project. Buckminster is a component resolution & materialization framework. Its purpose is to get software components for you and materialize them in a context of choice, typically a workspace or file system. This applies whether you are looking at what's available on your local machine, within your development organization or in the public open source cloud. Buckminster reuses existing investments in a wide range of build and source management tools - Maven, ANT, CVS, SVN, PDE, etc. It removes ambiguity from component descriptions, enables component sharing and increases productiveness when applied in development, build, assembly and deploy scenarios. "
anonymous

JVM And Docker- A Better Combination For Java Developers To Work - 0 views

  •  
    Aegis professionals will share information about JVM and Docker and how their combination can be really helpful for Java Developers. This article is shared to Help Java Development Community and the developers all over the world.
Hendy Irawan

Maven Archiver Plugin JAR WAR Manifest - Reference - 0 views

  •  
    "The Maven Archiver is mainly used by plugins to handle packaging. The version numbers referenced in the Since column on this page are the version of the Maven Archiver component - not for any specific plugin. To see which version of Maven Archiver a plugin uses, go to the site for that plugin. "
sureshstalin

Sr. Sharepoint Developer with Sql Experience - 0 views

  •  
    JOB SUMMARY: This Senior Programmer/Analyst is responsible for the design, development and documentation of SharePoint applications as well as devlelopment and support of organizationl reports and data queries. Reports are typically developed in Crystal Reports. This position is also responsible for the support and maintenance of the Crystal Enterprise environment.
anonymous

Getting Started with RequestFactory - Google Web Toolkit - Google Code - 0 views

  • Entity Proxies
    • anonymous
       
      Proxy type (on the Client) vs Entity type (on the server)
  • proxy types
  • entity types
  • ...147 more annotations...
  • methods that return service stubs
  • one RequestFactory interface for your application
  • employeeRequest();
  • @Service(Employee.class)
  • extends RequestContext
  • extends RequestFactory
  • service stub
  • RequestFactory service stubs
  • must extend RequestContext
  • The methods in a service stub do not return entities directly
  • return subclasses of com.google.gwt.requestfactory.shared.Request.
  • This allows the methods on the interface to be invoked asynchronously with
  • Request.fire()
  • fire(    new Receiver()
  • onSuccess
  • callers pass an AsyncCallback that implements onSuccess()
  • takes a Receiver which must implement onSuccess()
  • Receiver is an abstract class having a default implementation of onFailure()
  • you can extend Receiver and override onFailure()
  • onViolation()
  • any constraint violations on the server
  • The Request type returned from each method
  • parameterized with the return type of the service method.
  • Methods that have no return value should return type Request<Void>
  • BigDecimal, BigInteger, Boolean, Byte, Enum, Character, Date, Double, Float, Integer, Long, Short, String, Void
  • subclass of EntityProxy
  • List<T> or Set<T>
  • primitive types are not supported
  • methods that operate on an entity itself
  • like persist() and remove()
  • return objects of type InstanceRequest rather than Reques
  • Server Implementations
  • methods defined in an
  • entity's service interface
  • implemented in the class named
  • @Service annotation
  • in these examples, is the entity class
  • service implementations do not directly implement the RequestContext interface
  • server-side implementations use the domain entity types
  • @Entity
  • EntityManager
  • createQuery
  • getResultList();
  • entityManager()
  • createEntityManager()
  • em.persist(this);
  • em.remove(attached
  • em.close();
  • defined in the service's
  • RequestContext interface
  • even though the implementation does not formally implement the interface in Java
  • name and argument list for each method
  • same on client and server
  • Client side methods
  • return Request<T>
  • only T on the server
  • EntityProxy types become the domain entity type on the server
  • Methods that return a Request object in the client interface are implemented as static methods on the entity
  • Methods that operate on a single instance of an entity, like persist() and remove(),
  • eturn an
  • InstanceRequest
  • in the client interface
  • Instance methods do not pass the instance directly, but rather via the
  • using()
  • instance methods must be implemented as non-static methods in the entity type
  • Four special methods are required on all entities
  • as they are used by the RequestFactory servlet:
  • constructor
  • findEntity
  • An entity's getId()
  • is typically auto-generated by the persistence engine (JDO, JPA, Objectify, etc.)
  • "find by ID" method has a special naming convention
  • find()
  • "find" plus the type's simple name
  • On the server
  • getVersion() method is used by RequestFactory to infer if an entity has changed
  • backing store (JDO, JPA, etc.) is responsible for updating the version each time the object is persisted,
  • RequestFactoryServlet sends an UPDATE
  • if an entity changes as
  • Second, the client maintains a version cache of recently seen entities
  • Whenever it sees an entity whose version has changed, it fires
  • UPDATE events on the event bus
  • so that listeners can update the view
  • GWT.create
  • and initialize it with your application's EventBus
  • GWT.create
  • requestFactory.initialize
  • create a new entity on the client
  • EmployeeRequest request
  • EmployeeProxy newEmployee
  • All client-side code should use the EmployeeProxy
  • not the Employee entity itself
  • unlike GWT-RPC, where the same concrete type is used on both client and server
  • RequestFactory
  • designed to be used with an ORM layer like JDO or JPA
  • on the server
  • to build data-oriented (CRUD) apps with an ORM-like interface
  • on the client
  • easy to implement a data access layer
  • structure your server-side code in a data-centric way
  • GWT-RPC, which is service-oriented
  • On the client side, RequestFactory keeps track of objects that have been modified and sends only changes
  • lightweight network payloads
  • solid foundation for automatic batching and caching of requests in the future
  • RequestFactoryServlet
  • RequestFactory uses its own servlet
  • own protocol
  • not designed for general purpose services like GWT-RPC
  • implements its
  • It is designed specifically for implementing a persistence layer on both client and server.
  • In persistence frameworks like JDO and JPA, entities are annotated with
  • client-side representation of an entity
  • known as a
  • DTO (Data Transfer Object)
  • hook used to indicate that an object can be managed by RequestFactory
  • RequestFactory
  • EntityProxy interface
  • automatically populates bean-style properties between entities on the server and the corresponding EntityProxy on the client,
  • send only changes ("deltas") to the server
  • extends EntityProxy
  • interface
  • @ProxyFor
  • reference the server-side entity being represented
  • It is not necessary to represent every property and method from the server-side entity in the EntityProxy
  • EntityProxyId returned by this method is used throughout RequestFactory-related classes
  • while getId() is shown in this example, most client code will want to refer to
  • EntityProxy.stableId() i
  • to represent any type
  • is not required to expose an ID and version
  • often used to represent embedded object types within entities
  • @Embedded
  • Address
  • Address type
  • POJO with no persistence annotations
  • Address is represented as a ValueProxy
  • extends ValueProxy
  • interface
  • extends EntityProxy
  • interface
  • AddressProxy
  • AddressProxy
  • ValueProxy can be used to pass any type to and from the server
  • RequestFactory
  • interface between your client and server code
  • RequestContext interface
  • The server-side service
  • must implement each method
Baron M

Java Developers Leery of IBM-Sun Merger - 0 views

  • Java must advance into the new world of the cloud and big developer productivity.
  • Java will become a legacy platform.
  • slow down innovation
  • ...10 more annotations...
  • It would certainly bring us down to two major players on the Java side: IBM and Oracle.
    • Baron M
       
      this is damn TRUE!
  • IBM likes to create these 'boil the ocean' kinds of solutions
    • Baron M
       
      this is the GENERAL PRACTICE of IBM and Oracle
  • IBM could wind up having six different JVM [Java Virtual Machine] implementations
    • Baron M
       
      I like this example... and most likely, this would happen if IBM buys SUN
  • it's a good thing for Sun to get out of the doldrums
  • Every time IBM has bought a company that was in a leadership position, that company seems to have lost market share
    • Baron M
       
      sad but it's a fact...
  • JCP for behaving like a "Russian commissar.
  • Although many have lost faith in the JCP, this is one area where a new steward could really breathe new life into Java
  • the speediest when it comes to keeping their Java technologies up-to-date
  • hold back innovation in support of their own client needs
  • server market would become a bit tighter and that playing field would be altered as well
krowddigital

Salesforce CRM Features and Benefits [Guide 2022] - 1 views

  •  
    CRM tools, such as Salesforce, make it easy to share and access information across platforms
krowddigital

Salesforce CRM Features and Benefits [Guide 2022] - 1 views

  •  
    CRM tools, like Salesforce makes it simple to share information and gain access across multiple platforms
1 - 13 of 13
Showing 20 items per page