Skip to main content

Home/ Java Development/ Group items matching "application" 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
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
  • marketngedwisor on 03 Aug 19
     
    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

Java App Development Services - 2 views

www.strivemindz.com/java-application-development java programming development web framework opensource online library
shared by Strivemindz Pvt. Ltd. on 29 Dec 21 - No Cached
  • Strivemindz Pvt. Ltd. on 29 Dec 21
     
    As Java arises as a leading technology for enterprise applications, more and more businesses are looking ahead to take advantage of this technology.
1More

Sr. Sharepoint Developer with Sql Experience - 0 views

www.river2c.com/...viewjob.r2c sharepoint sp moss share point programmer developer cv find me a job jobs education vacancies sg
shared by sureshstalin on 04 Aug 13 - No Cached
  • sureshstalin on 04 Aug 13
     
    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.
4More

The NetBeans E-commerce Tutorial - Connecting the Application to the Database - 0 views

netbeans.org/...connect-db.html netbeans java ee tutorial
shared by Arup Vidyerthy on 30 Nov 13 - No Cached
  • sun-resources.xml
    • Arup Vidyerthy
      Arup Vidyerthy on 30 Nov 13
       
      This is incorrect. NetBeans generates glassfish-resources.xml
  • items="categories.rows"
    • Arup Vidyerthy
      Arup Vidyerthy on 30 Nov 13
       
      I have items="${categories.rows}"
5More

Redirect After Post - 0 views

www.theserverside.com/...Redirect-After-Post post redirect after web development get http java programming
shared by henry klingberg on 28 Jun 10 - Cached
  • input data, which can change state of server application
  • reloading result page using Refresh/Reload
  • Instead of returning a result page immediately in response to POST request, server responds with redirect to result page. Browser loads the result page as if it were an separate resource
  • ...2 more annotations...
  • When a user tries to refresh the result page, browser resends an "empty" GET request to the server. This request does not contain any input data and does not change server status
  • The vehicle which makes transition from POST to GET possible is redirection.
1More

SQuirreL SQL Client Home Page - 0 views

squirrel-sql.sourceforge.net database computing client browser application apps administration aol java tools software jdbc db sql programming
shared by Hendy Irawan on 25 Sep 10 - Cached
  • Hendy Irawan on 25 Sep 10
     
    * Enhancements o New plugins provide enhanced capabilities: + Hibernate Plugin: # allows to generate SQL statements from Hibernate HQL statements # shows object tree of mapped objec
9More

[JavaSpecialists 177] - Logging Part 3 of 3 - 0 views

www.javaspecialists.eu/...Issue177.html java javaspecialists logging bestpractices
shared by Rinav G on 17 Sep 10 - No Cached
  • Writing your own logging framework is the perfect coding crime.
  • Writing your own logging framework is the perfect coding crime
  • Even the Sun engineers fell into this trap. Prior to Java 4, we had a perfectly good logging framework in Log4J. However, instead of adopting this into the standard Java distribution, we ended up with java.util.logging. There are lots of Java logging frameworks available, even meta-logging frameworks like SLF4J and Jakarta Commons. These are supposed to abstract the logging frameworks so you can change the implementation without touching your code.
  • ...5 more annotations...
  • Logging Levels
  • In Log4J for example, we have six default levels, FATAL, ERROR, WARNING, INFO, DEBUG and TRACE.
  • Since it is tricky assigning the correct levels in our code, we should regularly do code reviews with specific emphasis on logging levels.
  • We should be able to adjust the log levels of our individual components at runtime without restarting our application.
  • Silent Operation
  • Rinav G on 17 Sep 10
     
    Writing your own logging framework is the perfect coding crime. If you can convince your manager to put it on the project plan, you are guaranteed to have success. At the end of each day, you will go home feeling happy and satisfied. It will feel like you are doing something creative. You will get the intellectual stimulation without the risk of failure. Even the Sun engineers fell into this trap. Prior to Java 4, we had a perfectly good logging framework in Log4J. However, instead of adopting this into the standard Java distribution, we ended up with java.util.logging. There are lots of Java logging frameworks available, even meta-logging frameworks like SLF4J and Jakarta Commons. These are supposed to abstract the logging frameworks so you can change the implementation without touching your code. http://www.javaspecialists.eu/archive/Issue177.html
