Mailing-List: contact scout-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: scout-dev@ws.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Message-ID: <472F2E52.6000603@apache.org>
Date: Mon, 05 Nov 2007 09:53:06 -0500
From: Kurt T Stam <kstam@apache.org>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: scout-dev@ws.apache.org
Subject: Re: Scout problems
References: <C354EA62.1BDB%javier.botana@uni-koeln.de>
In-Reply-To: <C354EA62.1BDB%javier.botana@uni-koeln.de>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

The version of both scout and jUDDI in JBossAS is pretty old. I think
the issues you mentioned are
related to scout. If you can please upgrade scout to rc1, or the latest
on the trunk. If you sill have issues there
please jira them. We are close to doing another release, so we may try
to fix any remaining issues.

Thx,

--Kurt

Javier Botana wrote:
> Dear developers,
>
>
> I am working at the University of Cologne on an EU-funded project called
> PLANETS (see http://www.planets-project.eu). I am using JAXR/Scout/jUDDI and
> JBoss to build an administration application for the JBoss/jUDDI based
> Service Registry (JBoss version is 4.0.2).
>
> I am experiencing some mysterious problems and would like to know whether
> there is a problem with the Scout implementation or it is a configuration
> mistake. There are various problems:
>
> 1. When querying for organizations (JAXR), the email collection of the
> primary contact has length = 0 although there is an email address stored in
> the jUDDI database.
>
> 2. When I use bqm.getRegistryObjects(LifeCycleManager.ORGANIZATION) to query
> for the organization(s) owned by a specific publisher, it returns all
> organizations regardless if there are owned by the caller
>
> 3. When I query for services by name, the services are found but have no
> description and no bindings, although this data is stored in the jUDDI
> database.
>
>
> I would very much appreciate some help or hints on these topics (especially
> 2.). If these are bugs within the Scout implementation then I will have to
> look in another direction.
>
>
> Cheers,
>
> Javier
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: scout-dev-help@ws.apache.org
>   


---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org