Sent this mail to jcp-open@ and cc'ed geir
Hi All,
Apache Axis2 1.3 (moving towards 1.4) is contain an implementation of JSR
224 (JAXWS 2.1).
In order to test the implementation for full compatibility with JSR-224 the
respective
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Please drop a note to jcp-open@ and cc geir. I believe the cxf folks have the
2.1 TCK already. worth dropping another
email to [EMAIL PROTECTED] as well. the jcp page is probably outdated.
thanks,
dims
Lahiru Sandakith wrote:
| Hi Dims/Nick,
|
| So
Hi Dims/Nick,
So what will be our strategy on obtaining the TCK 2.1 version. from the jcp
page on apache (http://www.apache.org/jcp/) it says we only have the 2.0,
Shall I post a request mail to the jcp-open list?
Thanks
Lahiru
On Jan 25, 2008 7:31 PM, Davanum Srinivas <[EMAIL PROTECTED]> wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nick,
If we don't anything more then we are all set for now :) Yes, module enablement
would be a big plus.
thanks,
dims
Nicholas L Gallardo wrote:
| Dims,
|
| Right now, I can't think of anything that we would need to turn on/off that
| can't be d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lahiru,
these are open questions. Remember the sun RI implementation also has a
sun-jaxws.xml which is a sun specific deployment
descriptor. CXF also has its own. From what i recall the CXF TCK folks use a
stylesheet to convert the sun deployment
d
Dims,
Right now, I can't think of anything that we would need to turn on/off that
can't be done in annotations. So, from a TCK perspective we should be good
to go there.
Or... is your comment for things beyond the spec? i.e., module
enablement?
-Nick
Hi Dims,
Ok, So where can I find these features that will be included. I am not that
familiar with the spec, but currently looking in to it.
I am +1 on adding extra key/value pairs in services.xml , but aren't that
violates the TCK compliance. I mean having additional configurations to
the Axis2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lahiru,
Yep, both work!. We need to figure out a couple of more things. See if there are jaxws
"features" that can/need to be
turned on/off and maybe add some key/value pairs in services.xml to control
them. Some annotations may be overridden by
de
Hi Devs,
+1 for the total JAXWS support on Axis2 1.4. And also +1 for going with
JAXWS 2.1, lets merge it to the trunk.
I have done some testing with the sample available in the and as I saw it
now the AAR based model works with JAXWS MR.
Also JSR 181 annotated pojos are working with the POJO Depl
t;
> |>
> |> [image removed] Jeff Barrett/Austin/[EMAIL PROTECTED]
> |>
> |
> |> Jeff Barrett/Austin/[EMAIL PROTECTED]
> |> 01/17/2008 09:34 AM
> |>
> |> Please respond to
> |> axis-dev@ws.apache.org
> |>
> |> [image removed]
> |>
|> 01/17/2008 09:34 AM
|>
|> Please respond to
|> axis-dev@ws.apache.org
|>
|> [image removed]
|> To
|>
|> [image removed]
|> axis-dev@ws.apache.org
|>
|> [image removed]
|> cc
|>
|> [image removed]
|>
|> [image removed]
|> Subject
|>
|> [image
@ws.apache.org
>
> [image removed]
> cc
>
> [image removed]
>
> [image removed]
> Subject
>
> [image removed]
> Re: [Axis2] JAXWS version in Axis2 1.4>
>
> [image removed]
>
> [image removed]
>
>
> Hi All,
>
> I agree with Nick's sug
>
> [image removed]
> axis-dev@ws.apache.org
>
> [image removed]
> cc
>
> [image removed]
>
> [image removed]
> Subject
>
> [image removed]
> Re: [Axis2] JAXWS version in Axis2 1.4
>
> [image removed]
>
> [image removed]
>
>
> Hi All
s.apache.org
To
axis-dev@ws.apache.org
cc
Subject
Re: [Axis2] JAXWS version in Axis2 1.4
Hi Dims, Nick
It would be good to get the code that is currently in the jaxws21 branch
moved over to the trunk asap. There is also an existing JIRA to cover the
JAX-WS 2.1 development in general,
http://iss
2008 10:19 AM
>
> Please respond to
> axis-dev@ws.apache.org
>
> [image removed]
> To
>
> [image removed]
> "axis-dev@ws.apache.org"
>
> [image removed]
> cc
>
> [image removed]
>
> [image removed]
> Subjec
Hi Dims
> , Nick, Rich,
>
> - I believe the jaxws-tck svn and the associated mailing list is ready.
> - cxf folks i am told are running JAXWS 2.1 TCK
> - Sun posted JDK 1.6 update 4 with JAXWS 2.1 inside.
>
> So, what should we do for Axis2 1.4? I just saw Nick's jira float by
> [1] and wanted to
ease respond to
> axis-dev@ws.apache.org
>
> [image removed]
> To
>
> [image removed]
> "axis-dev@ws.apache.org"
>
> [image removed]
> cc
>
> [image removed]
>
> [image removed]
> Subject
>
> [image removed]
> Re: [Axi
Dims,
Thanks for starting the discussion. I wasn't aware of jcp-open. It's good
to know there's an open forum for that information.
Wrt. Axis2 1.4, my vote is that we certify based on JAX-WS 2.1 rather than
2.0. Brian has done a large amount of work in the jaxws21 branch. We can
merge that o
Some discussion on jcp-open as well.
[4] http://news.gmane.org/gmane.comp.apache.jcp%2dopen
-- dims
On Jan 15, 2008 11:17 AM, Davanum Srinivas <[EMAIL PROTECTED]> wrote:
> Glen, Sandakith, Jeff, Nick, Rich,
>
> - I believe the jaxws-tck svn and the associated mailing list is ready.
> - cxf folks
Glen, Sandakith, Jeff, Nick, Rich,
- I believe the jaxws-tck svn and the associated mailing list is ready.
- cxf folks i am told are running JAXWS 2.1 TCK
- Sun posted JDK 1.6 update 4 with JAXWS 2.1 inside.
So, what should we do for Axis2 1.4? I just saw Nick's jira float by
[1] and wanted to k
20 matches
Mail list logo