9More

Overview (Java Platform SE 6) - 0 views

download.oracle.com/...index.html java platform java.util.concurrent.atomic concurrent AutomicInteger
shared by Rinav G on 17 Sep 10 - Cached
  • Package java.util.concurrent.atomic A small toolkit of classes that support lock-free thread-safe programming on single variables.
  • A small toolkit of classes that support lock-free thread-safe programming on single variables. In essence, the classes in this package extend the notion of volatile values, fields, and array elements to those that also provide an atomic conditional update operation of the form: boolean compareAndSet(expectedValue, updateValue);
  • Atomic classes are not general purpose replacements for java.lang.Integer and related classes. They do not define methods such as hashCode and compareTo. (Because atomic variables are expected to be mutated, they are poor choices for hash table keys.)
  • ...4 more annotations...
  • The specifications of these methods enable implementations to employ efficient machine-level atomic instructions that are available on contemporary processors.
  • java.util.concurrent.atomic Class AtomicInteger java.lang.Object java.lang.Number java.util.concurrent.atomic.AtomicInteger
  • An int value that may be updated atomically. See the java.util.concurrent.atomic package specification for description of the properties of atomic variables. An AtomicInteger is used in applications such as atomically incremented counters, and cannot be used as a replacement for an Integer. However, this class does extend Number to allow uniform access by tools and utilities that deal with numerically-based classes.
  • int incrementAndGet()           Atomically increments by one the current value.
  • Rinav G on 17 Sep 10
     
    Package java.util.concurrent.atomic Description A small toolkit of classes that support lock-free thread-safe programming on single variables. In essence, the classes in this package extend the notion of volatile values, fields, and array elements to those that also provide an atomic conditional update operation of the form: boolean compareAndSet(expectedValue, updateValue);
1More

Building Collaborative CRUD Applications With ICEfaces and NetBeans - 1 views

netbeans.org/...efaces-netbeans-crud-apps.html crud java web jsf iceFaces
shared by Rinav G on 11 Oct 10 - Cached
  • Rinav G on 11 Oct 10
     
    ICEFaces Netbeans Tutorial for creating Database CRUD
1More

Developing JavaFX applications with Eclipse - Tutorial - 0 views

www.vogella.de/...article.html JavaFX Eclipse
shared by Lars Vogel on 28 Dec 08 - Cached
  • Lars Vogel on 28 Dec 08
     
    Developing JavaFX with Eclipse
125More

Organize Projects - Google Web Toolkit - Google Code - 0 views

