VFS3 (in AS trunk) - Non .jar file handling
by Jaikiran Pai
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
JBOSS_HOME/common/lib/jboss-ejb3-core.jar.orig.bak
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
file:/NotBackedUp/jpai/business/jboss/wc/jbossas/trunk/build/target/jboss-6.0.0-SNAPSHOT/common/lib/jboss-ejb3-core.jar.orig.bak/]
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
this context)?
regards,
-Jaikiran
14 years
log.debugf usage leads to slow code
by Carlo de Wolf
Hi guys,
Just something I spotted in some random code:
log.debugf("Blah blah %s", value.toString().replace('\n', ' '));
I hope this is something isolated, because it completely obliterates the
allowance of not having log.isDebugEnabled().
Please be a bit more careful while using the new log API.
Carlo
14 years, 3 months
as trunk build and dependencies
by Alexey Loubyansky
I had to add the following dependencies to be able to build it. Has
anybody else seen these issues?
--- tomcat/pom.xml (revision 108213)
+++ tomcat/pom.xml (working copy)
@@ -166,6 +166,11 @@
<dependencies>
<!-- Compile (global dependencies) -->
+ <dependency>
+ <groupId>jfree</groupId>
+ <artifactId>jcommon</artifactId>
+ <version>1.0.2</version>
+ </dependency>
--- depchain/pom.xml (revision 108213)
+++ depchain/pom.xml (working copy)
@@ -1045,6 +1045,10 @@
<groupId>org.jboss.ws.native</groupId>
<artifactId>jbossws-native-services</artifactId>
</dependency>
+ <dependency>
+ <groupId>org.jboss.ws.native</groupId>
+ <artifactId>jbossws-native-core</artifactId>
+ </dependency>
--- weld-int/ejb/pom.xml (revision 108213)
+++ weld-int/ejb/pom.xml (working copy)
@@ -304,6 +304,11 @@
<artifactId>jboss-interceptors-api_1.1_spec</artifactId>
</dependency>
+ <dependency>
+ <groupId>org.jboss.spec.javax.servlet</groupId>
+ <artifactId>jboss-servlet-api_3.0_spec</artifactId>
+ </dependency>
Thanks,
Alexey
14 years, 3 months
Re: [jboss-dev] JBossAS 6.0.0.M5 Released
by Shelly McGowan
Marek,
Milestone 5 was intended to provide a stable release to the community while we continue
work for the CR1 milestone. The list of JIRAs are shown what has been resolved
between 6.0.0.M4 and the 6.0.0.M5 tag.
I had a request by a few project leads for a stable distribution of JBoss AS. While
doing that work, I decided to push/announce to the community.
Sorry for the confusion.
Shelly McGowan
JBoss, by Red Hat
----- Original Message -----
From: "Marek Novotny" <mnovotny(a)redhat.com>
To: "Shelly McGowan" <smcgowan(a)redhat.com>
Cc: "JBoss AS" <jboss-as(a)redhat.com>, "The Core" <thecore(a)redhat.com>, "JBoss.org development list" <jboss-development(a)lists.jboss.org>
Sent: Friday, September 24, 2010 4:56:33 AM GMT -05:00 US/Canada Eastern
Subject: Re: JBossAS 6.0.0.M5 Released
There is some mishmash. JIRA doesn't have any 6.0.0.M5 version and the
issues in Release notes have got Fix For Version 6.0.0.CR1, but as the
announcement says it is 6.0.0.M5. I am confused ;-)
Shelly McGowan píše v Čt 23. 09. 2010 v 20:53 -0400:
>
> Today I released MileStone 5 of JBoss AS 6. This release provides an interim stable release to the community
> while the work continues toward the first Candidate Release targeted for November.
>
> JBoss Application Server 6.0 Milestone 5 is available for download in the usual places:
>
> http://www.jboss.org/jbossas/downloads.html
>
> The release is also available in the nexus repository.
>
> https://community.jboss.org/wiki/AS600M5ReleaseNotes
>
>
> Shelly McGowan
> JBoss, by Red Hat
>
--
Marek Novotny
--
Seam Product Lead
Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno
Email: mnovotny(a)redhat.com
Office phone: +420 532 294 287, ext. 82-62 087
mobile: +420 608 509 230
14 years, 3 months
Re: [jboss-dev] JBossAS 6.0.0.M5 Released
by Shelly McGowan
Justin,
Yes, I'll change that link. You need to be logged in to JIRA to see the filtered Resolved issues.
Shelly McGowan
JBoss, by Red Hat
----- Original Message -----
From: "Justin Bertram" <jbertram(a)redhat.com>
To: "Shelly McGowan" <smcgowan(a)redhat.com>
Cc: "JBoss AS" <jboss-as(a)redhat.com>, "The Core" <thecore(a)redhat.com>, "JBoss.org development list" <jboss-development(a)lists.jboss.org>
Sent: Thursday, September 23, 2010 9:11:32 PM GMT -05:00 US/Canada Eastern
Subject: Re: JBossAS 6.0.0.M5 Released
When I go to https://jira.jboss.org/secure/IssueNavigator.jspa?mode=hide&requestId=123... from https://community.jboss.org/wiki/AS600M5ReleaseNotes I get an error. There error basically says:
The selected filter is not available to you, perhaps it has been deleted or had its permissions changed.
The selected filter with id '12313623' does not exist.
Justin
----- Original Message -----
From: "Shelly McGowan" <smcgowan(a)redhat.com>
To: "JBoss.org development list" <jboss-development(a)lists.jboss.org>, "JBoss AS" <jboss-as(a)redhat.com>, "The Core" <thecore(a)redhat.com>
Sent: Thursday, September 23, 2010 7:53:26 PM GMT -06:00 US/Canada Central
Subject: JBossAS 6.0.0.M5 Released
Today I released MileStone 5 of JBoss AS 6. This release provides an interim stable release to the community
while the work continues toward the first Candidate Release targeted for November.
JBoss Application Server 6.0 Milestone 5 is available for download in the usual places:
http://www.jboss.org/jbossas/downloads.html
The release is also available in the nexus repository.
https://community.jboss.org/wiki/AS600M5ReleaseNotes
Shelly McGowan
JBoss, by Red Hat
14 years, 3 months
Re: [jboss-dev] IcedTea6 compilation issue (JBMETA-224)
by Richard Opalka
OK,
What's the OpenJDK bug no. associated with it (so I could track it)?
My system configuration is:
---
$>uname -a
Linux opalka-notebook 2.6.34.7-56.fc13.x86_64 #1 SMP Wed Sep 15 03:36:55
UTC 2010 x86_64 x86_64 x86_64 GNU/Linux
$>java -version
java version "1.6.0_18"
OpenJDK Runtime Environment (IcedTea6 1.8.1) (fedora-42.b18.fc13-x86_64)
OpenJDK 64-Bit Server VM (build 14.0-b16, mixed mode)
---
Thanks,
Rio
On 09/23/2010 04:20 PM, Martha Benitez wrote:
> Hello Richard,
>
> I used the build mentioned in JIRA to build metadata 1.0.6 for EAP
> 5.1, and that is the latest build we have in Brew. However, as
> mentioned in JBMETA-224 this change still needs to make it upstream
> and that should be included in the next CP for RHEL5 but I don't know
> the dates. Somebody in the Java project CCd in this message may be
> able to give you more details.
>
> If you'd like, go ahead and reopen JBMETA-224 so we keep track of this
> issue.
>
> Regards,
> --
> Martha Benitez
> Richard Opalka wrote:
>> Hi folks,
>>
>> JBMETA-224 is closed but I'm still not able to
>> build jboss-metadata-common with OpenJDK :(
>> Should I reopen it or create new one?
>>
>> Thanks,
>>
>> Rio
>>
>> -- Richard Opalka ropalka(a)redhat.com JBoss, by Red Hat Office: +420
>> 222 365 200 Mobile: +420 731 186 942
--
Richard Opalka
ropalka(a)redhat.com
JBoss, by Red Hat
Office: +420 222 365 200
Mobile: +420 731 186 942
14 years, 3 months
