Group items tagged

"Essential is a project to create a workbench for applying Model Driven Development (MDD). The workbench allows to experiment with models, metamodels, templates and transformations in an integrated environment. The main focus is to provide a declarative environment oriented to prototyping and evolving custom DSL and MDD tools in a quick and clean way. Motivation for a new tool Essential.Meta. DSL for Metamodelling Modelling with Essential StringTemplate, the template engine"

"A hub for integrating your enterprise with the rich information available on the Web, the WSO2 Mashup Server leverages popular Web 2.0 formats and protocols into your service platform. Combining simple yet rich mashups with reusability, security, reliability, and governance, the WSO2 Mashup Server includes features for connecting Web Services to humans through Web pages, gadgets, feeds, instant messages, email and more. The WSO2 Mashup Server offers: Go Cloud-Native WSO2 Mashups as a Service gives you instant self-service provisioning, multi-tenancy and has built-in monitoring and metering capabilities. Increase productivity Reduce cost Gain more control Avoid vendor lock-in The ideal platform for defining composite services for user interfaces and mobile applications. A simple way to deploy services developed in JavaScript. Access to REST and WS-* web services, feeds, and scraped web pages with data scripted together quickly using common Web developer skills, the result being a new service, or a web page, gadget, email or instant message. The ability to secure hosted Mashups. Support for both recurring and longer-running tasks and service lifecycles. Monitoring, configuration of security and quality of service settings such as throttling. With no up-front license agreements or subscription fees, getting started with the WSO2 Mashup Server requires less developer effort, ensuring faster ROI."

"Hibernate OGM is an attempt to store data in a NoSQL data grid using he Hibernate Core engine rather than rewriting a JPA engine from scratch. The benefits are fairly obvious: reimplementing the complex JPA specification is a lot of work a new implementation would mature at a rather slow rate and risk of bugs would be high Hibernate is familiar to many people Earlier designs for this feature in Infinispan can be found on http://community.jboss.org/wiki/DesignofJPA-likeAPIandNewFineGrainedreplication"

"Spring Social is an extension of the Spring Framework that allows you to connect your applications with Software-as-a-Service (SaaS) providers such as Facebook and Twitter. Features An extensible service provider framework that greatly simplifies the process of connecting local user accounts to hosted provider accounts. A connect controller that handles the authorization flow between your Java/Spring web application, a service provider, and your users. Java bindings to popular service provider APIs such as Facebook, Twitter, LinkedIn, TripIt, GitHub, and Gowalla. A sign-in controller that enable users to authenticate with your application by signing through a service provider. "

This page contains the latest compiled builds of Pentaho Data Integration (Kettle) community edition.  The builds are based on source code downloaded daily from SVN. Why download these snapshot builds? You want the latest version - to get the latest features in PDI. You want a more stable version - PDI point releases (e.g. 4.0.1) can include important bug fixes - see the PDI JIRA system for a full list of known issues. You need a bug fixed - You're struggling with a critical bug which has been fixed in a more recent version. To save time - You haven't got the time and/or inclination to learn about how to download PDI from SVN and build your own version.

JDBC realm has a lot of attention in recent months. This blog summarizes the evolution of the JDBC realm implementation in GlassFish and explains how the latest implementation works. I would like to thank Jean-Baptiste, and Richter for their contributions and comments. The participation from the open source community definitely helps everyone. I encourage all of you to give feedback, participate, and help evolve this feature further. GlassFish always had the capability for anyone to plug-in a realm. Implementing a custom realm in the Sun Java System Application Server EE 8.0 is described in the article Authentication Using Custom Realms in Sun Java System Application Server. In S1AS 7.x, there is a JDBC Realm bundled in sample. Jean-Baptiste formally filed an enhancement and provided a clear text version of JDBCRealm for GlassFish. Richter wrote another implementation because the GlassFish JDBCRealm at that time not compatible with Tomcat.

"Let's imagine we want to create an application for orders. People can sign in to the system, place orders for various items, check out and have them sent to their address. Very simple, but we can show a lot of things here. As we expect to be writing more than one application of this type and as we also would like to be able to express the structure of the application on a business level (one of the major drivers for DSLs and MDSD for that matter), we come up with the idea of using a DSL to describe what the application does. Defining the DSL is what we did last week. This week, we need to map the concepts of the DSL to some code and some APIs we're going to program against. So, we're going to create a set of code templates for a code generator that can then read our DSL models and create persistence code for us."

