» tagged pages
» logout

sorted by: recent | see : popular
Content Tagged with SourceLabs + Java

SourceLabs News

SourceLabs Debuts New Class of Tools for Open Source Linux and Java (Press Release)(March 18, 2008)

CNET News – “Open-source support company SourceLabs on Tuesday launched a subscription service aimed at Linux developers and IT administrators who do their own support.”
(March 18, 2008)

O’Reilly Open Source – “Developers and open source system users will be particularly interested in a SourceLabs announcement of a service called Self-Support Suites that has been in beta since December.”
(March 18, 2008)

eWeek’s Linux-Watch – “A small start-up based in Seattle has started selling a ‘self-support’ tool for developers working with Java and/or Linux.”
(March 19, 2008)

SourceLabs is covered in the largest German IT publication – “Mit den “Self-Support Tools” will SourceLabs eine Alternative zu klassischen Supportverträgen bieten.”
(March 20, 2008)

SourceLabs builds momentum in Japan
(March 18, 2008)

Linux Magazine (Brazil) – “A SourceLabs pretende oferecer, através de ferramentas de self support , uma alternativa ao sistema clássico de suporte atualmente adotado pelo mercado corporativo.”
(March 22, 2008)

IT Jungle – “If you are a developer working at a major corporation or a small company and you want to use Linux and open source tools to create Java applications, there is very little possibility that your company is going to let you do that without getting tech support for the Linux and tools that you use.”
(March 18, 2008)

Seattle Times – “I keep waiting for a big tech company to buy SourceLabs, an open-source software and tools developer in Pioneer Square. Maybe the new product it’s launching today, SourceLabs’ Self-Support Suite, will speed the process.”
(March 18, 2008)

LinuxDevices.com – “A small start-up based in Seattle has started selling a ‘self-support’ tool for developers working with Java and/or Linux.”
(March 18, 2008)

GigaOm: Ostatic – “Could automated software support solutions come to the rescue? The jury’s still out on that, but I was interested in today’s announcement from SourceLabs regarding new Linux and Java self-support tools.”
(March 18, 2008)

Northwest Innovation – “Seattle-based SourceLabs said Tuesday that it has rolled out new tools to help support open source Java and Linux software.”
(March 18, 2008)

SysCon Media – “SourceLabs announced the availability of SASH 2 complete with a major new milestone – integrated support for Apache Tomcat.”
(Sep 9, 2007)

commons-codec

Commons Codec contains some general encoding/decoding algorithms, including phonetic encoders, Hex and Base64 encoders, and a URL encoder. The phonetic encoders are language encoders, which are useful in applications such as search engines, spell-check functions, and digital dictionaries. Hex and Base64 encoders are useful in applications that use characters to represent binary data. The URL encoder comes with more features and is considered a replacement for the JDK classes URLEncoder and URLDecoder.

SourceLabs covers Codec in its Self-Support Suite for Linux and Open Source Java

commons-daemon

An API that can be used to run executables or java applications as Windows service or UNIX daemon.

SourceLabs covers Commons-Daemon as part of its Self-Support Suite for Linux and Open Source Java

quartz

Quartz is an enterprise-class job scheduler for integration with stand-alone Java applications and full-scale J2EE applications.

SourceLabs includes Quartz in its Self Support Suite for Linux and Open Source Java offering.

cglib

cglib is a set of utility classes that can be used to generate and load Java classes at runtime.

SourceLabs includes CGLib in its Self Support for Linux and Open Source Java offering.

Spring

Spring is a Java/J2EE application framework that assembles components via configuration files. Spring is an open source project but is developed by engineers with Interface 21, and Spring Framework is a trademark of Interface 21. Spring is supported by a number of companies including Interface21 and SourceLabs, and is covered in SourceLabs Self-support Suite for Linux and Open Source Java

Spring’s core technical selling point has been the Inversion of Control design idea, where programming is focused on interfaces rather than classes. Spring’s design comes from the book Expert One-on-One J2EE Design and Development by Rod Johnson.

