January 2007 - jbossws-dev - Jboss List Archives

[Fwd: [members] Public Review of SAML-related specifications]

by Heiko Braun

FYI -- Heiko Braun JBoss, a division of Red Hat T: +49 89 52350383 M: +49 178 1496854

18 years

1
0
0 / 0

[Design of JBoss Web Services] - Support JAXWS on EJB2.1

by thomas.diesler＠jboss.com

Folks, should we continue to support JAXWS, JSR181 annotations on EJB-2.1? Please keep in mind that we can now use the trunk code base in jboss-4.2, jboss-4.0 Comments? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3998881#3998881 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3998881

18 years

1
0
0 / 0

Please unlock jbossws-1.0

by Thomas Diesler

Hi Jas, please unlock jbossws-1.0 http://www.jboss.org/index.html?module=bb&op=viewtopic&t=98635 cheers -thomas -- xxxxxxxxxxxxxxxxxxxxxxxxxxxx Thomas Diesler Web Service Lead JBoss, a division of Red Hat xxxxxxxxxxxxxxxxxxxxxxxxxxxx

18 years

1
0
0 / 0

[Design of JBoss Web Services] - Using jbossws/trunk for jboss-5.0, jboss-4.2, jboss-4.0.5

by thomas.diesler＠jboss.com

Folks, last week I succeded to implement porting layers for jboss50, jboss42, jboss40 on a common jbossws code base. This means that from now on we can work on jbossws/trunk again, which should reduce code maintenance significantly (branch/jbossws-1.0. is dead) jbossws-1.2.0.CR2 was release over the weekend and I updated http://wiki.jboss.org/wiki/Wiki.jsp?page=JBWSFAQBuildAndInstall to describe the new deployment procedure. In JIRA I moved all 1.0.5 and 2.0.0.CR3 issues to 1.2.0, which is due 1-Feb-2007. I will send a more detailed mail related to the 1.2.0 release later today. cheers View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3998876#3998876 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3998876

18 years

1
0
0 / 0

RE: Branch Code Freeze

by Jason T. Greene

Just in case someone misses this email, I have locked everyone out of this branch. Contact me if something comes up. > -----Original Message----- > From: Jason T. Greene > Sent: Tuesday, December 12, 2006 4:25 PM > To: jbossws-dev(a)lists.jboss.org > Cc: Darran Lofthouse; Magesh Kumar Bojan; David Boeren > Subject: Branch Code Freeze > > This week I am merging trunk to the jbossws-1.0 branch, please avoid > making changes to jbossws-1.0 if at all possible. If you need to make > changes, please apply them to trunk. > > Otherwise, please contact me about your change first, so I can keep from > overwriting it. > > Thanks, > -Jason > > xxxxxxxxxxxxxxxxxxxxxxxxxxxx > Jason T. Greene > Senior Software Engineer > JBoss, a division of Red Hat > xxxxxxxxxxxxxxxxxxxxxxxxxxxx

18 years

3
3
0 / 0

Re: FW: Reconvene with AmberPoint

by Thomas Diesler

18 years

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBWS-1260 - Sequence containing 2 elements

by darran.lofthouse＠jboss.com

Related to the partial unwrapping wscompile was doing what should we do if any of the message parts reference an element that is a simple type? e.g. <s:element name="string" nillable="true" type="s:string" /> At the moment if the element references anything other than a complex type we reject the WSDL. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3998218#3998218 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3998218

18 years

1
0
0 / 0

[Design of JBoss Web Services] - Re: New jboss version info attributes

by dimitris＠jboss.org

Can you switch (4.2/HEAD) to use a new attribute VersionNumber I added on Server mbean: | ObjectName oname = ObjectNameFactory.create("jboss.system:type=Server"); | jbossVersion = (String)getServer().getAttribute(oname, "VersionNumber"); | I can then revert the ServerConfig changes to avoid attribute bloat. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3997893#3997893 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3997893

18 years

1
0
0 / 0

[Design of JBoss Web Services] - Re: New jboss version info attributes

by thomas.diesler＠jboss.com

I use | ObjectName oname = ObjectNameFactory.create("jboss.system:type=ServerConfig"); | jbossVersion = (String)getServer().getAttribute(oname, "SpecificationVersion"); | to enable/disable parts of our testsuite dependeing on the target environment. I only added the others for completeness. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3997611#3997611 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3997611

18 years

1
0
0 / 0

[Design of JBoss Web Services] - New jboss version info attributes

by dimitris＠jboss.org

Just saw 4 new attributed added to jboss.system:type=ServerConfig mbean (I'm posting here 'cause Thomas added them) SpecificationTitle (JBoss) ImplementationTitle (JBoss [Trinity]) and ImplementationVersion (4.2.0.CR1 (build: SVNTag=JBoss_4_2_0_CR1 date=200701021921)) are either obvious or exist already in a jboss.system:type=Server mbean: Version (4.2.0CR1(build: CVSTag=JBoss_4_2_0_CR1 date=200701021921)) VersionName (Trinity) The only useful addition seems to be the SpecificationVersion (4.2.0.CR1) which again looks more appropriate to appear in jboss.system:type=Server mbean as, e.g., VersionNumber, VersionId, or similar. Are those new attributes used somewhere? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3997343#3997343 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3997343

18 years

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-dev January 2007