code.google.com/...evGuideOrganizingProjects.html
shared by anonymous on 14 Jan 11 - Cached
  • com.google.gwt.gears.Gears
    • anonymous
      anonymous on 14 Jan 11
       
      Gears.gwt.xml does not define andy entry point. It can only be inherits
  • two ways to approach loading them
  • nclude each module with a separate <script> tag
  • ...118 more annotations...
  • Create a top level module XML definition
  • Compile the top level module
  • the second approach will lead to much better end-user performance
  • each module has to be downloaded separately by the end-user's browser
  • each module will contain redundant copies of GWT library
  • conflict with each other during event handling
  • Linkers are divided into three categories, PRE, POST, and PRIMARY
  • one primary linker is run for a compilation
  • everal linkers are provided by Core.gwt.xml, which is automatically inherited by User.gwt.xml.
  • monolithic JavaScript file.
  • cross-site deployment model.
  • standard iframe-based
  • <add-linker name="xs" />
  • The GWT compiler
  • packaging its output with the Linker subsystem
  • responsible for the final packaging of the JavaScript code
  • providing a pluggable bootstrap mechanism
  • re-use an existing Java API for a GWT project,
  • <super-source>
  • "re-root" a source path
  • to emulate part of the JRE not implemented by GWT
  • tells the compiler to add all subfolders of com/example/myproject/jre/
  • to the source path
  • com/google/myproject/gwt/jre/java/util/UUID.java
  • most commonly used elements in the module XML file.
  • <inherits name="
  • herits all the settings from the specified module
  • <entry-point class=
  • Entry points are all compiled into a single codebase
  • when the onModuleLoad() of your first entry point finishes, the next entry point is called immediately.
  • Any number of entry-point classes can be added
  • <source path="
  • resources get copied into the output directory during a GWT compile.
  • client subpackage is implicitly added to the source path
  • <public path="path" />
  • treated as a publicly-accessible resource.
  • resources get copied into the output directory
  • the public subpackage is implicitly added to the public
  • <servlet
  • For RPC, this element loads a servlet class
  • mounted at the specified URL path
  • path=
    • anonymous
      anonymous on 14 Jan 11
       
      monting location
  • class="
    • anonymous
      anonymous on 14 Jan 11
       
      Which servlet class
  • URL path should be absolute
  • @RemoteServiceRelativePath attribute
  • you must configure a WEB-INF/web.xml in your war directory to load any servlets needed.
  • n development mode,
  • <script src="
  • external JavaScrip
  • <stylesheet src="
  • Extends the set of values
  • for an existing client property
  • <replace-with-class>
  • <generate-with-class>
  • <when-property-is
  • three different types of predicates are
  • <when-type-assignable
  • <when-type-is
  • <all>
  • <any>
  • <none>
  • GWT libraries are organized into modules
  • you want to inherit at least the User module
  • contains all the core GWT functionality
  • including the EntryPoint class
  • widgets and panels
  • History feature
  • Internationalization
  • DOM programming, and more
  • Low-level HTTP
  • Use the following syntax to cause an external JavaScript file to be loaded
  • before your module entry point is called.
  • as if you had included it explicitly using the HTML <script
  • loaded before your onModuleLoad() is called.
  • all included scripts will be loaded when your application starts, in the order in which they are declared.
  • associate external CSS files with your module
  • GWT.getModuleBaseURL() + "foo.css" in client code
  • module's public path
  • useful when
  • inheritance makes resource inclusion particularly convenient.
  • If you wish to create a reusable library that relies upon particular stylesheets or JavaScript files, you can be sure that clients
  • see the documentation for FileSet for a general overview
  • <public>
  • <super-source>
  • <source>
  • includes
  • excludes
  • defaultexcludes
  • casesensitive
  • By default, the patterns listed here are excluded.
  • defaultexcludes is true
  • <script src='myApp/myApp.nocache.js'></script>
  • <script> tags always block evaluation of the page
  • <img> tags do not block page evaluation
  • two simultaneous connections
  • The body.onload() event will only fire once all external resources are fetched, including images and frames.
  • GWT selection script
  • like a normal script tag
  • but the compiled script will be fetched asynchronously.
  • Parsing is blocked until externalScriptZero.js is done fetching and evaluating.
  • myApp/myApp.nocache.js completes
  • the compiled scrip
  • (<hashname>.cache.html
  • begins fetching in a hidden IFRAME (this is non-blocking).
  • onModuleLoad() is not called yet, as we're still waiting on externalScriptOne.js
  • body.onload() fires
  • onload='alert("w00t!")
    • anonymous
      anonymous on 14 Jan 11
       
      is the last line executed
  • put the GWT selection script as early as possible
  • because it won't block any other script requests
  • <img> tags are not guaranteed to be done loading when onModuleLoad() is called
  • <script> tags are guaranteed to be done loading when onModuleLoad() is called
  • multiple EntryPoints
  • will all be called in sequence as soon as that module (and the outer document) is ready
  • multiple GWT modules within the same page
  • each module's EntryPoint will be called as soon as both that module and the outer document is ready
  • EntryPoints are not guaranteed to fire at the same time
  • or in the same order
  • in which their selection scripts were specified in the host page
151More

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

code.google.com/...DevGuideRequestFactory.html
shared by anonymous on 10 Jan 11 - No Cached
  • Entity Proxies
    • anonymous
      anonymous on 10 Jan 11
       
      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
1More

Business Intelligence solution with Java - 0 views

business.ezinemark.com/-development-7d2d3bd62833.html business intelligence java development
shared by enderson james on 16 Feb 11 - No Cached
  • enderson james on 16 Feb 11
     
    Business Intelligence solution plays important role to drive for organization. Aegis offering business intelligence software with latest java technology and tools.
3More

Lucid Imagination » Don't Use Java 7, For Anything - 1 views

www.lucidimagination.com/...dont-use-java-7-for-anything java java7 programming
shared by Stefano Locati on 31 Jul 11 - No Cached
  • In case you upgrade to Java 7, remember that you may have to reindex, as the unicode version shipped with Java 7 changed and tokenization behaves differently (e.g. lowercasing).
  • Unfortunately it contains hotspot compiler optimizations, which miscompile some loops. This can affect code of several Apache projects. Sometimes JVMs only crash, but in several cases, results calculated can be incorrect, leading to bugs in applications
  • Stefano Locati on 31 Jul 11
     
    Unfortunate first major release under Oracle stewardship.
11More

Page 2 - Java Developers Leery of IBM-Sun Merger - 0 views

www.eweek.com/...1 java
shared by Baron M on 01 Apr 09 - Cached
  • IBM still runs basic physics last I checked and has deep resources in research to throw at any problem it wants
  • with more money and influence than nearly all of their competitors
  • both companies are highly invested in Java, which means it will continue, but in what form we have no idea
  • ...7 more annotations...
  • IBM is not interested in Sun software but in the Sun hardware and storage
    • Baron M
      Baron M on 01 Apr 09
       
      different perspective
  • pose a number of integration issues for IBM Software Group
  • expect that IBM will take the long view, that an open, flourishing ecosystem around Java will be the tide that lifts all boats
  • some observers say IBM would do well to merge the best parts of both platforms into one.
  • IBM has been a proponent of open standards in the Java ecosystem, and I expect that will continue
  • shed a lot of the weaker products (and a significant number of redundant staff)
    • Baron M
      Baron M on 01 Apr 09
       
      conclusion: SUN and JCP suck, so they deserve this. God bless java and java dependent vendors.
17More

Java Developers Leery of IBM-Sun Merger - 0 views

www.eweek.com/...-Leery-of-IBMSun-Merger-411968 java
shared by Baron M on 01 Apr 09 - Cached
  • 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
      Baron M on 01 Apr 09
       
      this is damn TRUE!
  • IBM likes to create these 'boil the ocean' kinds of solutions
    • Baron M
      Baron M on 01 Apr 09
       
      this is the GENERAL PRACTICE of IBM and Oracle
  • IBM could wind up having six different JVM [Java Virtual Machine] implementations
    • Baron M
      Baron M on 01 Apr 09
       
      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
      Baron M on 01 Apr 09
       
      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
1More

Building and Running ICEfaces Examples with Maven - ICEfaces - ICEfaces.org Community Wiki - 0 views

wiki.icefaces.org/...g+ICEfaces+Examples+with+Maven building running icefaces application jsf java javaee
shared by Hendy Irawan on 24 Apr 11 - No Cached
  • Hendy Irawan on 24 Apr 11
     
    The maven2 poms and jars for this distribution are located in the following repository location
1More

Eclipse Scout Blog - 0 views

www.bsiag.com/scout project eclipse framework SDK platform business application overview blog scout
shared by Hendy Irawan on 24 Apr 11 - No Cached
  • Hendy Irawan on 24 Apr 11
     
      Eclipse Scout: "Hello World" App mzi | 23. March 2011 um 08.40 Uhr | Kategorien: General | Keine Kommentare | Install Scout: See the recent blog post Create Scout App: See new "Hello World" wiki tutorial Deploy to Tomcat: Wiki tutorial again Having Eclipse Scout and Tomcat installed all this should take you less than 15 minutes. If you happen to be at the Eclipse Con right now you may skip the download part, visit our boot #12 or attend our tutorial and get our Scouty memory stick with everything on it
« First ‹ Previous 81 - 100 of 108 Next ›
Showing 20▼ items per page