Mission

Spring’s mission statement as articulated by Interface21 includes these points:
  1. J2EE should be easier
  2. Interfaces > Classes
  3. JavaBeans are good for configuration
  4. OOP > implementation technology (J2EE)
  5. Testability is important and should be easier
  6. Frameworks shouldn’t force recoverable exception catching

And these direct points about Spring

  1. Spring should be a pleasure to use
  2. Spring APIs should not be a dependency
  3. Spring should not compete with good existing solutions like JDO and Hibernate.

External Links

From Rod Johnson

Reviews of Spring

Critiques of Spring

CompareJ2EESolutions

There are a number of open source competing Java (J2EE) development solutions. What are the strengths and weaknesses of popular options for similar tools and tasks?

Presentation

Goal Projects Comparison
Javascript kits Yahoo! UI Library, Dojo, Prototype, DWR JavaScript Library

Code

Goal Projects Comparisons
Templating engine freemarker, velocity, JSP+JSTL, sitemesh, tiles, Tapestry, Wicket Java Templating Engine
Web services axis, axis2, Xfire Axis vs XFire
Logging commons-logging, log4j, slf4j, JDK 1.4 Java Logging
Web frameworks struts, struts2, Spring MVC, Spring Web Flow, Tapestry, Wicket springmvc-vs-struts
IoC (inversion of control) Spring, PicoContainer, Hivemind
Persistence Hibernate, Spring JdbcTemplate

Tools

Goal Projects Comparisons
IDE Eclipse, NetBeans, IntelliJ IDEA eclipse-vs-netbeans
Build Maven, Ant
VCS Subversion, CVS
Unit testing JUnit, relaxng
Web testing JWebUnit, Cactus
Load testing JMeter, grinder jmeter-vs-grinder
Mocking jmock, EasyMock

App Servers
Goal Projects Comparisons
JSP/Servlet Tomcat, Jetty, Resin Tomcat-vs-Jetty-vs-Resin
JSP/Servlet + EJB JBoss, Geronimo JBoss-vs-Geronimo
Tomcat integration with Apache httpd mod_jk, mod_proxy, mod_proxy_ajp Tomcat httpd integration

Java Artifact Repository (CJAR) at SourceLabs

Java Artifact Repository live

I have been annoyed by lack of comprehensive artifact repository in Java community. Perl has CPAN, Python has PyPI, Ruby has Gems and to this moment Java did not have something that would resemble CPAN as Wikipedia put it.

And therefore I wrote my version of CJAR, which is based on Maven repository structure but is not Maven specific and has some additional services available:

- search artifacts by name or content: class names etc.;

- quickly getting information about artifacts – license, bytecode version, availability of javadocs and sources;

- creation of Ant or Maven build file based on selected artifacts;

- jardiff that allows comparing different versions of Jars and see precisely what has changed at class and package levels: new and removed classes, methods, and method signatures;


I am working for SourceLabs and the company supports the service and hosts it on its servers at:

http://area51.sourcelabs.com/cjar/app


It is just a beginning – many things needs to be done:

* repository needs to be filled with artifacts;

* POM files needs to be cleaned;

* missed information needs to be put into POMs and MANIFEST files;

* java artifacts needs to be signed by they authors or trusted persons;

* more information should be available about artifacts;

Please visit the CJAR site and leave feedback, together we can fill the gap in Java infrastructure!

SourceLabs: LabNotes

Reining in Bloatware

One of the issues with the “traditional” software world is the constant incentive to add more and more features to a product – primarily because this is how “differentiation” is traditionally measured (rather than quality, stability, etc.) The most notable and infamous examples of this are the Microsoft Office Suite – where Microsoft defeated competitiors in the word processing, spreadsheet, and desktop database markets by providing more comprehensive features in the early 90s, and then kept the feature train rolling. In Microsoft’s case, the motivation is to give users a “good” reason to upgrade. Similar phenomina are true in the server software world. Many people never use the “latest and greatest” features in, say, an enterprise database management system. But – very often, they still choose these systems based on feature/functionality. Why? Well, perhaps because information they care about more (like, say, stability of the code base, interoperability, reliability, etc.) isn’t readily available (and in fact many vendors write clauses into their licenses to “prevent” such data from being generated and published.)

