You are viewing a plain text version of this content. The canonical link for it is here.
Posted to scout-dev@ws.apache.org by Kurt T Stam <ks...@apache.org> on 2007/07/26 20:28:35 UTC
scout-v1.0rc1 is out
Hi guys,
Scout-1.0rc1 is out :). The website should update itself within the hour
to reflect the new release.
But if you can't wait you can download the jars here:
http://people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/ws/scout/
RELEASE NOTES
Release Notes - Scout - Version 1.0rc1
** Bug
* [SCOUT-23] - Classification are not saved.
* [SCOUT-25] - FindBinding does not work + patch
* [SCOUT-26] - Removing a service does not remove the service + patch
* [SCOUT-28] - XmlBeans conversion compiles but is non-functional
* [SCOUT-29] - AuthTokenImpl.getAuthInfo() doesn't seem to work correctly
* [SCOUT-30] - Classifications are ignored when preforming finds.
* [SCOUT-31] - Fix scout maven 1 build issue so that the dependency jars can be downloaded automatically
* [SCOUT-32] - Fix NPE at getConcept
* [SCOUT-33] - Should throw exception when level 1 feature is accessed in RegistryEntryImpl.java
* [SCOUT-34] - DiscoveryURLs aren't constructed correctly when there is more than 1 discoveryURLs for a businessEntity
* [SCOUT-35] - Should use hashset for the collection in BulkResponseImpl to not allow duplicate
* [SCOUT-36] - minor update to get scout maven 2 build pass the error in download juddi snapshot
* [SCOUT-40] - InternationalString is not handled correctly
* [SCOUT-41] - Results not returned in the given order
* [SCOUT-44] - port fixes for scout 8 to trunk
* [SCOUT-45] - port scout 19 to trunk
* [SCOUT-46] - port scout 10 to trunk
** Improvement
* [SCOUT-9] - Separation of Apache Scout and jUDDI
** New Feature
* [SCOUT-18] - Embedded mode execution
** Task
* [SCOUT-27] - Update Tests with embedded juddi setup
* [SCOUT-37] - Cleanup code to get rid of warnings
* [SCOUT-38] - Produce website from the maven2 build
* [SCOUT-39] - Integrate all sample code in unittests
* [SCOUT-42] - apply fixes on 0.7 branches to the trunk
Cheers,
--Kurt
---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org
Re: scout-v1.0rc1 is out
Posted by Lin Sun <li...@gmail.com>.
Hi Kurt, this is great! Thanks for all your effort in putting it out.
We'll try it in geronimo and report any prob here (hopefully none). :)
Lin
Kurt T Stam wrote:
> Hi guys,
>
> Scout-1.0rc1 is out :). The website should update itself within the hour
> to reflect the new release.
> But if you can't wait you can download the jars here:
>
> http://people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/ws/scout/
>
> RELEASE NOTES
>
> Release Notes - Scout - Version 1.0rc1
>
> ** Bug
> * [SCOUT-23] - Classification are not saved.
> * [SCOUT-25] - FindBinding does not work + patch
> * [SCOUT-26] - Removing a service does not remove the service + patch
> * [SCOUT-28] - XmlBeans conversion compiles but is non-functional
> * [SCOUT-29] - AuthTokenImpl.getAuthInfo() doesn't seem to work correctly
> * [SCOUT-30] - Classifications are ignored when preforming finds.
> * [SCOUT-31] - Fix scout maven 1 build issue so that the dependency jars can be downloaded automatically
> * [SCOUT-32] - Fix NPE at getConcept
> * [SCOUT-33] - Should throw exception when level 1 feature is accessed in RegistryEntryImpl.java
> * [SCOUT-34] - DiscoveryURLs aren't constructed correctly when there is more than 1 discoveryURLs for a businessEntity
> * [SCOUT-35] - Should use hashset for the collection in BulkResponseImpl to not allow duplicate
> * [SCOUT-36] - minor update to get scout maven 2 build pass the error in download juddi snapshot
> * [SCOUT-40] - InternationalString is not handled correctly
> * [SCOUT-41] - Results not returned in the given order
> * [SCOUT-44] - port fixes for scout 8 to trunk
> * [SCOUT-45] - port scout 19 to trunk
> * [SCOUT-46] - port scout 10 to trunk
>
> ** Improvement
> * [SCOUT-9] - Separation of Apache Scout and jUDDI
>
> ** New Feature
> * [SCOUT-18] - Embedded mode execution
>
> ** Task
> * [SCOUT-27] - Update Tests with embedded juddi setup
> * [SCOUT-37] - Cleanup code to get rid of warnings
> * [SCOUT-38] - Produce website from the maven2 build
> * [SCOUT-39] - Integrate all sample code in unittests
> * [SCOUT-42] - apply fixes on 0.7 branches to the trunk
>
> Cheers,
>
> --Kurt
>
>
> ---------------------------------------------------------------------
> 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
Re: Scout problems
Posted by Kurt T Stam <ks...@apache.org>.
Thanks Javier,
Yes please jira them: http://ws.apache.org/scout/issue-tracking.html
--Kurt
Javier Botana wrote:
> Hi again,
>
> I have now built a new jUDDI.war with maven and not with Ant like
> previously. The build process worked out perfectly!
>
>
> Now, when running the same sample as before (deployed in Tomcat 5.5.20),
> there are no exceptions whatsoever.. Sorry for the inconvenience!
>
> Still, I have the same issues as I posted in my first mail (repeated in the
> following for your convenience):
>
>
>
>>>>> 1. When querying for organizations (JAXR), the email collection
>>>>>
>
> and the phone number and the postal address collections as well!
>
>
>
>>>>> 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.
>>>>>
>
>
> Now, how can I JIRA them?
>
>
> Kind regards,
>
> Javier
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: scout-dev-help@ws.apache.org
>
Re: Scout problems
Posted by Javier Botana <ja...@uni-koeln.de>.
Hi again,
I have now built a new jUDDI.war with maven and not with Ant like
previously. The build process worked out perfectly!
Now, when running the same sample as before (deployed in Tomcat 5.5.20),
there are no exceptions whatsoever.. Sorry for the inconvenience!
Still, I have the same issues as I posted in my first mail (repeated in the
following for your convenience):
>>>> 1. When querying for organizations (JAXR), the email collection
and the phone number and the postal address collections as well!
>>>> 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.
Now, how can I JIRA them?
Kind regards,
Javier
---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org
Re: Scout problems
Posted by Kurt T Stam <ks...@apache.org>.
Hmm. I don't have time right now to run your files, but it seems awfully
close to what we do in
the JAXR010OrganizationTest? Let me know if that helps, I may have time
tomorrow to look at it some more.
--Kurt
Javier Botana wrote:
> Hi Kurt,
>
> Thanks for your quick answer.
>
> I have already tried this. I use scout-1.0rc1.jar and jaxr-api-1.0rc1.jar
> from the Scout web site. When running the attached class JAXRFindBusiness in
> the console (assuming I have run SaveJAXROrganization twice before whith the
> old configuration), I get the following output:
>
> Organization(s) found: 2
> Organization key: 16133CE0-8BA0-11DC-BCE0-98ACD5633B51
> Organization name: null
> Organization description: null
> Contact name: Steve Viens
> Phone Numbers size: 0
> Email Addresses size: 0
> Postal Addresses Size: 0
> Services found: 1
> Service name: null
> Service description: null
> ---
> Organization key: FF31FFC0-8B9F-11DC-BFC0-C1B679CFD8D9
> Organization name: null
> Organization description: null
> Contact name: Steve Viens
> Phone Numbers size: 0
> Email Addresses size: 0
> Postal Addresses Size: 0
> Services found: 1
> Service name: null
> Service description: null
>
>
> The output is the same if I use a scout.jar build from the current trunk.
>
>
> Now I have build a new juddi.war from the current trunk (copied missing
> resources manually, see mail "Problems with juddi.war built from trunk" on
> jUDDI list), deployed to Tomcat 5.5.20, and created a new MySQL database.
> When running JAXRFindBusiness with the latest Scout snapshot and
> jaxr-api-1.0rc1.jar from the Scout web site, I get the
>
>
> AxisFault
> faultCode: Client
> faultSubcode:
> faultString: E_unsupported
> (10050) The implementor does not support a feature or API. find_business:
> findQualifier=null
> faultActor:
> faultNode:
> faultDetail:
>
> {urn:uddi-org:api_v2}dispositionReport:<result errno="10050"><errInfo
> errCode="E_unsupported">E_unsupported (10050) The implementor does not
> support a feature or API. find_business:
> findQualifier=null</errInfo></result>
>
> E_unsupported (10050) The implementor
> does not support a feature or API. find_business: findQualifier=null
> at
> org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:2
> 22)
> at
> org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:12
> 9)
> at
> org.apache.axis.encoding.DeserializationContext.endElement(DeserializationCo
> ntext.java:1087)
> at
> com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(Abst
> ractSAXParser.java:633)
> at
> com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanEndElem
> ent(XMLNSDocumentScannerImpl.java:719)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$Fragm
> entContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1685)
>
> at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanD
> ocument(XMLDocumentFragmentScannerImpl.java:368)
> at
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Con
> figuration.java:834)
> at
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Con
> figuration.java:764)
> at
> com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:14
> 8)
> at
> com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractS
> AXParser.java:1242)
> at
> javax.xml.parsers.SAXParser.parse(SAXParser.java:375)
> at
> org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext
> .java:227)
> at
> org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
> at
> org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
> at
> org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChe
> cker.java:62)
> at
> org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
> at
> org.apache.axis.client.Call.invokeEngine(Call.java:2784)
> at
> org.apache.axis.client.Call.invoke(Call.java:2767)
> at
> org.apache.axis.client.Call.invoke(Call.java:1792)
> at
> org.apache.ws.scout.transport.AxisTransport.send(AxisTransport.java:66)
>
> at org.apache.ws.scout.registry.RegistryImpl.execute(RegistryImpl.java:271)
>
> at
> org.apache.ws.scout.registry.RegistryImpl.findBusiness(RegistryImpl.java:666
> )
> at
> org.apache.ws.scout.registry.BusinessQueryManagerImpl.findOrganizations(Busi
> nessQueryManagerImpl.java:126)
> at
> JAXRFindBusiness.main(JAXRFindBusiness.java:69)
> SOAP message:
> <soapenv:Fault
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><faultcode>Client<
> /faultcode><faultstring>E_unsupported (10050) The implementor does not
> support a feature or API. find_business:
> findQualifier=null</faultstring><faultactor/><detail
> xmlns:axis2ns1="urn:uddi-org:api_v2"><axis2ns1:dispositionReport
> generic="2.0" operator="jUDDI.org"><result errno="10050"><errInfo
> errCode="E_unsupported">E_unsupported (10050) The implementor does not
> support a feature or API. find_business:
> findQualifier=null</errInfo></result></axis2ns1:dispositionReport></detail><
> /soapenv:Fault>
> javax.xml.registry.JAXRException:
> at
> org.apache.ws.scout.registry.BusinessQueryManagerImpl.findOrganizations(Busi
> nessQueryManagerImpl.java:153)
> at
> JAXRFindBusiness.main(JAXRFindBusiness.java:69)
> Caused by:
> at
> org.apache.ws.scout.registry.RegistryImpl.execute(RegistryImpl.java:357)
>
> at
> org.apache.ws.scout.registry.RegistryImpl.findBusiness(RegistryImpl.java:666
> )
> at
> org.apache.ws.scout.registry.BusinessQueryManagerImpl.findOrganizations(Busi
> nessQueryManagerImpl.java:126)
> ... 1 more
>
>
>
> When running JAXRGetProviderOrganization (attached) with the same
> configuration, I get the following exception:
>
>
> AxisFault
> faultCode: Server
> faultSubcode:
> faultString: local part cannot
> be "null" when creating a QName
> faultActor:
> faultNode:
>
> faultDetail:
> {urn:uddi-org:api_v2}dispositionReport:<result
> errno="10500"><errInfo errCode="E_fatalError">A serious technical exception
> has occurred while processing the request. An internal UDDI server error has
> occurred. Please report this error to the UDDI server
> administrator.</errInfo></result>
>
> local part cannot be "null" when creating
> a QName
> at
> org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:2
> 22)
> at
> org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:12
> 9)
> at
> org.apache.axis.encoding.DeserializationContext.endElement(DeserializationCo
> ntext.java:1087)
> at
> com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(Abst
> ractSAXParser.java:633)
> at
> com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanEndElem
> ent(XMLNSDocumentScannerImpl.java:719)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$Fragm
> entContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1685)
>
> at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanD
> ocument(XMLDocumentFragmentScannerImpl.java:368)
> at
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Con
> figuration.java:834)
> at
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Con
> figuration.java:764)
> at
> com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:14
> 8)
> at
> com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractS
> AXParser.java:1242)
> at
> javax.xml.parsers.SAXParser.parse(SAXParser.java:375)
> at
> org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext
> .java:227)
> at
> org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
> at
> org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
> at
> org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChe
> cker.java:62)
> at
> org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
> at
> org.apache.axis.client.Call.invokeEngine(Call.java:2784)
> at
> org.apache.axis.client.Call.invoke(Call.java:2767)
> at
> org.apache.axis.client.Call.invoke(Call.java:1792)
> at
> org.apache.ws.scout.transport.AxisTransport.send(AxisTransport.java:66)
>
> at org.apache.ws.scout.registry.RegistryImpl.execute(RegistryImpl.java:271)
>
> at
> org.apache.ws.scout.registry.RegistryImpl.findBusiness(RegistryImpl.java:666
> )
> at
> org.apache.ws.scout.registry.BusinessQueryManagerImpl.findOrganizations(Busi
> nessQueryManagerImpl.java:126)
> at
> org.apache.ws.scout.registry.BusinessQueryManagerImpl.getRegistryObjects(Bus
> inessQueryManagerImpl.java:941)
> at
> JAXRGetProviderOrganization.main(JAXRGetProviderOrganization.java:78)
> SOAP
> message:
> <soapenv:Fault
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><faultcode>Server<
> /faultcode><faultstring>local part cannot be "null" when creating a
> QName</faultstring><faultactor/><detail
> xmlns:axis2ns3="urn:uddi-org:api_v2"><axis2ns3:dispositionReport
> generic="2.0" operator="jUDDI.org"><result errno="10500"><errInfo
> errCode="E_fatalError">A serious technical exception has occurred while
> processing the request. An internal UDDI server error has occurred. Please
> report this error to the UDDI server
> administrator.</errInfo></result></axis2ns3:dispositionReport></detail></soa
> penv:Fault>
> javax.xml.registry.JAXRException:
> at
> org.apache.ws.scout.registry.BusinessQueryManagerImpl.findOrganizations(Busi
> nessQueryManagerImpl.java:153)
> at
> org.apache.ws.scout.registry.BusinessQueryManagerImpl.getRegistryObjects(Bus
> inessQueryManagerImpl.java:941)
> at
> JAXRGetProviderOrganization.main(JAXRGetProviderOrganization.java:78)
> Caused
> by:
> at
> org.apache.ws.scout.registry.RegistryImpl.execute(RegistryImpl.java:357)
>
> at
> org.apache.ws.scout.registry.RegistryImpl.findBusiness(RegistryImpl.java:666
> )
> at
> org.apache.ws.scout.registry.BusinessQueryManagerImpl.findOrganizations(Busi
> nessQueryManagerImpl.java:126)
> ... 2 more
>
>
>
>
> Now, how can I JIRA these issues?
>
>
> Kind regards,
>
> Javier
>
>
>
>
>
> Am 05.11.2007 16:53 Uhr schrieb "Kurt T Stam" unter <ks...@apache.org>:
>
>
>> 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
Re: Scout problems
Posted by Javier Botana <ja...@uni-koeln.de>.
Hi Kurt,
Thanks for your quick answer.
I have already tried this. I use scout-1.0rc1.jar and jaxr-api-1.0rc1.jar
from the Scout web site. When running the attached class JAXRFindBusiness in
the console (assuming I have run SaveJAXROrganization twice before whith the
old configuration), I get the following output:
Organization(s) found: 2
Organization key: 16133CE0-8BA0-11DC-BCE0-98ACD5633B51
Organization name: null
Organization description: null
Contact name: Steve Viens
Phone Numbers size: 0
Email Addresses size: 0
Postal Addresses Size: 0
Services found: 1
Service name: null
Service description: null
---
Organization key: FF31FFC0-8B9F-11DC-BFC0-C1B679CFD8D9
Organization name: null
Organization description: null
Contact name: Steve Viens
Phone Numbers size: 0
Email Addresses size: 0
Postal Addresses Size: 0
Services found: 1
Service name: null
Service description: null
The output is the same if I use a scout.jar build from the current trunk.
Now I have build a new juddi.war from the current trunk (copied missing
resources manually, see mail "Problems with juddi.war built from trunk" on
jUDDI list), deployed to Tomcat 5.5.20, and created a new MySQL database.
When running JAXRFindBusiness with the latest Scout snapshot and
jaxr-api-1.0rc1.jar from the Scout web site, I get the
AxisFault
faultCode: Client
faultSubcode:
faultString: E_unsupported
(10050) The implementor does not support a feature or API. find_business:
findQualifier=null
faultActor:
faultNode:
faultDetail:
{urn:uddi-org:api_v2}dispositionReport:<result errno="10050"><errInfo
errCode="E_unsupported">E_unsupported (10050) The implementor does not
support a feature or API. find_business:
findQualifier=null</errInfo></result>
E_unsupported (10050) The implementor
does not support a feature or API. find_business: findQualifier=null
at
org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:2
22)
at
org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:12
9)
at
org.apache.axis.encoding.DeserializationContext.endElement(DeserializationCo
ntext.java:1087)
at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(Abst
ractSAXParser.java:633)
at
com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanEndElem
ent(XMLNSDocumentScannerImpl.java:719)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$Fragm
entContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1685)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanD
ocument(XMLDocumentFragmentScannerImpl.java:368)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Con
figuration.java:834)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Con
figuration.java:764)
at
com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:14
8)
at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractS
AXParser.java:1242)
at
javax.xml.parsers.SAXParser.parse(SAXParser.java:375)
at
org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext
.java:227)
at
org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
at
org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
at
org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChe
cker.java:62)
at
org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
at
org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at
org.apache.axis.client.Call.invoke(Call.java:2767)
at
org.apache.axis.client.Call.invoke(Call.java:1792)
at
org.apache.ws.scout.transport.AxisTransport.send(AxisTransport.java:66)
at org.apache.ws.scout.registry.RegistryImpl.execute(RegistryImpl.java:271)
at
org.apache.ws.scout.registry.RegistryImpl.findBusiness(RegistryImpl.java:666
)
at
org.apache.ws.scout.registry.BusinessQueryManagerImpl.findOrganizations(Busi
nessQueryManagerImpl.java:126)
at
JAXRFindBusiness.main(JAXRFindBusiness.java:69)
SOAP message:
<soapenv:Fault
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><faultcode>Client<
/faultcode><faultstring>E_unsupported (10050) The implementor does not
support a feature or API. find_business:
findQualifier=null</faultstring><faultactor/><detail
xmlns:axis2ns1="urn:uddi-org:api_v2"><axis2ns1:dispositionReport
generic="2.0" operator="jUDDI.org"><result errno="10050"><errInfo
errCode="E_unsupported">E_unsupported (10050) The implementor does not
support a feature or API. find_business:
findQualifier=null</errInfo></result></axis2ns1:dispositionReport></detail><
/soapenv:Fault>
javax.xml.registry.JAXRException:
at
org.apache.ws.scout.registry.BusinessQueryManagerImpl.findOrganizations(Busi
nessQueryManagerImpl.java:153)
at
JAXRFindBusiness.main(JAXRFindBusiness.java:69)
Caused by:
at
org.apache.ws.scout.registry.RegistryImpl.execute(RegistryImpl.java:357)
at
org.apache.ws.scout.registry.RegistryImpl.findBusiness(RegistryImpl.java:666
)
at
org.apache.ws.scout.registry.BusinessQueryManagerImpl.findOrganizations(Busi
nessQueryManagerImpl.java:126)
... 1 more
When running JAXRGetProviderOrganization (attached) with the same
configuration, I get the following exception:
AxisFault
faultCode: Server
faultSubcode:
faultString: local part cannot
be "null" when creating a QName
faultActor:
faultNode:
faultDetail:
{urn:uddi-org:api_v2}dispositionReport:<result
errno="10500"><errInfo errCode="E_fatalError">A serious technical exception
has occurred while processing the request. An internal UDDI server error has
occurred. Please report this error to the UDDI server
administrator.</errInfo></result>
local part cannot be "null" when creating
a QName
at
org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:2
22)
at
org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:12
9)
at
org.apache.axis.encoding.DeserializationContext.endElement(DeserializationCo
ntext.java:1087)
at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(Abst
ractSAXParser.java:633)
at
com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanEndElem
ent(XMLNSDocumentScannerImpl.java:719)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$Fragm
entContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1685)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanD
ocument(XMLDocumentFragmentScannerImpl.java:368)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Con
figuration.java:834)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Con
figuration.java:764)
at
com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:14
8)
at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractS
AXParser.java:1242)
at
javax.xml.parsers.SAXParser.parse(SAXParser.java:375)
at
org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext
.java:227)
at
org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
at
org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
at
org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChe
cker.java:62)
at
org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
at
org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at
org.apache.axis.client.Call.invoke(Call.java:2767)
at
org.apache.axis.client.Call.invoke(Call.java:1792)
at
org.apache.ws.scout.transport.AxisTransport.send(AxisTransport.java:66)
at org.apache.ws.scout.registry.RegistryImpl.execute(RegistryImpl.java:271)
at
org.apache.ws.scout.registry.RegistryImpl.findBusiness(RegistryImpl.java:666
)
at
org.apache.ws.scout.registry.BusinessQueryManagerImpl.findOrganizations(Busi
nessQueryManagerImpl.java:126)
at
org.apache.ws.scout.registry.BusinessQueryManagerImpl.getRegistryObjects(Bus
inessQueryManagerImpl.java:941)
at
JAXRGetProviderOrganization.main(JAXRGetProviderOrganization.java:78)
SOAP
message:
<soapenv:Fault
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><faultcode>Server<
/faultcode><faultstring>local part cannot be "null" when creating a
QName</faultstring><faultactor/><detail
xmlns:axis2ns3="urn:uddi-org:api_v2"><axis2ns3:dispositionReport
generic="2.0" operator="jUDDI.org"><result errno="10500"><errInfo
errCode="E_fatalError">A serious technical exception has occurred while
processing the request. An internal UDDI server error has occurred. Please
report this error to the UDDI server
administrator.</errInfo></result></axis2ns3:dispositionReport></detail></soa
penv:Fault>
javax.xml.registry.JAXRException:
at
org.apache.ws.scout.registry.BusinessQueryManagerImpl.findOrganizations(Busi
nessQueryManagerImpl.java:153)
at
org.apache.ws.scout.registry.BusinessQueryManagerImpl.getRegistryObjects(Bus
inessQueryManagerImpl.java:941)
at
JAXRGetProviderOrganization.main(JAXRGetProviderOrganization.java:78)
Caused
by:
at
org.apache.ws.scout.registry.RegistryImpl.execute(RegistryImpl.java:357)
at
org.apache.ws.scout.registry.RegistryImpl.findBusiness(RegistryImpl.java:666
)
at
org.apache.ws.scout.registry.BusinessQueryManagerImpl.findOrganizations(Busi
nessQueryManagerImpl.java:126)
... 2 more
Now, how can I JIRA these issues?
Kind regards,
Javier
Am 05.11.2007 16:53 Uhr schrieb "Kurt T Stam" unter <ks...@apache.org>:
> 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
Re: Scout problems
Posted by Kurt T Stam <ks...@apache.org>.
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
Scout problems
Posted by Javier Botana <ja...@uni-koeln.de>.
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
Re: scout-v1.0rc1 is out
Posted by Lin Sun <li...@gmail.com>.
FYI - we've tested this in geronimo env, so far it looks good. :)
Lin
Anil Saldhana wrote:
> Great news and great job driving it, Kurt. ;)
>
> */Kurt T Stam <ks...@apache.org>/* wrote:
>
> Hi guys,
>
> Scout-1.0rc1 is out :). The website should update itself within the hour
> to reflect the new release.
> But if you can't wait you can download the jars here:
>
> http://people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/ws/scout/
>
> RELEASE NOTES
>
> Release Notes - Scout - Version 1.0rc1
>
> ** Bug
> * [SCOUT-23] - Classification are not saved.
> * [SCOUT-25] - FindBinding does not work + patch
> * [SCOUT-26] - Removing a service does not remove the service + patch
> * [SCOUT-28] - XmlBeans conversion compiles but is non-functional
> * [SCOUT-29] - AuthTokenImpl.getAuthInfo() doesn't seem to work
> correctly
> * [SCOUT-30] - Classifications are ignored when preforming finds.
> * [SCOUT-31] - Fix scout maven 1 build issue so that the dependency
> jars can be downloaded automatically
> * [SCOUT-32] - Fix NPE at getConcept
> * [SCOUT-33] - Should throw exception when level 1 feature is
> accessed in RegistryEntryImpl.java
> * [SCOUT-34] - DiscoveryURLs aren't constructed correctly when there
> is more than 1 discoveryURLs for a businessEntity
> * [SCOUT-35] - Should use hashset for the collection in
> BulkResponseImpl to not allow duplicate
> * [SCOUT-36] - minor update to get scout maven 2 build pass the
> error in download juddi snapshot
> * [SCOUT-40] - InternationalString is not handled correctly
> * [SCOUT-41] - Results not returned in the given order
> * [SCOUT-44] - port fixes for scout 8 to trunk
> * [SCOUT-45] - port scout 19 to trunk
> * [SCOUT-46] - port scout 10 to trunk
>
> ** Improvement
> * [SCOUT-9] - Separation of Apache Scout and jUDDI
>
> ** New Feature
> * [SCOUT-18] - Embedded mode execution
>
> ** Task
> * [SCOUT-27] - Update Tests with embedded juddi setup
> * [SCOUT-37] - Cleanup code to get rid of warnings
> * [SCOUT-38] - Produce website from the maven2 build
> * [SCOUT-39] - Integrate all sample code in unittests
> * [SCOUT-42] - apply fixes on 0.7 branches to the trunk
>
> Cheers,
>
> --Kurt
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: scout-dev-help@ws.apache.org
>
>
> ------------------------------------------------------------------------
> Be a better Heartthrob. Get better relationship answers
> <http://us.rd.yahoo.com/evt=48255/*http://answers.yahoo.com/dir/_ylc=X3oDMTI5MGx2aThyBF9TAzIxMTU1MDAzNTIEX3MDMzk2NTQ1MTAzBHNlYwNCQUJwaWxsYXJfTklfMzYwBHNsawNQcm9kdWN0X3F1ZXN0aW9uX3BhZ2U-?link=list&sid=396545433>from
> someone who knows.
> Yahoo! Answers - Check it out.
---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org
Re: scout-v1.0rc1 is out
Posted by Anil Saldhana <an...@yahoo.com>.
Great news and great job driving it, Kurt. ;)
Kurt T Stam <ks...@apache.org> wrote: Hi guys,
Scout-1.0rc1 is out :). The website should update itself within the hour
to reflect the new release.
But if you can't wait you can download the jars here:
http://people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/ws/scout/
RELEASE NOTES
Release Notes - Scout - Version 1.0rc1
** Bug
* [SCOUT-23] - Classification are not saved.
* [SCOUT-25] - FindBinding does not work + patch
* [SCOUT-26] - Removing a service does not remove the service + patch
* [SCOUT-28] - XmlBeans conversion compiles but is non-functional
* [SCOUT-29] - AuthTokenImpl.getAuthInfo() doesn't seem to work correctly
* [SCOUT-30] - Classifications are ignored when preforming finds.
* [SCOUT-31] - Fix scout maven 1 build issue so that the dependency jars can be downloaded automatically
* [SCOUT-32] - Fix NPE at getConcept
* [SCOUT-33] - Should throw exception when level 1 feature is accessed in RegistryEntryImpl.java
* [SCOUT-34] - DiscoveryURLs aren't constructed correctly when there is more than 1 discoveryURLs for a businessEntity
* [SCOUT-35] - Should use hashset for the collection in BulkResponseImpl to not allow duplicate
* [SCOUT-36] - minor update to get scout maven 2 build pass the error in download juddi snapshot
* [SCOUT-40] - InternationalString is not handled correctly
* [SCOUT-41] - Results not returned in the given order
* [SCOUT-44] - port fixes for scout 8 to trunk
* [SCOUT-45] - port scout 19 to trunk
* [SCOUT-46] - port scout 10 to trunk
** Improvement
* [SCOUT-9] - Separation of Apache Scout and jUDDI
** New Feature
* [SCOUT-18] - Embedded mode execution
** Task
* [SCOUT-27] - Update Tests with embedded juddi setup
* [SCOUT-37] - Cleanup code to get rid of warnings
* [SCOUT-38] - Produce website from the maven2 build
* [SCOUT-39] - Integrate all sample code in unittests
* [SCOUT-42] - apply fixes on 0.7 branches to the trunk
Cheers,
--Kurt
---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org
---------------------------------
Be a better Heartthrob. Get better relationship answers from someone who knows.
Yahoo! Answers - Check it out.