Re: [jboss-dev] 6.0.0.CR1 Release Update #2
by Shelly McGowan
The final commits have been made to the CR1 branch to fix the regressions detected.
One more round of testing to be done before the rescheduled hand off to QA tomorrow, November 16.
The new release target date is Friday, November 19.
You can follow the release status here:
http://community.jboss.org/wiki/AS600CR1StatusExecutiveSummary
Shelly McGowan
JBoss, by Red Hat
----- Original Message -----
From: "Shelly McGowan" <smcgowan(a)redhat.com>
To: jboss-development(a)lists.jboss.org
Sent: Thursday, November 11, 2010 4:32:59 PM GMT -05:00 US/Canada Eastern
Subject: [jboss-dev] 6.0.0.CR1 Release Update
The tag is still pending on resolution to the regressions noted below. The
issues are actively being addressed and tested.
http://hudson.jboss.org/hudson/view/JBoss%20AS/job/JBoss-AS-6.0.x-testSui...
Shelly McGowan
JBoss, by Red Hat
----- Original Message -----
From: "Shelly McGowan" <smcgowan(a)redhat.com>
To: "JBoss.org development list" <jboss-development(a)lists.jboss.org>
Sent: Thursday, November 11, 2010 12:31:36 AM GMT -05:00 US/Canada Eastern
Subject: Re: [jboss-dev] Branching jbossas/trunk for 6.0.0.CR1 Release
The 6.0.0.CR1 branch has been created:
http://anonsvn.jboss.org/repos/jbossas/branches/6.0.0.20101110-CR1/
Excellent push and hard work to meet this important milestone.
There were a couple of test suite regressions that did arise as a result of the commits.
These regressions are being looked at and will be fixed in the Branch prior to the Tag and hand off to QA.
Shelly McGowan
JBoss, by Red Hat
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
14 years, 5 months
6.0.0.CR1 Release Update
by Shelly McGowan
The tag is still pending on resolution to the regressions noted below. The
issues are actively being addressed and tested.
http://hudson.jboss.org/hudson/view/JBoss%20AS/job/JBoss-AS-6.0.x-testSui...
Shelly McGowan
JBoss, by Red Hat
----- Original Message -----
From: "Shelly McGowan" <smcgowan(a)redhat.com>
To: "JBoss.org development list" <jboss-development(a)lists.jboss.org>
Sent: Thursday, November 11, 2010 12:31:36 AM GMT -05:00 US/Canada Eastern
Subject: Re: [jboss-dev] Branching jbossas/trunk for 6.0.0.CR1 Release
The 6.0.0.CR1 branch has been created:
http://anonsvn.jboss.org/repos/jbossas/branches/6.0.0.20101110-CR1/
Excellent push and hard work to meet this important milestone.
There were a couple of test suite regressions that did arise as a result of the commits.
These regressions are being looked at and will be fixed in the Branch prior to the Tag and hand off to QA.
Shelly McGowan
JBoss, by Red Hat
14 years, 5 months
Re: [jboss-dev] Branching jbossas/trunk for 6.0.0.CR1 Release
by Neubauer. Rico
Hi,
would like to point you to https://jira.jboss.org/browse/JBAS-8580 and its sub-task JBAS-8623, which I would consider at least major for a production release.
Best Regards,
Rico
Von: jboss-development-request(a)lists.jboss.org
Gesendet: Mi 10.11.2010 18:00
An: jboss-development(a)lists.jboss.org
Betreff: jboss-development Digest, Vol 53, Issue 5
Send jboss-development mailing list submissions to
jboss-development(a)lists.jboss.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.jboss.org/mailman/listinfo/jboss-development
or, via email, send a message with subject or body 'help' to
jboss-development-request(a)lists.jboss.org
You can reach the person managing the list at
jboss-development-owner(a)lists.jboss.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of jboss-development digest..."
Today's Topics:
1. Branching jbossas/trunk for 6.0.0.CR1 Release (Shelly McGowan)
----------------------------------------------------------------------
Message: 1
Date: Wed, 10 Nov 2010 11:47:56 -0500 (EST)
From: Shelly McGowan <smcgowan(a)redhat.com>
Subject: [jboss-dev] Branching jbossas/trunk for 6.0.0.CR1 Release
To: "JBoss.org development list" <jboss-development(a)lists.jboss.org>
Message-ID:
<1189040185.614381289407676829.JavaMail.root(a)zmail03.collab.prod.int.phx2.redhat.com>
Content-Type: text/plain; charset=utf-8
As planned, jbossas/trunk will be branched later tonight:
http://community.jboss.org/wiki/AS600CR1StatusExecutiveSummary
A few outstanding JIRAs expected for the release remain. Let me know if these
issues are BLOCKERS for the release or will be deferred.
EJB 3 Update:
https://jira.jboss.org/browse/JBAS-8370
-- Async
Integration of jboss-ejb3-bean-instantiator
https://jira.jboss.org/browse/JBAS-8313
RESTEasy Upgrade
https://jira.jboss.org/browse/JBAS-8555
Once the branch is created, the integrations related to jboss-injection will be begin (tomorrow) in trunk. This POC has already been
performed in its' own branch but it is possible there will be some initial destabilization of trunk.
Shelly McGowan
JBoss, by Red Hat
------------------------------
_________________________________________________________________________
SEEBURGER AG Vorstand/Seeburger Executive Board:
Sitz der Gesellschaft/ Bernd Seeburger, Axel Haas, Michael Kleeberg
Registered Office:
Edisonstrasse 1 Vorsitzender des Aufsichtsrats/Chairperson of
D-75015 Bretten the Seeburger Supervisory Board:
Tel.: 07252 / 96-0 Dr. Franz Scherer
Fax: 07252 / 96-2222
Internet: http://www.seeburger.de Registergericht/Commercial Register:
e-mail: info(a)seeburger.de HRB 240708 Mannheim
_________________________________________________________________________
Dieses E-Mail ist nur für den Empfänger bestimmt, an den es gerichtet
ist und kann vertrauliches bzw. unter das Berufsgeheimnis fallendes
Material enthalten. Jegliche darin enthaltene Ansicht oder Meinungs-
äußerung ist die des Autors und stellt nicht notwendigerweise die
Ansicht oder Meinung der SEEBURGER AG dar.
Sind Sie nicht der Empfänger, so haben Sie diese E-Mail irrtümlich
erhalten und jegliche Verwendung, Veröffentlichung, Weiterleitung,
Abschrift oder jeglicher Druck dieser E-Mail ist strengstens untersagt.
Weder die SEEBURGER AG noch der Absender (Rico Neubauer)
übernehmen die Haftung für Viren; es obliegt Ihrer Verantwortung,
die E-Mail und deren Anhänge (0) auf Viren zu prüfen.
The present email addresses only the addressee which it targets and
may contain confidential material that may be protected by the
professional secret. The opinions reflected herein are not necessarily
the one of the SEEBURGER AG.
If you are not the addressee, you have accidentally got this email and
are not enabled to use, publish, forward, copy or print it in any way.
Neither the SEEBURGER AG, nor the sender (Rico Neubauer) are
liable for viruses, being your own responsibility to check this email
and its attachments (0) for this purpose.
_________________________________________________________________________
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
End of jboss-development Digest, Vol 53, Issue 5
************************************************
14 years, 5 months
AS6 EJB+Resteasy regression with unchanged code
by Bill Burke
I'm getting deployment errors for Resteasy + EJB integration with
existing code (that I haven't changed in months). For a simple EJB:
package org.jboss.resteasy.test;
@Path("/scan")
@Stateless
public class MyResourceBean implements MyResource
{...}
I"m getting a JNDI lookup error in Resteasy deployment that it can't find:
"MyResourceBean/local"
Some questions:
1) Has the local interface jndi binding changed?
2) Maybe servlet filters can deployed before EJBs?
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
14 years, 5 months
Unable to resolve an AS trunk dependency
by Galder Zamarreño
Hey,
I'm trying to build AS trunk using the given build.sh but I get:
[ERROR] Failed to execute goal on project jboss-as-depchain: Missing:
----------
1) org.jboss.system:system-jmx:jar:5.1.0.GA
...
Path to dependency:
1) org.jboss.jbossas:jboss-as-depchain:pom:6.0.0-SNAPSHOT
2) org.jboss.ejb3:jboss-ejb3-metrics-deployer:jar:1.1.0
3) org.jboss.system:system-jmx:jar:5.1.0.GA
----------
1 required artifact is missing.
for artifact:
org.jboss.jbossas:jboss-as-depchain:pom:6.0.0-SNAPSHOT
from the specified remote repositories:
apache.snapshots (http://repository.apache.org/snapshots, releases=false, snapshots=true),
jboss-maven2-brew (http://repository.jboss.org/maven2-brew/, releases=true, snapshots=false),
jboss-public-repository-group (http://repository.jboss.org/nexus/content/groups/public/, releases=true, snapshots=true),
central (http://repo1.maven.org/maven2, releases=true, snapshots=false)
Cheers,
--
Galder Zamarreño
Sr. Software Engineer
Infinispan, JBoss Cache
14 years, 6 months
Accessing java: namespace from outside the server JVM (keeping in mind EJB3.1 spec)
by Jaikiran Pai
Traditionally JBoss AS (backed by the JNP naming server) hasn't allowed
access to objects bound in java: JNDI namespace outside of the server
JVM. For example, if someone does a java:DefaultDS lookup from a remote
JVM, it's bound to fail with a NameNotFoundException. However, with the
introduction of "Global JNDI naming scheme" in EJB3.1 spec, which
mandates binding of EJBs under the java:global/ namespace, accessing the
beans under java:global/ namespace from outside server JVM becomes
necessary.
From what I understand, the java: namespace handling (i.e. not allowing
it to be accessed outside the JVM) is a JBoss specific implementation
detail and the spec doesn't mandate that (haven't found a documentation
which says otherwise).
Is there a way, we can make available the resources under java:
namespace to be available to remote clients, in AS6? I understand that
this might break existing functionality and applications, so probably we
could pass a property through the InitialContext constructor (or
jndi.properties) during a EJB lookup (or any other lookup for that
matter) which would explicitly allow access to this namespace remotely.
Is this something that could be introduced in the naming server
implementation? Or any other better way to handle this?
P.S: Looking at the naming server code, I _think_ I might have a very
hackish way of providing a remotely accessible java:global/ namespace,
from within the EJB3 jndi binding code. I haven't tried it though and
would preferably avoid doing it in the EJB3 code.
-Jaikiran
14 years, 6 months
