changes in parsing with xb
by Alexey Loubyansky
There have been many fixes in the last two beta releases of XB that will
affect AS and other users.
Most noticeable changes/fixes are related to internal navigation across
schema structures during XML parsing. In simple words, XB is now (much)
more sensitive to validation issues (incorrect element order, etc).
Some files that could be parsed before, now (with default settings)
won't. WRT AS it would be e.g. vfs, aop xml etc.
To workaround this, you can set system property
xb.builder.useUnorderedSequence to true. This will make the order in
which elements from a sequence appear in xml not important.
Alternatively, you can call
JBossXBBuilder.setUseUnorderedSequence(boolean value) or use annotation
@JBossXmlModelGroup(kind=JBossXmlConstants.MODEL_GROUP_UNORDERED_SEQUENCE)
to bind classes to unordered sequences.
But this has to remain a workaround, not the default. There has to be a
good reason to use unordered sequences. Fix your XML and binding now.
The latest XB has not been integrated into the AS yet (although, I ran
some tests from the AS testsuite locally) due to dependency on changes
in VFS and deployers:
https://jira.jboss.org/jira/browse/JBVFS-99
https://jira.jboss.org/jira/browse/JBDEPLOY-173
The latest metadata release (1.0.0.CR17) requires at least XB 2.0.1.Beta3.
If you are using XB, please, try the latest beta.
Here are release notes for XB 2.0.1.Beta3
https://jira.jboss.org/jira/secure/ReleaseNote.jspa?version=12313320&styl...
and XB 2.0.1.Beta2
https://jira.jboss.org/jira/secure/ReleaseNote.jspa?version=12313217&styl...
15 years, 7 months
TEST, please ignore
by Jason T. Greene
$Subject
--
Jason T. Greene
JBoss, a division of Red Hat
15 years, 7 months
JBoss application deployment - Handling properties outside of ear folder.
by sittont
We are currently migrating our application into JBoss 5.0.1.GA application
server (currently running on Weblogic).
In our application we use several ear files per server, each points to a
separate properties directory that exists out of the ear file but is in use
only by the specific application deployed in each ear.
We encountered some problems to configure the JBoss server the same way:
When we put the properties folder outside of the ear directory (we currently
use ear directory structure and not .ear file) the resources in the
properties directory are not ‘seen’ upon server load. We also cannot put the
properties directory in the classpath as each ear file uses properties with
same name so it needs to be a solution that will be set per each ear file
(directory).
Does anybody had any experience with such implementation?
--
View this message in context: http://www.nabble.com/JBoss-application-deployment---Handling-properties-...
Sent from the JBoss - Dev mailing list archive at Nabble.com.
15 years, 7 months
Branch_5_x freeze is over
by Jason T. Greene
Now that CR1 is tagged, the freeze is over. The next release is
5.1.0.GA, and will focus on finishing the remaining console tasks, and a
stable release. More to come.
--
Jason T. Greene
JBoss, a division of Red Hat
15 years, 7 months
One Week Until CR1 Component Freeze!
by Jason T. Greene
We still have 11 updates, and only one week is left until freeze. We
also only have a week for catching regressions, so we should avoid
including anything at the last minute. Therefore, let me know if any of
these should *not* be moved to 5.1.0.GA (except for jboss-managed, which
has to be included), and if so, when they will be included.
https://jira.jboss.org/jira/browse/JBAS-6552
JBAS-6691 Upgrade JGroups to 2.6.10 Brian Stansberry
JBAS-6661 Upgrade Web Beans to 1.0.0.PREVIEW Pete Muir
JBAS-6636 Upgrade JBoss Cache to 3.1.0.GA Brian Stansberry
JBAS-6635 Upgrade JAXB to 2.1.9.patch Shelly McGowan
JBAS-6634 Upgrade JBossWS Native to 3.1.1.GA Alessio Soldano
JBAS-6633 Upgrade jboss-ha-server to 1.2.0.GA Paul Ferraro
JBAS-6621 Update jboss-managed to 2.1.0.GA Scott M Stark
JBAS-6564 Include JBoss Negotiation 2.0.3.SP1 Darran Lofthouse
JBAS-6364 Upgrade apache-beanutils to 1.8.0 David Walluck
JBAS-6052 Upgrade jboss-profiler-jvmti to final Clebert Suconic
JBAS-6652 Upgrade AOP to 2.1.0.GA Kabir Khan
--
Jason T. Greene
JBoss, a division of Red Hat
15 years, 7 months
JBoss Tattletale 1.0.0
by Jesper Pedersen
The JBoss Tattletale team released the first official release of the
application today.
JBoss Tattletale is a tool that can help you get an overview of the project
you are working on or a product that you depend on. JBoss Tattletale is
licensed under GNU Lesser General Public License (LGPL) version 2.1 or later.
The tool will provide you with reports that can help you
* Identify dependencies between JAR files
* Find missing classes from the classpath
* Spot if a class is located in multiple JAR files
* Spot if the same JAR file is located in multiple locations
* With a list of what each JAR file requires and provides
* Verify the SerialVersionUID of a class
* Find similar JAR files that have different version numbers
* Find JAR files without a version number
* Locate a class in a JAR file
* Get the OSGi status of your project
* Identify black listed API usage
JBoss Tattletale will recursive scan the directory pass as the argument for
JAR files and then build the reports as HTML files.
The list of current reports:
* Dependants
* Depends On
* Graphical Dependencies
* Transitive Dependants
* Transitive Depends On
* Class Location
* OSGi
* Eliminate Jar files with different versions
* Invalid version
* Multiple Jar files
* Multiple Locations
* No version
* Black listed API
* JAR archive
The packages includes the binaries plus both the user and developer
guides as PDF files.
We hope that JBoss Tattletale will help you in your development tasks !
Website: http://www.jboss.org/tattletale
Download:
http://sourceforge.net/project/showfiles.php?group_id=22866&package_id=31...
JIRA: https://jira.jboss.org/jira/browse/TTALE
Forum: http://www.jboss.org/index.html?module=bb&op=viewforum&f=306
15 years, 7 months
Branch_5_x Code Freeze
by Jason T. Greene
Now that we are starting to get reasonable hudson test results, the 5.x
branch is essentially frozen until we tag on Monday (tomorrow).
Please don't make any changes on the branch without checking with me
first. Thanks.
--
Jason T. Greene
JBoss, a division of Red Hat
15 years, 7 months
SecurityAssociation is empty after successful login.
by Martin Mucha
Hi,
I got cornered while trying to do some basic authentization/authorization.
I've got here two applications - prototype war (working), real ear
application (not working). While looking for error, I've set both of
them to use SAME application policy in login-config.xml.
Authentization succed in both of them, but
SecurityAssociation.getSubject returns null in ear app for some
reason. I've tried to fiddle a little with
"org.jboss.security.SecurityAssociation.ThreadLocal" property, but
nothing changed. Jbosssx client library is packaged in both war and
ear(here it is localed in nested .war) archive. In web.xml there are
no roles defined/requested - any authenticated user is authorized to
do anything. So where can be the problem? I'm out of ideas. Thanks in
advance for any help or hint.
martin.
for more details (testing jsp pages - simple one, with few lines of
scriptlet code) please look in
http://www.alfonz19.uvadi.cz/security/problemDescription.txt
15 years, 8 months