A pretty common request that I hear is how do you build a wizard in RichFaces. So, that's exactly what we are going to build. You come into a bar and on each table there is a screen via which you place an order. You click to start an order, a wizard is launched where you enter all the required information and place the order. We will also have the ability to view all placed orders. Additionally, we will be able to change the look and feel of the ordering screen using RichFaces' skinnability feature.

http://www.vipindianpakistanigirls.com/2016/09/abu-dhabi-pakistani-escorts.html http://www.vipindianpakistanigirls.com/2016/09/abu-dhabi-indian-escorts.html http://www.vipindianpakistanigirls.com/2016/09/massage-escorts-in-abu-dhabi.html http://www.vipindianpakistanigirls.com/2016/09/cheap-escorts-in-abu-dhabi.html http://www.vipindianpakistanigirls.com/2016/09/model-escorts-in-abu-dhabi.html http://www.vipindianpakistanigirls.com/2016/09/vip-russian-escort-in-abu-dhabi.html http://www.vipindianpakistanigirls.com/2016/09/vip-arab-escort-in-abu-dhabi.html http://www.vipindianpakistanigirls.com/2016/09/russian-escort-in-abu-dhabi.html http://www.vipindianpakistanigirls.com/2016/09/arab-escort-in-abu-dhabi.html

" Given that web service invocations are always remote across the internet, developing rigorous and responsive web service client applications has always been a challenge for architects and developers working with SOA. JAX-WS 2.0 comes with one effective solution to this problem: asynchronous web service invocation, with which a web service client may interact with a web service in a non-blocking, asynchronous approach. In this article, we will provide an exposition of this technology with examples built upon the reference implementation. Our examples utilize JDK 5.0, JAX-WS 2.0 reference implementation (RI), and Tomcat 5.5. JAX-WS 2.0 requires JAXP 1.3. To replace the JAXP 1.2 released with JDK 5.0 with this newer version, one approach is to download the JAXP 1.3 RI, and copy the endorsed directory under /lib of its installation home to %JAVA_HOME%/jre/lib. We need to copy the jaxp-api.jar of JAXP 1.3 RI to %JAVA_HOME%/jre/lib/endorsed as well. To make Tomcat 5.5 work with JAX-WS 2.0, readers need to copy all the .jar files under the /lib directory of the JAX-WS 2.0 RI installation to the %CATALINA_HOME%/shared/lib directory. As of this writing (in addition to Tomcat 5.5), Sun Java System Application Server 9.0, GlassFish, and Celtix also support JAX-WS 2.0. xFire is in the process of completing its implementation of this specification. Since asynchronous web service invocation in JAX-WS 2.0 is built upon the concurrent programming support in JDK 5.0 introduced with the java.util.concurrent package, we will start from there."

There was a recent outburst in blogs on the topic of Groovy and how it compares to Java. Although I respect the youthfull entusiasim of Groovy and Co. working on this little exercise I'm just perplexed by the "WHY?" in this whole discussion. Let me just say again: W H Y ?!?! 1. Practically no one cares about Groovy (let alone Groovy++ strap-on) beyond Grails community. So this language just as "widely accepted" as Ruby (at least for enterprise software development) 2. If you know Java it's equally "challenging" to pick up either Groovy or Scala. Don't let anyone insult your intelligence by claiming that Scala syntax is somehow more complex than Groovy. In both languages you will need to adapt to functional thinking - and that's where you will have to spend a couple of weekends… 3. If you know Groovy - you already know 90% of Scala (different syntax and few extra features can be picked up in the evening) 4. Scala is designed by people who have proper academic background, experience and talent in the area of language design - Groovy has never been that way (and anyone who dares to look inside of Groovy runtime or history of changes in it will attest to that). NOTE: it did come out rather strong - but that's how I feel about it and after some thinking I'll leave as is. Nothing personal to anyone reading it… 5. Scala as a post-functional language is years ahead of Groovy (static typing with best-in-business type inference, highly tuned mix of imperative and functional styles, powerful and done-right generics, etc.) 6. Groovy will ALWAYS be slower than Scala or Java (latest benchmarks put even Groovy++ about 50 times slower than Java) just by its nature unless someone changes the language and rebuilds the runtime from the ground up. 7. Once we get decent integration with Eclipse, NetBeans and IDEA for Scala, the Groovy will lose its only serious advantage

