| Recent Entries |
|
16. Mar 2010
|
|||||
|
15. Mar 2010
|
|||||
|
13. Mar 2010
|
|||||
|
10. Mar 2010
|
|||||
|
09. Mar 2010
|
|||||
|
08. Mar 2010
|
|||||
|
04. Mar 2010
|
|||||
|
03. Mar 2010
|
| Seam News | (133) |
| Seam | (105) |
| Web Beans | (60) |
| Contexts and Dependency Injection | (55) |
| RichFaces | (54) |
| JBoss Tools | (53) |
| Eclipse | (45) |
| JBoss Tools Eclipse | (40) |
| JavaServer Faces | (35) |
| Weld | (32) |
| Hibernate | (25) |
| Bean Validation | (24) |
| Java EE 6 | (14) |
| News | (9) |
| Asylum | (8) |
I'm pleased to announce the availability of our first Seam 3 module, Seam Remoting 3.0.0.Beta1. This release provides a CDI-based port of most of the AJAX remoting features that you know from Seam 2.x, and also introduces a new feature, the Model API. Please refer to the following links for downloads and documentation, and if you encounter any issues please use the issue tracking link to let us know about them. (Seam Remoting now has its own project in JIRA).
Also, stay tuned for a release of the Seam XML module in the next day, which will allow you to configure your CDI beans via an XML configuration file.
I'm very happy to announce the availability of the Tattletale 1.1, the Java dependency analyzer, release.
A lot of features have been added over the last year, so I'll give a brief run-down of some of them. See our documentation for full details.
Profiles
Tattletale now features known profiles
, which are well-known APIs targeting the Java Standard or Java Enterprise platforms.
The list of profiles are
- Java 5 and Java 6
- Java Enterprise Edition 5 and Java Enterprise Edition 6
- Spring 2.5 and Spring 3.0
- Contexts and Dependency Injection (CDI) 1.0 (JSR-299)
- JBoss Seam 2.2
Adding profiles to your configuration will resolve any dependencies on the specified profiles.
New reports
Tattletale 1.1 also features new reports.
- Sealed information
- Signed information
- Unused Jar archives
- Circular Dependency
which should help you make your product/project distribution even better.
Other enhancements
A lot of small/large enhancements also went in the release.
- Ability to exclude directories from the scan
- Ability to filter results from the reports
- Apache Ant support
- Apache Maven support
These features will allow you to integrate Tattletale into your QA environment and automate getting daily reports.
I want to thank the people that helped out with the release over the last year, especially Torben Jaeger who did a lot of work :)
For Those About to Rock, We Salute You !
As the title says, Seam 2.2.1.CR1 is now available for download - you can get it from Sourceforge here:
http://sourceforge.net/projects/jboss/files/JBoss%20Seam/2.2.1.CR1
Release notes can be found here:
And docs can be found here:
http://docs.jboss.org/seam/2.2.1.CR1
Enjoy!
I'm often asked to identify what projects I'm working on at Red Hat, or what group I'm a part of. My response reads like a laundry list:
- Seam
- Weld
- CDI TCK
- Arquillian
...and sometimes I'm really not sure if I can classify myself as a member of a certain project (e.g., RichFaces). Other developers that hang around here likely have a similar story. Eventually, we just settle on the response, I'm part of the in.relation.to crowd.
However, for people that don't know this blog, or its history, this description makes no sense whatsoever. Which made me come to the realization that we lack a true identity within the JBoss Community. I believe this detracts from the spirit of integration and coordination between projects. As my first order as Community Liaison, I set out to fix that.
Seam is often described as the glue that brings together a myriad of standard and third-party Java EE technologies. The glue that brings us together is that we are all working on creating tools and frameworks for the application developer (some use the term enterprise web developer
). This purpose not only unites those of us creating these technologies, but also unites us with the folks that consume these technologies. So, to align the name of our group with the common organizational group name of our community members, we have chosen this name for our group:
Application Developer Projects Group (or the more casual name, App Dev Group)
This group is a loose knit collection of projects which people often view as their development stack:
- Seam
- JBoss Tools
- Weld (CDI)
- RichFaces (JSF)
- Hibernate Validator (Bean Validation)
- Hibernate (JPA)
- Hibernate Search
- ...perhaps others
We also recently formed the JBoss Testing Group that encompasses Arquillian, ShrinkWrap, JSFUnit, and other testing tools. Some of us are a part of that group too, myself included.
When we address this audience, or seek to describe where we fit in the JBoss community, we can really establish the connectedness by using the term App Dev
, or Application Developer Projects, to show we are thinking about the concerns across technologies. So there you have it, our group name.
Weld Extensions is set of portable services and utility classes for CDI which make up a good base layer for extension and application development. You can read more about the sort of portable extensions we are planning in this interview I gave.
Injectable Logger
Weld extensions includes an injectable logger, based on slf4j. By default, the fully qualified class name will be used as the category:
class Sparrow {
@Inject
private Logger log;
...
}
Alternatively you can specify a category:
class Finch
{
@Inject @Category("Finch")
private Logger log;
...
}
Managed Resource Streams
Weld extensions also contains managed resource streams (the stream is automatically closed for you when the bean goes out of scope) for resources loaded from the classpath:
@RequestScoped
class ResourceClient {
@Inject @Resource("/META-INF/config.xml")
InputStream inputStream;
public void parse() {
// TODO Parse the inputStream!
}
}
Here the stream will be closed for you when the request ends. Of course, you often don't know the file name you want to parse at development time, so you can also specify the name at runtime:
@SessionScoped
class ResourceClient {
@Inject ResourceProvider resourceProvider;
public void parse(String fileName) {
InputStream is = resourceProvider.loadResourceAsStream(fileName);
// TODO parse the XML!
}
}
Here, the stream will be closed for you when the session is destroyed.
At the moment, only loading resources from the classpath is supported, but we'll add support for loading resources from the servlet context soon. As you can see, this can greatly simplyfy using input streams!
Extensions to the core CDI programming model
Gavin has blogged about a number of improvements to the CDI programming model, some of which are available in this release. Included are:
- Bean declaration at the constructor level
- The exact qualifier
- Compound name defaulting
- Generic beans
The extensions package is currently available in Maven, and we welcome feedback, either in the Weld forum or in JIRA. Thanks for this release go to David Allen for the injectable logger and to Gavin King and Stuart Douglas for the extensions to the core CDI programming model.
| Showing 1 to 5 of 650 blog entries |
|
|