Skip to main content

Home/ Java Development/ Group items matching "Support" in title, tags, annotations or url

Group items matching
in title, tags, annotations or url

Sort By: Relevance | Date Filter: All | Bookmarks | Topics Simple Middle
Arup Vidyerthy

Java for OS X 2013-002: How to re-enable the Apple-provided Java SE 6 web plug-in and Web Start functionality. - 0 views

  •  
    Switching between Apple and Oracle Java plugin
nick puruzio

Scala (programming language) - Wikipedia, the free encyclopedia - 0 views

  • Scala supports functional programming.
  •  
    "concisely express solutions in an elegant,[6] type-safe and lightweight (low ceremonial) manner"
Richard Boss

Steps to Configure Wowza and Create an Application - 0 views

  •  
    Read this post to know how to install and configure Wowza media server. And let's see basic steps to create an application on Wowza server.
abuwipp

Spring to Java EE - A Migration Experience | OcpSoft - 0 views

  •  
    Does it all make sense now? Do you know how to solve every problem? Probably not, but when it comes right down to it, using Java EE can be even simpler than using Spring, and take much less time. You just have to find the right guides and the right documentation (which is admittedly a severe sore-spot of Java EE; the documentation is still a work in progress, but is getting much better, save blogs like this one.) You have to turn to a vendor like JBoss, or IBM in order to get the use-case driven documentation you need, and they do have documentation, it's just a matter of finding it. Seam 3 in particular strives to give extensive user-documentation, hopefully making things much simpler to adopt, and easier to extend. The main purpose of this article was not to bash Spring, although I may have taken that tone on occasion just for contrast and a little bit of fun. Both Spring and Java EE are strongly engineered and have strong foundations in practical use, but if you want a clean programming experience right out of the box - use Java EE 6 on JBoss Application Server 6 - JBoss Tools - and Eclipse. I will say, though, that the feeling I've gotten from the Spring forums vs the Java EE forums, is that there are far many more people willing to help you work through Java EE issues, and more available developers of the frameworks themselves to actually help you than there are on the Spring side. The community for Java EE is much larger, and much more supportive (from my personal experience.) In the end, I did get my application migrated successfully, and despite these issues (from which I learned a great deal,) I am still happy with Java EE, and would not go back to Spring! But I do look forward to further enhancements from the JBoss Seam project, which continue to make developing for Java EE simpler and more fun. Don't believe me? Try it out. Find something wrong? Tell me. Want more? Let me know what you want to hear.
Baron M

GAME OVER - Java Server Faces | ComeSolveGo - 0 views

  • Almost everything is wrong with the framework
  • Little control over generated HTML
  • While you need basic functionalities, everything is fine. When you need to modify the component (which is configurable, right?) you are facing the problems
  • ...8 more annotations...
  • EXTREMELY idiotic thing - because JSF has their famous lifecycle with lots of magic phases, some backing bean getters are called multiple times!
  • Back button problem.
  • Unreadable URLs. JSF always does the POST.
  • JSF is submitting a form on itself so it could call a backing bean method to handle an event. Of course, if you have a request, there is unnecessary repeated initialization, getter calls, postconstruct etc
  • Reusability? Good joke…
  • JSF - you are FIRED!
  • IDE support
  • Development of custom component? No way, extremely complicated. Extensible? In the movie, maybe…
  •  
    I think many people have the same feeling (of course including me)
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
samantha armstrong

FixComputerpProblemsSite Surely Knows How to Fix Computer Problems! - 1 views

I was having problems with my laptop before. Good thing FixComputerpProblemsSite helped me fix it. And they are really the experts when it comes to solving any computer related issues. They can eas...

fix computer problems java web development opensource framework programming eclipse spring jsf library

started by samantha armstrong on 07 Jun 11 no follow-up yet
seth kutcher

Two Thumbs Up For Computer Assistance Services - 2 views

I am so happy for the computer assistance that Computer Assistance Online gave me. They provided me with precise and fast solutions to my computer problem. Their computer specialists really know wh...

computer assistance

started by seth kutcher on 06 Jun 11 no follow-up yet
shai edrote

They Fixed My Slow Computer - 1 views

My computer started running so slow that it takes me 10 minutes just to open a site. So I called Fix Slow Computer Today to help me with my concern. They have expert computer technicians who can fi...

They Fixed My Slow Computer

started by shai edrote on 12 Sep 11 no follow-up yet
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
cecilia marie

My Computer Problem Was Solved in a Few Minutes - 1 views

I had a good internet connection for the past few weeks. Then I began to observe that it was not working the way it should be compared to the past few weeks. I tried to troubleshoot it myself but, ...

computer problem online help fix

started by cecilia marie on 13 Oct 11 no follow-up yet
Programming People

Developing Java Application using Couchbase - 0 views

  •  
    Several Java Web Applications framework like Ruby on Rails and other PHP and Python web server also hold pre-integrated option for storing data with the help of Memcached protocol automatically supported by Couchbase.
krowddigital

About Us :UI/UX Design & Mobile App Development Services Company - 1 views

  •  
    We can help you grow your business online through our services. The support staff is friendly and honest. Their customer service is excellent.
« First ‹ Previous 61 - 73 of 73
Showing 20 items per page