"Activiti is a Business Process Management (BPM) and workflow system targeted at business people, developers and system admins. Its core is a super-fast and rock-solid BPMN 2 process engine for Java. It's open-source and distributed under the Apache license. Activiti runs in any Java application, on a server, on a cluster or in the cloud. It integrates perfectly with Spring, it is extremely lightweight and based on simple concepts. "

A tutorial on how to create a web application using basic Spring MVC from spring-framework 3.0.5. We will design our web-based application based on the standard Spring MVC where request to the web-app will be routed to a Controller module, then to it's jsp View with data from our business Model

Emfatic is a text editor supporting navigation, editing, and conversion of Ecore models, using a compact and human-readable syntax similar to Java. The EPLed Emfatic now hosted at EMFT extends the Feb 2005 alphaworks release with support for EMF Generics, folding, "red squigglies", an EMF Type Hierarchy, hyperlinks, AutoEdits, and the possibility to define templates to speed up document creation, among other usability features. The best way to gain hands-on experience with Emfatic is to right-click on any .ecore file and choose Generate Emfatic source, a similar converter works in the opposite direction. Online help is also available. Emfatic itself builds upon Gymnast, a framework for jumpstarting text editors for custom Domain Specific Languages. Documentation on how to extend Emfatic, as well as on using Gymnast, can be found in this technical report.

Before you read, please look at this video, showing the core features of ECP. The EMF Client Platform is a framework to build EMF-based client applications. The goal is to provide a one-click application based on a given EMF model. Besides the EMF model no additional components have to be developed or generated. Therefore ECP provides a standard solution including the most common features needed for EMF-based client applications. This application can then be customized step by step. This can be done by extending ECP or replacing single components completly.

Provide mechanisms for integrating Java security providers into Eclipse: Applications that need to implement security related functionality require cryptographic services upon which to build. Java provides the Java Cryptography Architecture (JCA) as a mechanism for installing implementations of several interfaces used for cryptography, including MessageDigest, Signature, KeyStore, Certstore, and more. In a typical Java application, these implementations reside in the extensions directory of the JRE. In a dynamic Eclipse application, the appropriate packaging mechanism is in Eclipse plug-ins. The goal is to allow JCA to be used in an Eclipse environment while maintaining the programming model of the JCA subsystem. A related goal is to expose the configuration of the JCA system via an Eclipse-based user interface, allowing authorized users to inspect and modify the Security object.

"We are specialists in Pentaho Data Integration plugin development, if there's something you just can't do with a standard plugin then give us a call - we'll save you money on in-house development and get the work done faster. This is a list of some of the plugins we've developed and new plugins are being released on a regular basis. If you'd like to be notified when we release on just register for our news letter (we won't spam you and we'll never pass your address on to other parties.)"

"The Open Services for Lifecycle Collaboration (OSLC) is an open (creative commons) REST based service specification aimed at improving/simplifying Application Lifecycle Management (ALM) system integration. A number of aspects of ALM integration are covered by OSLC ranging from Requirements Management to Automation(Build/Deploy). The OSLC Change Management (CM) spec outlines a standard for creating, modifying, and querying for change requests (tasks) from OSLC based service providers. A goal of the Mylyn project is to implement a client for OSLC-CM (see [1]). Additionally, support for both OSLC Automation and OSLC SCM are part of the Mylyn restructuring proposal: http://www.eclipse.org/project-slides/mylyn-restructuring-review.html Once these plans have solidified, we can begin to fill out the roadmaps for each specification. "

"Jsvc is a set of libraries and applications for making Java applications run on UNIX more easily. Jsvc allows the application (e.g. Tomcat) to perform some privileged operations as root (e.g. bind to a port < 1024), and then switch identity to a non-privileged user. It can run on Win32 via the Cygwin emulation layer (see Cygwin for more information), however Win32 users may prefer to use procrun instead, which allows the application to run as a Windows Service. The sources are located in the src/native/unix subdirectory. In the future APR may be used to provide more portable platform support. "

"The Open Data Protocol (OData) is a Web protocol for querying and updating data that provides a way to unlock this data and free it from silos that exist in applications today. OData does this by applying and building upon Web technologies such as HTTP, Atom Publishing Protocol (AtomPub) and JSON to provide access to information from a variety of applications, services, and stores. Project Info odata4j is a new open-source toolkit for building first-class OData producers and first-class OData consumers in Java. "