I see a new behaviour with VFS3 in JBoss AS. Earlier in AS-5/6 (with
VFS2) and AS-4 (without any VFS), to try out some quick fixes, i used to
rename existing jar files to end with .bak name and replace them with
the new patched jar file. So for example, if i had a fix in
jboss-ejb3-core.jar, i would:
1) Rename the JBOSS_HOME/common/lib/jboss-ejb3-core.jar to
2) Place a patched jboss-ejb3-core.jar in JBOSS_HOME/common/lib
3) Restart the server
The server would then pickup the new patched jar file and ignore the
.bak file. After testing the fix, i would then revert back to the
original jar file by renaming it back to its original name.
However, with the recent upgrade to VFS3 in AS trunk, i notice that even
the .bak is used for classloading (following is the output from
-verbose:class JVM argument):
[Loaded org.jboss.ejb3.EJBContainer from
Looks like VFS3 picks up this non .jar suffix file for classloading. Is
this expected? Shouldn't it be looking for only .jar files (atleast in
We are happy to announce the initial release of Flies 1.0
and its availability now for the jboss.org community for
translation work at http://translate.jboss.org/
Flies is a web-based system for translators to translate
documentation and software online using a web-browser. It
is written in Java and uses modern web technologies like
JBoss, Seam, GWT, Hibernate, and a REST API. It currently
supports translation of Publican documentation through PO
files. Projects can be uploaded to and downloaded from a
Flies server using a Maven plugin or a Python client.
For developers and writers: By using Flies for your document
translations, you can open up your project for translations
*without* opening your entire project in version control.
For translators: No need to deal with PO files, gettext or
a version control system - just log in to the website, join
a language team and start translating, with translation memory
(history of similar translations) and the ability to see updates
from other translators in seconds.
The first release has been deployed at http://translate.jboss.org/
and is ready to accept documentation for jboss.org projects
for translation. Visit http://community.jboss.org/wiki/Flies for
instructions on how to get started.
The Flies wiki documentation is here:
If you have questions, feedback, or want to have a JBoss project
hosted, please contact the mailing-list
https://lists.jboss.org/mailman/listinfo/jboss-l10n or the IRC
channel #flies on freenode.net.
The Flies project is Free Software, licensed under the LGPL 2.1.
To contribute to the Flies project, visit the project page:
On behalf of the Flies Team:
Senior Software Engineer
Engineering - Internationalisation
I've updated the Executive Summary with the targeted release dates for the
final release of AS 6.
This is a very aggressive schedule with only 3 weeks till code freeze. If you have JBAS JIRAs assigned to you,
it would help minimize destabilization during the end game to get those fixed, tested, and committed as
soon as possible. I will be triaging the outstanding issues as well and make Edits accordingly.
Community participation and contributions are welcome as always. Be sure to attach a patch to your
JBAS JIRA for consideration into the Final release.
JBoss, by Red Hat
Over the week-end I've packaged JBoss AS 6 into HomeBrew (a Mac OS X packaging system made of git and ruby).
I've discovered that our scripts are not symlinks friendly and will fail (often not finding the jars).
I've fixed the issue but I wanted to get a review of my work. Let me know if you thing there could be a problem, otherwise I'll apply them to SVN.
I've basically replaced
# Extract the directory and the program name
# takes care of symlinks
while [ -h "$PRG" ] ; do
ls=`ls -ld "$PRG"`
link=`expr "$ls" : '.*-> \(.*\)$'`
if expr "$link" : '/.*' > /dev/null; then
Full details and full patch available here https://jira.jboss.org/browse/JBAS-8670
The Logging I18n tool is (finally) ready! Most of the functionality
specified in the requirements document  is present, which a few minor
To use the tool, just add it in to your project dependencies (use
"provided" scope though, so that it doesn't become a transitive
dependency for everyone). Implementations for your annotated interfaces
will automatically be generated.
The maven coordinates are
"org.jboss.logging:jboss-logging-tools:1.0.0.Beta1", and the official
source is currently at https://github.com/dmlloyd/jboss-logging-tools
See http://docs.jboss.org/jbosslogging/latest/ for details on the
Special thanks to Kevin Pollet and James Perkins for doing essentially
all the work on this! :-)
A second round of SwitchBoard/jboss-injection integration in AS trunk is
going to happen today. This mainly brings in EJB3 containers integrated
with SwitchBoard and jboss-injection. AS trunk is _open_ for commits and
you can go ahead with any of your commits into AS trunk. This mail is
more of a FYI since you might see some testsuite regressions (embedded
and smoke-test will be passing) which I'll be fixing once I get the
Now that the branch for 6.0.0 CR1 has been created, I'll start merging
the SwitchBoard/jboss-injection changes from switchboard-integration
branch to AS trunk. I'll be starting the merge process in a few minutes
from now. I'll be sending out a mail once the merge completes
successfully with embedded and smoke-tests passing. Till that time,
please do not commit anything to AS trunk.
Once the merge is completed, the SwitchBoard/jboss-injection work will
continue on AS trunk. All other commits to AS trunk can continue as
usual. However do note that you might see some failures/instability in
the AS testsuite when the switchboard work is in progress. I'll be
committing to trunk only when the embedded/smoke-test pass fully, but
can't promise the same for the full testsuite run. I'll be watching the
AS testsuite run for any regressions and will be fixing them as necessary.