-----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 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: | | 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 | descriptor into a CXF specific one. | | thanks, | dims | | Lahiru Sandakith wrote: | | 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 for deployment. | | | | Thanks | | Lahiru | | | | On Jan 25, 2008 5:13 PM, Davanum Srinivas <[EMAIL PROTECTED]> wrote: | | | | 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 | | deployment descriptors. We need to come up with a list of those and be | | able to specify them in services.xml too. Stay tuned. | | | | thanks, | | dims | | | | Lahiru Sandakith wrote: | | | 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 Deployer with | | current | | | Axis2 trunk. | | | | | | Thanks | | | Lahiru Sandakith | | | | | | On Jan 16, 2008 10:20 AM, Deepal jayasinghe <[EMAIL PROTECTED]> wrote: | | | | | |> 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 kick start the discussion. Please see Steve's | | |>> analysis [2] and the JAXWS change log [3] | | |>> | | |> We really need to have full support of JAXWS in Axis2 1.4 , most | | |> importantly it will be great of we could have a sample and a document | | |> explaining how to use Axis2 JAXWS. | | |> | | |> -Deepal | | |>> thanks, | | |>> dims | | |>> | | |>> [1] https://issues.apache.org/jira/browse/AXIS2-3448 | | |>> [2] http://1060.org/blogxter/publish/5 | | |>> [3] | | |> | | | http://jcp.org/aboutJava/communityprocess/maintenance/jsr224/JAXWS_2.1_ChangeLog.pdf | | |>> | | |> | | |> --------------------------------------------------------------------- | | |> To unsubscribe, e-mail: [EMAIL PROTECTED] | | |> For additional commands, e-mail: [EMAIL PROTECTED] | | |> | | |> | | | | | | | |> | --------------------------------------------------------------------- | To unsubscribe, e-mail: [EMAIL PROTECTED] | For additional commands, e-mail: [EMAIL PROTECTED] | |> | |> | |> - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] |> |> -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Cygwin) iD8DBQFHmrDqgNg6eWEDv1kRAv+lAKC1psUO/7+Do3wEzgW7S5sGKkeqKACgnfQr rz1r5igwyUFKrGSX9JDPzdo= =PwJR -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
