jbossws-2.0.3 release owner
by Thomas Diesler
Hi Heiko/Team,
I would like to rotate the release responsibility among the team members
again. As we talked about, you would be the one who owns the 2.0.3.GA
release.
I've started a to document what needs to be done here:
http://jbws.dyndns.org/mediawiki/index.php?title=Release_Procedure
Please complete this documentation if necessary as you go along. Your
first responsibility would be to decide upon the set of jira issues that
will get fixed for 2.0.3.GA by jira freeze (14-Dec-2007). You would talk
to everybody who owns jira issues for that release and get their OK that
their issues will actually get fixed in time for code freeze
(18-Jan-2008). After jira freeze there should be no change in the number
of issues that go into the release.
cheers & good luck
-thomas
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
17 years, 1 month
Re: Server Configuration Guide - Chapter9 - Web Services
by Thomas Diesler
On Fri, 2007-11-30 at 10:22 +1000, Samson Kittoli wrote:
> Thanks Thomas,
> I will do the necessary updates.
> One more request, I would like to request your teams feedback on the docs
> review and update process we have used.
> Do you feel this is an effective method or are there any improvements you
> would wish us to make.
Sure. Where are the docs?
> I will highly appreciate your team's feedback on this and wish to make
> necessary improvements if any.
> Regards,
>
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
17 years, 1 month
[Fwd: Big problem with WebXMLRewriterImpl.java rename]
by Thomas Diesler
Heiko,
could you please follow up on this?
cheers
-thomas
-------- Forwarded Message --------
From: Leonardo Penczek <lpenczek(a)gmail.com>
To: thomas.diesler(a)jboss.com
Subject: Big problem with WebXMLRewriterImpl.java rename
Date: Thu, 29 Nov 2007 12:11:25 -0200
In WindowsNT systems, your modification in these lines doesn't work:
FileInputStream stream = new FileInputStream(webXML);
String modifyProperty =
(String)dep.getProperty("org.jboss.ws.webapp.modify");
// JBWS 1762
if ((modifyProperty == null) || (!modifyProperty.equals("false")))
{
String suffix =
(String)dep.getProperty("org.jboss.ws.webapp.descriptor.suffix");
if (suffix == null)
suffix = ".org";
File orgWebXML = new File(webXML.getCanonicalPath() + suffix);
// Rename the web.xml
if (webXML.renameTo(orgWebXML) == false)
throw new WebServiceException("Cannot rename web.xml: "
+ orgWebXML);
stream = new FileInputStream(orgWebXML);
}
As you open a FileInputStream over webXML, it can't be renamed to
orgWebXML because the stream is open in this point, and Windows blocks
te rename operation.
It can be solved as below:
// WindowsNT correction
FileInputStream stream = null;
String modifyProperty =
(String)dep.getProperty("org.jboss.ws.webapp.modify");
// JBWS 1762
if ((modifyProperty == null) || (!modifyProperty.equals("false")))
{
String suffix =
(String)dep.getProperty("org.jboss.ws.webapp.descriptor.suffix");
if (suffix == null)
suffix = ".org";
File orgWebXML = new File(webXML.getCanonicalPath() + suffix);
// Rename the web.xml
if (webXML.renameTo(orgWebXML) == false)
throw new WebServiceException("Cannot rename web.xml: "
+ orgWebXML);
stream = new FileInputStream(orgWebXML);
} else {
stream = new FileInputStream(webXML);
}
Cheers,
Leonardo Penczek
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
17 years, 1 month
Re: [Fwd: Re: Compatibility Between CP Releases]
by Thomas Diesler
On Fri, 2007-11-23 at 15:55 +0200, Dimitris Andreadis wrote:
> The change in serialVersionUIDs is often unintentional and happens when no explicit
> serialVersionUID is defined and a change is made in the class that recalculates a different
> implicit Id. As Thomas pointed out, we fixed those ids in SP2.
>
> We probably need to run probably something like JBoss-AS-4.2.x-CompatibilityMatrix for EAP.
>
> Rajesh could help you setup it up.
>
> http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-4.2.x-Comp...
>
> At the same time the compatibility matrix testsuite doesn't include webservices tests,
> AFAIK, so this is a possible TODO item.
>
> Thomas, is there some kind of cross-version compatibility testing for WS happening already?
No, AFAIK there is not. We do however have public interop endpoints
setup.
http://jbws.dyndns.org/mediawiki/index.php?title=Interop_Endpoints
I also don't really understand the use case where a serialVersionUID
conflict would show up. The only use case I can think of is an appclient
deployment to jboss-4.x and a client vm doing a JNDI lookup of the
preconfigured stub using jboss-4.y libraries.
cheers
-thomas
>
> Fernando Nasser wrote:
> > Dimitirs,
> >
> > What was the idea behind the serialVersionUID change?
> >
> > How do we handle applications using EAP 4.2 client taljing to EAP 4.3
> > servers (as per compatibility rules)?
> >
> > Any workarounds?
> >
> > Cheers,
> > Fernando
> >
> > Thomas Diesler wrote:
> >> This is possible. We changed the serialVersionUID as requested by
> >> Dimitris
> >>
> >> cheers
> >> -thomas
> >>
> >> [tdiesler@tddell jbossws-native-2.0.1.SP2]$ svn log -v -r4837
> >> ------------------------------------------------------------------------
> >> r4837 | thomas.diesler(a)jboss.com | 2007-10-21 08:40:22 +0200 (Sun, 21
> >> Oct 2007) | 1 line
> >> Changed paths:
> >>
> >> M
> >> /stack/native/tags/jbossws-native-2.0.1.SP2/src/main/java/javax/xml/rpc/JAXRPCException.java
> >>
> >>
> >> M
> >> /stack/native/tags/jbossws-native-2.0.1.SP2/src/main/java/javax/xml/rpc/ServiceException.java
> >>
> >>
> >> M
> >> /stack/native/tags/jbossws-native-2.0.1.SP2/src/main/java/javax/xml/rpc/soap/SOAPFaultException.java
> >>
> >>
> >> M
> >> /stack/native/tags/jbossws-native-2.0.1.SP2/src/main/java/javax/xml/soap/SOAPException.java
> >>
> >>
> >> Use serialVersionUID required by the tests
> >> ------------------------------------------------------------------------
> >>
> >>
> >> On Fri, 2007-11-23 at 11:57 +0100, Heiko Braun wrote:
> >>> something we may need to verify before the 2.0.2 release.
> >>> unfortunately i am stuck in meetings today and wasn't able to
> >>> reproduce the problem yet.
> >>>
> >>> /heiko
> >>> email message attachment, "Forwarded message - Re: Compatibility
> >>> Between CP Releases"
> >>>> -------- Forwarded Message --------
> >>>> From: Fernando Nasser <fnasser(a)redhat.com>
> >>>> To: Heiko Braun <hbraun(a)redhat.com>
> >>>> Cc: Fernando Nasser <fnasser(a)redhat.com>, Deepak Bhole
> >>>> <dbhole(a)redhat.com>
> >>>> Subject: Re: Compatibility Between CP Releases
> >>>> Date: Thu, 22 Nov 2007 09:23:44 -0500
> >>>>
> >>>> Heiko Braun wrote:
> >>>>> so, no action item for me, right?
> >>>>>
> >>>> We need you to confirm or deny the following statement:
> >>>>
> >>>> "An application using the WS 1.2.1 client library cannot communicate
> >>>> with a server using the new WS 2.0.1 due to serialVersionUID mismatch"
> >>>>
> >>>> And if you say yes, is there anything we can/should do to prevent that?
> >>>>
> >>>> Cheers,
> >>>> Fernando
> >>>>
> >>>>
> >>>>> On Thu, 2007-11-22 at 08:37 -0500, Fernando Nasser wrote:
> >>>>>> It seems to fall into this same class of problem.
> >>>>>>
> >>>>>>
> >>>>>> Carlo de Wolf wrote:
> >>>>>>> Fernando,
> >>>>>>>
> >>>>>>> On a related note: do you want this one in?
> >>>>>>> http://jira.jboss.com/jira/browse/EJBTHREE-1118
> >>>>>>>
> >>>>>>> Carlo
> >>>>>>>
> >>>>>>> On Wed, 2007-11-21 at 19:01 -0500, Fernando Nasser wrote:
> >>>>>>>> It seems that applications with older client libraries (like EAP
> >>>>>>>> 4.2) using web services may have problems communicating with new
> >>>>>>>> (EAP 4.3) servers because serialVersionUIDs changed between WS
> >>>>>>>> 1.2.1 and WS 2.0.1.
> >>>>>>>>
> >>>>>>>> Heiko, can you confirm or deny that?
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> Ryan Campbell wrote:
> >>>>>>>>> Darran Lofthouse wrote:
> >>>>>>>>>> Do we have plans to actually perform the compatibility tests
> >>>>>>>>>> between the
> >>>>>>>>>> different CP versions to ensure none of the changes will prevent
> >>>>>>>>>> different versions communicating with each other?
> >>>>>>>>>>
> >>>>>>>>> What kinds of compatibility?
> >>>>>>>>>
> >>>>>>>>> What we have:
> >>>>>>>>> Serialization Static Analysis - Do the serialUID's match
> >>>>>>>>> between versions? All classes are checked.
> >>>>>>>>> Interop - do legacy client libraries work with the current
> >>>>>>>>> server implementation? Coverage here is across several
> >>>>>>>>> services. See
> >>>>>>>>> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.2-compatibility-ma...
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> What we don't have:
> >>>>>>>>> API compatibility - we don't currently have any tests for
> >>>>>>>>> this. There are reporting tools for comparing API's which we
> >>>>>>>>> should consider for CP02, but we won't have time for CP01 since
> >>>>>>>>> testing starts in about a week.
> >>>>>>>>>
> >>>>>>>>> Ryan
> >>>>>>>>>
> >>>>>>>>>
> >>>>>
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
17 years, 1 month
Re: 'port-component' not found as a child of 'ejb'
by Thomas Diesler
merci
On Mon, 2007-11-19 at 16:10 +0100, Alexey Loubyansky wrote:
> Yes, I was just creating a testcase for this in the metadata project.
>
> Thomas Diesler wrote:
> > Hi Alex,
> >
> > could you please have a look at
> >
> > http://jira.jboss.org/jira/browse/JBAS-4989
> >
> > According to the jboss_5_0.xsd schema, <port-component> is allowed as
> > child of the generic <ejb> element.
> >
> > cheers
> > -thoams
> >
> >
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
17 years, 1 month
