Hi Andy,
I had read somewhere in one of tck related documents years back, that
there was a need to include a jaxr library in the app server. The TCK
configuration needs to either have a uddi registry or ebxml registry for
certification.
It is similar to JDBC. We are not required to ship a DB.
Maybe Shelly can get it clarified.
Regards,
Anil
On 11/15/2011 02:33 AM, Andrig Miller wrote:
Didn't the EE TCK require the UDDI registry? Does the EE 6 TCK
no
longer require it?
If its no longer required, we should definitely not put it into AS 7.1
or EAP 6, since it always ends up in conflict with what the SOA-P guys
need. They seem to always need a newer version than what is in EAP,
so they end up overlaying the EAP one.
Andy
------------------------------------------------------------------------
*From: *"Anil Saldhana" <Anil.Saldhana(a)redhat.com>
*To: *"Thomas Diesler" <thomas.diesler(a)jboss.com>
*Cc: *"Kurt T Stam" <kurt.stam(a)jboss.com>,
"jboss-as7-dev(a)lists.jboss.org Development"
<jboss-as7-dev(a)lists.jboss.org>
*Sent: *Monday, November 14, 2011 3:55:27 PM
*Subject: *Re: [jboss-as7-dev] Initial JAXR subsystem available
Hi Thomas/Kurt,
when I checked few years back, the EE tck required the shipping
of jaxr library and there was no need for the app server to ship
the UDDI registry.
So, IMO the uddiv3 registry should be downloadable by the user and
not be in standalone AS7. Of course, EAP and SOA-P can carry them
by default.
Just my thoughts.
Regards,
Anil
On 11/03/2011 11:26 AM, Thomas Diesler wrote:
Folks,
the initial JAXR subsystem is available for pull
<
https://github.com/jbossas/jboss-as/pull/562>. There are a
number of outstanding issues tracked by this filter
<
https://issues.jboss.org/secure/IssueNavigator.jspa?mode=hide&request...;.
The full set of tests that existed in AS6 have been ported to
Arquillian and run/pass as part of the integration tests.
Next I'd be looking at the TCK setup related to JAXR and see
if I can get that to pass.
cheers
-thomas