The issues with bloatware are pretty severe when you’re talking about a large-scale deployment (100s or 1000s of servers) for large applications. “Feature frenzy” means its harder to develop on a platform (too much to learn just to do basic things), harder to test out what you’ve built (dev environments and production environments tend to be very different), harder to manage, and harder to support. Add up all those additional costs, and chances are it far outweighs the benefit of the “latest and greatest” features – even if you do happen to be using them.

Open source tends to be different. Take open source Java, for example – a topic near and dear to SourceLabs’ heart. You can get up and running on Tomcat in under an hour, and build simple web applications (it’s some work to download, install the database and configure it correctly, alas…) Compare this to many commercial J2EE application servers. Some of them come on 10s of disks, and can take days to install. I recently encountered one Proof of Concept where it took over 5 system engineers from a vendor ONE WEEK just to install their application server and get it running. Want to do something more complicated? Add the SourceLabs SASH stack to the mix, and you have a platform capable of most things – save distributed transactions. more advanced management capabilities and messaging – than you get from a “full blown” J2EE application server. We have yet to compare the TCO for the two alternatives, but we have several customers who have estimated 20-40% less costs than with a “proprietary” alternative.

That’s before you take into account that the license for the open source software is free :-)

SourceLabs: LabNotes

dom4j

dom4j is an easy to use, open source library for working with XML, XPath, and XSLT on the Java platform, using the Java Collections Framework, and with full support for DOM, SAX, and JAXP.

SourceLabs covers Dom4J in its Self Support Suite for Linux and Open Source Java

User:willpugh

Hi, I’m Will Pugh.

I’m currently the Chief Architect at SourceLabs, where we are bringing dependable Open Source to enterprises. I’m interested in many different areas, but right now, I find myself focusing on SASH and our Cert-7 process.

Projects I’m looking at for fun:

  • OpenPegasus This looks like a pretty interesting peice of Enterprise Management software built off the CIM stuff. I haven’t dug into it too deeply yet to see how much is there.
  • Ruby Source Code Management APIs for using Ruby to interact with SCM

velocity

Velocity is a Java-based template engine.

SourceLabs covers Velocity in its Self-Support Suite for Linux and Open Source Java

XMLbeans

XMLBeans is a technology for accessing XML by binding it to Java types. It provides full XML schema support and full XML infoset fidelity.

SourceLabs includes XMLBeans in its Self Support for Linux and Open Source Java Suite

Jakarta-Commons

The Jakarta Commons components are a group of Java components that implement common functionality. They are a great place to start looking when you need a utility function that you know a million other people must have written before, and you’d really like to not re-write it.

A few examples of the ones that are pretty popular are:
  • Collections—This is a set of many common/useful collection classes that are not included in the JDK
  • Lang—Contains a lot of classes for extending the Core Java Library. This includes things like utilites for HTML escaping a string, or creating a mutable integer object.
  • Logging—Contains a wrapper around most of the common logging models
But there are tons more dealing with topics from Database access to parsing XML configuration files to uploading files via HTTP.

In addition to the released projects there is also a sandbox area where more experimental components live.

All the Jakarta Commons projects are covered in SourceLabs Self-support Suite for Linux and Open Source Java

log4j

Log4j is a logging package written in Java. This is now part of the Apache Logging Services.

SourceLabs includes the ability to capture, search, sort and correlate Log4J messages with millions of datapoints as part of its Self-Support Suite for Linux and Open Source Java

Tomcat

Apache Tomcat is the servlet container that is used in the official Reference Implementation for the Java Servlet and JavaServer Pages technologies. These are Java standards for developing dynamic web applications. Tomcat is widely used, although some people would like to see a better management console.

Tomcat is covered by SourceLabs Self-Support for Java offering and is also included in JBOSS.