You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@juddi.apache.org by "Bryan Pendleton (JIRA)" <ju...@ws.apache.org> on 2009/11/09 01:39:32 UTC
[jira] Commented: (JUDDI-306) errors calling getOperationalInfo
[ https://issues.apache.org/jira/browse/JUDDI-306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12774840#action_12774840 ]
Bryan Pendleton commented on JUDDI-306:
---------------------------------------
Thanks Kurt!
Is it possible for me to build my own version of the 3.0 implementation which contains this fix?
If so, would it be better for me to take the 3.0 source zip and patch it? Or fetch the trunk from
subversion and build it?
> errors calling getOperationalInfo
> ----------------------------------
>
> Key: JUDDI-306
> URL: https://issues.apache.org/jira/browse/JUDDI-306
> Project: jUDDI
> Issue Type: Bug
> Components: core
> Affects Versions: 3.0
> Reporter: Kurt T Stam
> Assignee: Kurt T Stam
> Fix For: 3.0.1
>
>
> I've got the juddi 3.0 server up and running using the portal bundle.
> I can successfully run most operations, but when I try calling
> getOperationalInfo for one of my business service entities, I get
> the error stack below in my Tomcat server console, and on the client
> side I get a Soap fault with the text
> Marshalling Error: cvc-complex-type.4: Attribute 'entityKey' must appear on element 'operationalInfo'.
> Is this a known problem? Does it indicate that I am making an error
> in my getOperationalInfo call? The request I sent is :
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:urn="urn:uddi-org:api_v3">
> <soapenv:Header/>
> <soapenv:Body>
> <urn:get_operationalInfo>
> <urn:entityKey>uddi:juddi.apache.org:14c6b54e-0edf-4fec-be89-1a7b20ad9e19</urn:entityKey>
> </urn:get_operationalInfo>
> </soapenv:Body>
> </soapenv:Envelope>
> thanks,
> bryan
> P.S. Here's the error stack on the server side console:
> INFO: Interceptor has thrown exception, unwinding now
> org.apache.cxf.interceptor.Fault: Marshalling Error: cvc-complex-type.4: Attribu
> te 'entityKey' must appear on element 'operationalInfo'.
> at org.apache.cxf.jaxb.JAXBEncoderDecoder.marshall(JAXBEncoderDecoder.ja
> va:176)
> at org.apache.cxf.jaxb.io.DataWriterImpl.write(DataWriterImpl.java:166)
> at org.apache.cxf.interceptor.AbstractOutDatabindingInterceptor.writePar
> ts(AbstractOutDatabindingInterceptor.java:113)
> at org.apache.cxf.interceptor.BareOutInterceptor.handleMessage(BareOutIn
> terceptor.java:68)
> at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseIntercept
> orChain.java:220)
> at org.apache.cxf.interceptor.OutgoingChainInterceptor.handleMessage(Out
> goingChainInterceptor.java:74)
> at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseIntercept
> orChain.java:220)
> at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainIniti
> ationObserver.java:78)
> at org.apache.cxf.transport.servlet.ServletDestination.invoke(ServletDes
> tination.java:92)
> at org.apache.cxf.transport.servlet.ServletController.invokeDestination(
> ServletController.java:285)
> at org.apache.cxf.transport.servlet.ServletController.invoke(ServletCont
> roller.java:168)
> at org.apache.cxf.transport.servlet.AbstractCXFServlet.invoke(AbstractCX
> FServlet.java:175)
> at org.apache.cxf.transport.servlet.AbstractCXFServlet.doPost(AbstractCX
> FServlet.java:153)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
> icationFilterChain.java:290)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
> ilterChain.java:206)
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV
> alve.java:233)
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextV
> alve.java:191)
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j
> ava:128)
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
> ava:102)
> at org.apache.catalina.authenticator.SingleSignOn.invoke(SingleSignOn.ja
> va:394)
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal
> ve.java:109)
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.jav
> a:293)
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java
> :849)
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.proce
> ss(Http11Protocol.java:583)
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:45
> 4)
> at java.lang.Thread.run(Thread.java:619)
> Caused by: javax.xml.bind.MarshalException
> - with linked exception:
> [org.xml.sax.SAXParseException: cvc-complex-type.4: Attribute 'entityKey' must a
> ppear on element 'operationalInfo'.]
> at com.sun.xml.bind.v2.runtime.MarshallerImpl.write(MarshallerImpl.java:
> 328)
> at com.sun.xml.bind.v2.runtime.MarshallerImpl.marshal(MarshallerImpl.jav
> a:172)
> at org.apache.cxf.jaxb.JAXBEncoderDecoder.writeObject(JAXBEncoderDecoder
> .java:379)
> at org.apache.cxf.jaxb.JAXBEncoderDecoder.marshall(JAXBEncoderDecoder.ja
> va:155)
> ... 27 more
> Caused by: org.xml.sax.SAXParseException: cvc-complex-type.4: Attribute 'entityK
> ey' must appear on element 'operationalInfo'.
> at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAX
> ParseException(ErrorHandlerWrapper.java:195)
> at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.error(Err
> orHandlerWrapper.java:131)
> at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(
> XMLErrorReporter.java:384)
> at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(
> XMLErrorReporter.java:318)
> at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator$XSIErro
> rReporter.reportError(XMLSchemaValidator.java:410)
> at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.reportS
> chemaError(XMLSchemaValidator.java:3165)
> at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.addDefa
> ultAttributes(XMLSchemaValidator.java:2859)
> at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.handleS
> tartElement(XMLSchemaValidator.java:2041)
> at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.startEl
> ement(XMLSchemaValidator.java:685)
> at com.sun.org.apache.xerces.internal.jaxp.validation.ValidatorHandlerIm
> pl.startElement(ValidatorHandlerImpl.java:549)
> at org.xml.sax.helpers.XMLFilterImpl.startElement(XMLFilterImpl.java:527
> )
> at com.sun.xml.bind.v2.runtime.output.SAXOutput.endStartTag(SAXOutput.ja
> va:124)
> at com.sun.xml.bind.v2.runtime.output.ForkXmlOutput.endStartTag(ForkXmlO
> utput.java:102)
> at com.sun.xml.bind.v2.runtime.XMLSerializer.endAttributes(XMLSerializer
> .java:302)
> at com.sun.xml.bind.v2.runtime.XMLSerializer.childAsXsiType(XMLSerialize
> r.java:680)
> at com.sun.xml.bind.v2.runtime.property.ArrayElementNodeProperty.seriali
> zeItem(ArrayElementNodeProperty.java:65)
> at com.sun.xml.bind.v2.runtime.property.ArrayElementProperty.serializeLi
> stBody(ArrayElementProperty.java:168)
> at com.sun.xml.bind.v2.runtime.property.ArrayERProperty.serializeBody(Ar
> rayERProperty.java:152)
> at com.sun.xml.bind.v2.runtime.ClassBeanInfoImpl.serializeBody(ClassBean
> InfoImpl.java:322)
> at com.sun.xml.bind.v2.runtime.XMLSerializer.childAsXsiType(XMLSerialize
> r.java:681)
> at com.sun.xml.bind.v2.runtime.property.SingleElementNodeProperty.serial
> izeBody(SingleElementNodeProperty.java:150)
> at com.sun.xml.bind.v2.runtime.ElementBeanInfoImpl$1.serializeBody(Eleme
> ntBeanInfoImpl.java:156)
> at com.sun.xml.bind.v2.runtime.ElementBeanInfoImpl$1.serializeBody(Eleme
> ntBeanInfoImpl.java:185)
> at com.sun.xml.bind.v2.runtime.ElementBeanInfoImpl.serializeBody(Element
> BeanInfoImpl.java:305)
> at com.sun.xml.bind.v2.runtime.ElementBeanInfoImpl.serializeRoot(Element
> BeanInfoImpl.java:312)
> at com.sun.xml.bind.v2.runtime.ElementBeanInfoImpl.serializeRoot(Element
> BeanInfoImpl.java:71)
> at com.sun.xml.bind.v2.runtime.XMLSerializer.childAsRoot(XMLSerializer.j
> ava:490)
> at com.sun.xml.bind.v2.runtime.MarshallerImpl.write(MarshallerImpl.java:
> 325)
> ... 30 more
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: Building the 3.0.0 tag from svn using mvn (was JUDDI-306...)
Posted by Bryan Pendleton <bp...@amberpoint.com>.
Kurt T Stam wrote:
> 1. I just checked out the 3.0.0 tag on a clean machine ...
> and ran a successful build:
Hi Kurt, thanks for taking another look.
I'm sure this is something strange about my environment, as I get a similar
problem when trying to build the trunk.
Don't worry about it; I'll try and puzzle it out and let you know what I find.
In the meantime, as you say, I can build juddi-core, and that's the particular
thing I need for the time being, so I can continue to make progress in my
learning and study of the juddi system.
Thanks again for all the help!
bryan
Re: Building the 3.0.0 tag from svn using mvn (was JUDDI-306...)
Posted by Kurt T Stam <ku...@gmail.com>.
Hi Bryan,
1. I just checked out the 3.0.0 tag on a clean machine with the
following enviroment:
mvn -v
Apache Maven 2.2.1 (r801777; 2009-08-06 15:16:01-0400)
Java version: 1.6.0
Java home: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux" version: "2.6.18-128.1.10.el5xen" arch: "amd64" Family:
"unix"
Note that I have*
export MAVEN_OPTS='-Xmx512m'
*to give maven some more memory.
and ran a successful build:
mvn clean install
[INFO] Scanning for projects...
[INFO]
------------------------------------------------------------------------
[INFO] Building Maven Default Project
[INFO] task-segment: [clean, install]
[INFO] --------------------------------
.........
[INFO]
------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
------------------------------------------------------------------------
[INFO] jUDDI_v3 Parent ....................................... SUCCESS
[4:36.199s]
[INFO] UDDI_v3 WS Stubs and Schema Bindings Generated from WSDL SUCCESS
[4:10.919s]
[INFO] UDDI Technical Compatibility Kit (TCK) Base ........... SUCCESS
[14.392s]
[INFO] jUDDI Client side Code ................................ SUCCESS
[33.746s]
[INFO] jUDDI Core ............................................ SUCCESS
[3:35.382s]
[INFO] jUDDI Axis2 Deployment ................................ SUCCESS
[3:09.165s]
[INFO] jUDDI CXF Deployment .................................. SUCCESS
[1:47.150s]
[INFO] jUDDI Service Registration Examples ................... SUCCESS
[4.148s]
[INFO] jUDDI Tomcat Packaging ................................ SUCCESS
[31.068s]
[INFO] UDDI TCK Tests ........................................ SUCCESS
[4:25.793s]
[INFO] jUDDI Document Packaging .............................. SUCCESS
[5.758s]
[INFO]
------------------------------------------------------------------------
[INFO]
------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 23 minutes 14 seconds
[INFO] Finished at: Tue Nov 10 14:28:36 EST 2009
[INFO] Final Memory: 110M/265M
[INFO]
------------------------------------------------------------------------
[WARNING] [talledLocalContainer] Java Result: 143
[WARNING] [talledLocalContainer] Java Result: 143
The build takes a while b/c it's downloading all the maven build
artifacts (Subsequent builds take 3 min).
So I'm starting to think there is something wrong in your environment.
2. That said, the fix is in the juddi-core.jar, and I think you already
have that building? Just take that jar and replace the one in
your distribution.
--Kurt
Bryan Pendleton wrote:
> Hi Kurt,
>
> Editing the word SNAPSHOT out of juddi-tomcat/bootstrap/pom.xml didn't
> seem to help; I still get the error about being unable to access
> org.apache.juddi:juddi-parent:pom:3.0.0.SNAPSHOT during the Tomcat
> packaging.
>
> I also found the word SNAPSHOT in
> juddi-console/uddi-portlets/uddi-portlets.launch,
> but editing it out of that file didn't help, either.
>
> However, I *was* able to build just the juddi-core POM using Maven, so
> for
> the purposes of verifying that I can use the fix for JUDDI-306, I
> should be
> able to make progress that way.
>
> But it would be really nice to figure out if I just have some sort of
> configuration
> error in my environment, or if it's just not possible to build the 3.0
> tag
> from subversion.
>
> I suppose the next thing I should try is to checkout the trunk, and
> see if I
> can successfully build it using my Maven installation?
>
> Are there Maven "debug" settings that I can configure which would give me
> more information about where the SNAPSHOT reference is coming from?
>
> thanks,
>
> bryan
>
> Kurt T Stam wrote:
>> Bryan Pendleton wrote:
>>>> Can you do a find to see if any pom is referencing 3.0.0.SNAPSHOT?
>>>> It really should be referencing 3.0.0.
>>>
>>> Hi Kurt,
>>>
>>> The SNAPSHOT reference appears to be in juddi-tomcat/bootstrap/pom.xml
>>> (http://svn.apache.org/viewvc/webservices/juddi/tags/juddi-3.0.0/juddi-tomcat/bootstrap/pom.xml?view=markup)
>>>
>>>
>>> Should I try editing out the word "SNAPSHOT" from this file and see
>>> if that resolves my build problem?
>>>
>>> thanks,
>>>
>>> bryan
>>>
>>>
>> Yes please, that target is only used to get tomcat-6 into our repos,
>> so that we can use it for our builds.
>> There is not need to run this target itself.
>
>
>
Re: Building the 3.0.0 tag from svn using mvn (was JUDDI-306...)
Posted by Bryan Pendleton <bp...@amberpoint.com>.
Hi Kurt,
Editing the word SNAPSHOT out of juddi-tomcat/bootstrap/pom.xml didn't
seem to help; I still get the error about being unable to access
org.apache.juddi:juddi-parent:pom:3.0.0.SNAPSHOT during the Tomcat packaging.
I also found the word SNAPSHOT in juddi-console/uddi-portlets/uddi-portlets.launch,
but editing it out of that file didn't help, either.
However, I *was* able to build just the juddi-core POM using Maven, so for
the purposes of verifying that I can use the fix for JUDDI-306, I should be
able to make progress that way.
But it would be really nice to figure out if I just have some sort of configuration
error in my environment, or if it's just not possible to build the 3.0 tag
from subversion.
I suppose the next thing I should try is to checkout the trunk, and see if I
can successfully build it using my Maven installation?
Are there Maven "debug" settings that I can configure which would give me
more information about where the SNAPSHOT reference is coming from?
thanks,
bryan
Kurt T Stam wrote:
> Bryan Pendleton wrote:
>>> Can you do a find to see if any pom is referencing 3.0.0.SNAPSHOT? It
>>> really should be referencing 3.0.0.
>>
>> Hi Kurt,
>>
>> The SNAPSHOT reference appears to be in juddi-tomcat/bootstrap/pom.xml
>> (http://svn.apache.org/viewvc/webservices/juddi/tags/juddi-3.0.0/juddi-tomcat/bootstrap/pom.xml?view=markup)
>>
>>
>> Should I try editing out the word "SNAPSHOT" from this file and see
>> if that resolves my build problem?
>>
>> thanks,
>>
>> bryan
>>
>>
> Yes please, that target is only used to get tomcat-6 into our repos, so
> that we can use it for our builds.
> There is not need to run this target itself.
Re: Building the 3.0.0 tag from svn using mvn (was JUDDI-306...)
Posted by Kurt T Stam <ku...@gmail.com>.
Bryan Pendleton wrote:
>> Can you do a find to see if any pom is referencing 3.0.0.SNAPSHOT? It
>> really should be referencing 3.0.0.
>
> Hi Kurt,
>
> The SNAPSHOT reference appears to be in juddi-tomcat/bootstrap/pom.xml
> (http://svn.apache.org/viewvc/webservices/juddi/tags/juddi-3.0.0/juddi-tomcat/bootstrap/pom.xml?view=markup)
>
>
> Should I try editing out the word "SNAPSHOT" from this file and see
> if that resolves my build problem?
>
> thanks,
>
> bryan
>
>
Yes please, that target is only used to get tomcat-6 into our repos, so
that we can use it for our builds.
There is not need to run this target itself.
Re: Building the 3.0.0 tag from svn using mvn (was JUDDI-306...)
Posted by Bryan Pendleton <bp...@amberpoint.com>.
> Can you do a find to see if any pom is referencing 3.0.0.SNAPSHOT? It
> really should be referencing 3.0.0.
Hi Kurt,
The SNAPSHOT reference appears to be in juddi-tomcat/bootstrap/pom.xml
(http://svn.apache.org/viewvc/webservices/juddi/tags/juddi-3.0.0/juddi-tomcat/bootstrap/pom.xml?view=markup)
Should I try editing out the word "SNAPSHOT" from this file and see
if that resolves my build problem?
thanks,
bryan
Re: Building the 3.0.0 tag from svn using mvn (was JUDDI-306...)
Posted by Kurt T Stam <ku...@gmail.com>.
Hi Bryan,
Can you do a find to see if any pom is referencing 3.0.0.SNAPSHOT? It
really should be referencing 3.0.0.
Now you got me worried..
Thx,
--Kurt
Bryan Pendleton wrote:
> Kurt T Stam wrote:
>> Sure it's one line fix (see the commit in jira), just check out the
>> 3.0.0 tag, and run
>>
>> mvn install
>
> Hi Kurt, thanks for all the help so far.
>
> I'm kind of a Maven newbie, but I gave this a whirl.
>
> I fetched the 3.0.0 tag and ran mvn install.
>
> It ran along for 10 minutes and seemed to be working pretty successfully,
> then it aborted with the message below.
>
> Do I have a configuration problem?
>
> thanks,
>
> bryan
>
> Downloading:
> http://download.java.net/maven/2/org/apache/juddi/juddi-parent/3.0.
> 0.SNAPSHOT/juddi-parent-3.0.0.SNAPSHOT.pom
> [INFO] Unable to find resource
> 'org.apache.juddi:juddi-parent:pom:3.0.0.SNAPSHOT
> ' in repository maven2-repository.dev.java.net
> (http://download.java.net/maven/2
> )
> Downloading:
> http://download.java.net/maven/1/org.apache.juddi/poms/juddi-parent
> -3.0.0.SNAPSHOT.pom
> [INFO] Unable to find resource
> 'org.apache.juddi:juddi-parent:pom:3.0.0.SNAPSHOT
> ' in repository maven-repository.dev.java.net
> (http://download.java.net/maven/1)
> Downloading:
> http://people.apache.org/repo/m2-ibiblio-rsync-repository/org/apach
> e/juddi/juddi-parent/3.0.0.SNAPSHOT/juddi-parent-3.0.0.SNAPSHOT.pom
> [INFO] Unable to find resource
> 'org.apache.juddi:juddi-parent:pom:3.0.0.SNAPSHOT
> ' in repository apache
> (http://people.apache.org/repo/m2-ibiblio-rsync-repositor
> y)
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Failed to resolve artifact.
>
> GroupId: org.apache.juddi
> ArtifactId: juddi-parent
> Version: 3.0.0.SNAPSHOT
>
> Reason: Unable to download the artifact from any repository
>
> org.apache.juddi:juddi-parent:pom:3.0.0.SNAPSHOT
>
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2),
> apache (http://people.apache.org/repo/m2-ibiblio-rsync-repository),
> maven2-repository.dev.java.net (http://download.java.net/maven/2),
> maven-repository.dev.java.net (http://download.java.net/maven/1)
>
Building the 3.0.0 tag from svn using mvn (was JUDDI-306...)
Posted by Bryan Pendleton <bp...@amberpoint.com>.
Kurt T Stam wrote:
> Sure it's one line fix (see the commit in jira), just check out the 3.0.0 tag, and run
>
> mvn install
Hi Kurt, thanks for all the help so far.
I'm kind of a Maven newbie, but I gave this a whirl.
I fetched the 3.0.0 tag and ran mvn install.
It ran along for 10 minutes and seemed to be working pretty successfully,
then it aborted with the message below.
Do I have a configuration problem?
thanks,
bryan
Downloading: http://download.java.net/maven/2/org/apache/juddi/juddi-parent/3.0.
0.SNAPSHOT/juddi-parent-3.0.0.SNAPSHOT.pom
[INFO] Unable to find resource 'org.apache.juddi:juddi-parent:pom:3.0.0.SNAPSHOT
' in repository maven2-repository.dev.java.net (http://download.java.net/maven/2
)
Downloading: http://download.java.net/maven/1/org.apache.juddi/poms/juddi-parent
-3.0.0.SNAPSHOT.pom
[INFO] Unable to find resource 'org.apache.juddi:juddi-parent:pom:3.0.0.SNAPSHOT
' in repository maven-repository.dev.java.net (http://download.java.net/maven/1)
Downloading: http://people.apache.org/repo/m2-ibiblio-rsync-repository/org/apach
e/juddi/juddi-parent/3.0.0.SNAPSHOT/juddi-parent-3.0.0.SNAPSHOT.pom
[INFO] Unable to find resource 'org.apache.juddi:juddi-parent:pom:3.0.0.SNAPSHOT
' in repository apache (http://people.apache.org/repo/m2-ibiblio-rsync-repositor
y)
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to resolve artifact.
GroupId: org.apache.juddi
ArtifactId: juddi-parent
Version: 3.0.0.SNAPSHOT
Reason: Unable to download the artifact from any repository
org.apache.juddi:juddi-parent:pom:3.0.0.SNAPSHOT
from the specified remote repositories:
central (http://repo1.maven.org/maven2),
apache (http://people.apache.org/repo/m2-ibiblio-rsync-repository),
maven2-repository.dev.java.net (http://download.java.net/maven/2),
maven-repository.dev.java.net (http://download.java.net/maven/1)
Re: [jira] Commented: (JUDDI-306) errors calling getOperationalInfo
Posted by Kurt T Stam <ku...@gmail.com>.
Sure it's one line fix (see the commit in jira), just check out the
3.0.0 tag, and run
mvn install
and then if you also want to portal, you cd into juddi-console and do
mvn install
See also the Dev Guide.
You can also build the trunk, thus far only bug fixes have gone in and
no new features.
Cheers,
--Kurt
Bryan Pendleton (JIRA) wrote:
> [ https://issues.apache.org/jira/browse/JUDDI-306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12774840#action_12774840 ]
>
> Bryan Pendleton commented on JUDDI-306:
> ---------------------------------------
>
> Thanks Kurt!
>
> Is it possible for me to build my own version of the 3.0 implementation which contains this fix?
>
> If so, would it be better for me to take the 3.0 source zip and patch it? Or fetch the trunk from
> subversion and build it?
>
>
>
>> errors calling getOperationalInfo
>> ----------------------------------
>>
>> Key: JUDDI-306
>> URL: https://issues.apache.org/jira/browse/JUDDI-306
>> Project: jUDDI
>> Issue Type: Bug
>> Components: core
>> Affects Versions: 3.0
>> Reporter: Kurt T Stam
>> Assignee: Kurt T Stam
>> Fix For: 3.0.1
>>
>>
>> I've got the juddi 3.0 server up and running using the portal bundle.
>> I can successfully run most operations, but when I try calling
>> getOperationalInfo for one of my business service entities, I get
>> the error stack below in my Tomcat server console, and on the client
>> side I get a Soap fault with the text
>> Marshalling Error: cvc-complex-type.4: Attribute 'entityKey' must appear on element 'operationalInfo'.
>> Is this a known problem? Does it indicate that I am making an error
>> in my getOperationalInfo call? The request I sent is :
>> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
>> xmlns:urn="urn:uddi-org:api_v3">
>> <soapenv:Header/>
>> <soapenv:Body>
>> <urn:get_operationalInfo>
>> <urn:entityKey>uddi:juddi.apache.org:14c6b54e-0edf-4fec-be89-1a7b20ad9e19</urn:entityKey>
>> </urn:get_operationalInfo>
>> </soapenv:Body>
>> </soapenv:Envelope>
>> thanks,
>> bryan
>> P.S. Here's the error stack on the server side console:
>> INFO: Interceptor has thrown exception, unwinding now
>> org.apache.cxf.interceptor.Fault: Marshalling Error: cvc-complex-type.4: Attribu
>> te 'entityKey' must appear on element 'operationalInfo'.
>> at org.apache.cxf.jaxb.JAXBEncoderDecoder.marshall(JAXBEncoderDecoder.ja
>> va:176)
>> at org.apache.cxf.jaxb.io.DataWriterImpl.write(DataWriterImpl.java:166)
>> at org.apache.cxf.interceptor.AbstractOutDatabindingInterceptor.writePar
>> ts(AbstractOutDatabindingInterceptor.java:113)
>> at org.apache.cxf.interceptor.BareOutInterceptor.handleMessage(BareOutIn
>> terceptor.java:68)
>> at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseIntercept
>> orChain.java:220)
>> at org.apache.cxf.interceptor.OutgoingChainInterceptor.handleMessage(Out
>> goingChainInterceptor.java:74)
>> at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseIntercept
>> orChain.java:220)
>> at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainIniti
>> ationObserver.java:78)
>> at org.apache.cxf.transport.servlet.ServletDestination.invoke(ServletDes
>> tination.java:92)
>> at org.apache.cxf.transport.servlet.ServletController.invokeDestination(
>> ServletController.java:285)
>> at org.apache.cxf.transport.servlet.ServletController.invoke(ServletCont
>> roller.java:168)
>> at org.apache.cxf.transport.servlet.AbstractCXFServlet.invoke(AbstractCX
>> FServlet.java:175)
>> at org.apache.cxf.transport.servlet.AbstractCXFServlet.doPost(AbstractCX
>> FServlet.java:153)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
>> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
>> icationFilterChain.java:290)
>> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
>> ilterChain.java:206)
>> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV
>> alve.java:233)
>> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextV
>> alve.java:191)
>> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j
>> ava:128)
>> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
>> ava:102)
>> at org.apache.catalina.authenticator.SingleSignOn.invoke(SingleSignOn.ja
>> va:394)
>> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal
>> ve.java:109)
>> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.jav
>> a:293)
>> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java
>> :849)
>> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.proce
>> ss(Http11Protocol.java:583)
>> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:45
>> 4)
>> at java.lang.Thread.run(Thread.java:619)
>> Caused by: javax.xml.bind.MarshalException
>> - with linked exception:
>> [org.xml.sax.SAXParseException: cvc-complex-type.4: Attribute 'entityKey' must a
>> ppear on element 'operationalInfo'.]
>> at com.sun.xml.bind.v2.runtime.MarshallerImpl.write(MarshallerImpl.java:
>> 328)
>> at com.sun.xml.bind.v2.runtime.MarshallerImpl.marshal(MarshallerImpl.jav
>> a:172)
>> at org.apache.cxf.jaxb.JAXBEncoderDecoder.writeObject(JAXBEncoderDecoder
>> .java:379)
>> at org.apache.cxf.jaxb.JAXBEncoderDecoder.marshall(JAXBEncoderDecoder.ja
>> va:155)
>> ... 27 more
>> Caused by: org.xml.sax.SAXParseException: cvc-complex-type.4: Attribute 'entityK
>> ey' must appear on element 'operationalInfo'.
>> at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAX
>> ParseException(ErrorHandlerWrapper.java:195)
>> at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.error(Err
>> orHandlerWrapper.java:131)
>> at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(
>> XMLErrorReporter.java:384)
>> at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(
>> XMLErrorReporter.java:318)
>> at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator$XSIErro
>> rReporter.reportError(XMLSchemaValidator.java:410)
>> at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.reportS
>> chemaError(XMLSchemaValidator.java:3165)
>> at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.addDefa
>> ultAttributes(XMLSchemaValidator.java:2859)
>> at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.handleS
>> tartElement(XMLSchemaValidator.java:2041)
>> at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.startEl
>> ement(XMLSchemaValidator.java:685)
>> at com.sun.org.apache.xerces.internal.jaxp.validation.ValidatorHandlerIm
>> pl.startElement(ValidatorHandlerImpl.java:549)
>> at org.xml.sax.helpers.XMLFilterImpl.startElement(XMLFilterImpl.java:527
>> )
>> at com.sun.xml.bind.v2.runtime.output.SAXOutput.endStartTag(SAXOutput.ja
>> va:124)
>> at com.sun.xml.bind.v2.runtime.output.ForkXmlOutput.endStartTag(ForkXmlO
>> utput.java:102)
>> at com.sun.xml.bind.v2.runtime.XMLSerializer.endAttributes(XMLSerializer
>> .java:302)
>> at com.sun.xml.bind.v2.runtime.XMLSerializer.childAsXsiType(XMLSerialize
>> r.java:680)
>> at com.sun.xml.bind.v2.runtime.property.ArrayElementNodeProperty.seriali
>> zeItem(ArrayElementNodeProperty.java:65)
>> at com.sun.xml.bind.v2.runtime.property.ArrayElementProperty.serializeLi
>> stBody(ArrayElementProperty.java:168)
>> at com.sun.xml.bind.v2.runtime.property.ArrayERProperty.serializeBody(Ar
>> rayERProperty.java:152)
>> at com.sun.xml.bind.v2.runtime.ClassBeanInfoImpl.serializeBody(ClassBean
>> InfoImpl.java:322)
>> at com.sun.xml.bind.v2.runtime.XMLSerializer.childAsXsiType(XMLSerialize
>> r.java:681)
>> at com.sun.xml.bind.v2.runtime.property.SingleElementNodeProperty.serial
>> izeBody(SingleElementNodeProperty.java:150)
>> at com.sun.xml.bind.v2.runtime.ElementBeanInfoImpl$1.serializeBody(Eleme
>> ntBeanInfoImpl.java:156)
>> at com.sun.xml.bind.v2.runtime.ElementBeanInfoImpl$1.serializeBody(Eleme
>> ntBeanInfoImpl.java:185)
>> at com.sun.xml.bind.v2.runtime.ElementBeanInfoImpl.serializeBody(Element
>> BeanInfoImpl.java:305)
>> at com.sun.xml.bind.v2.runtime.ElementBeanInfoImpl.serializeRoot(Element
>> BeanInfoImpl.java:312)
>> at com.sun.xml.bind.v2.runtime.ElementBeanInfoImpl.serializeRoot(Element
>> BeanInfoImpl.java:71)
>> at com.sun.xml.bind.v2.runtime.XMLSerializer.childAsRoot(XMLSerializer.j
>> ava:490)
>> at com.sun.xml.bind.v2.runtime.MarshallerImpl.write(MarshallerImpl.java:
>> 325)
>> ... 30 more
>>
>
>