Re: [akka-user] Unable to locate akka schema

[√iktor Ҡlang]

http://repo.akka.io/akka-1.3.1.xsd

Looks good to me.

Cheers,

√

On Thu, Jan 17, 2013 at 1:00 AM, Varsha Neelesh <varsha....@gmail.com> wrote:

I am pretty new to akka and trying it out. This may be a trivial issue on my side which I'm not able to recognize. I have the below xml (copied just a portion). 

<beans xmlns="http://www.springframework.org/schema/beans"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:amq="http://activemq.apache.org/schema/core"
    xmlns:context="http://www.springframework.org/schema/context"
    xmlns:akka="http://repo.akka.io/schema/akka"
    xmlns:jdbc="http://www.springframework.org/schema/jdbc"
    xsi:schemaLocation="
http://activemq.apache.org/schema/core 
http://activemq.apache.org/schema/core/activemq-core.xsd
http://www.springframework.org/schema/beans 
http://www.springframework.org/schema/beans/spring-beans-3.0.xsd
http://camel.apache.org/schema/spring 
http://camel.apache.org/schema/spring/camel-spring.xsd
http://repo.akka.io/schema/akka
http://repo.akka.io/akka-1.3.1.xsd
http://www.springframework.org/schema/context 
http://www.springframework.org/schema/context/spring-context-3.0.xsd">

.......

  <akka:camel-service id="camelService">
    <akka:camel-context ref="camelContext" />
  </akka:camel-service>

</bean>

Looks like the schema is not available for akka. I get the error, The matching wildcard is strict, but no declaration can be found for element 'akka:camel-service'. Any help is appreciated. Thanks!

--
>>>>>>>>>> Read the docs: http://akka.io/docs/
>>>>>>>>>> Check the FAQ: http://akka.io/faq/
>>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user
---
You received this message because you are subscribed to the Google Groups "Akka User List" group.
To post to this group, send email to akka...@googlegroups.com.
To unsubscribe from this group, send email to akka-user+...@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user?hl=en.
 
 

--

Viktor Klang
Director of Engineering

Typesafe - The software stack for applications that scale
Twitter: @viktorklang

[Rich Dougherty]

Hmm, thanks.

The problem seems to be we have declarations like:

   <xsd:sequence>

      <xsd:element name="remote" type="remote-type" minOccurs="0" maxOccurs="1"/>

      <xsd:element name="dispatcher" type="dispatcher-type" minOccurs="0" maxOccurs="1"/>

      <xsd:element ref="dispatcher" minOccurs="0" maxOccurs="1"/>

      <xsd:element ref="beans:property" minOccurs="0" maxOccurs="unbounded"/>

    </xsd:sequence>

Where

<xsd:element name="dispatcher" type="dispatcher-type"/>

On Thu, Jan 17, 2013 at 6:39 PM, Varsha Neelesh <varsha....@gmail.com> wrote:

Looks like the xsd has errors as per the w3 xsd validator. I tried to verify it at http://www.w3.org/2001/03/webdata/xsv and see the error 

Schema representation errors

Detected during instance validation

http://repo.akka.io/akka-1.3.1.xsd:192:3: Invalid: non-deterministic content model for type untyped-actor-type: {http://akka.io/schema/akka}:dispatcher/{http://akka.io/schema/akka}:dispatcher

http://repo.akka.io/akka-1.3.1.xsd:132:3: Invalid: non-deterministic content model for type typed-actor-type: {http://akka.io/schema/akka}:dispatcher/{http://akka.io/schema/akka}:dispatcher

You can see the error at

http://www.w3.org/2001/03/webdata/xsv?docAddrs=http%3A%2F%2Frepo.akka.io%2Fakka-1.3.1.xsd&warnings=on&independent=on&style=xsl#

Regards,

Varsha

[Rich Dougherty]

On Fri, Jan 18, 2013 at 1:42 PM, Rich Dougherty <ri...@rd.gen.nz> wrote:

Hmm, thanks.

The problem seems to be we have declarations like:

   <xsd:sequence>

      <xsd:element name="remote" type="remote-type" minOccurs="0" maxOccurs="1"/>

      <xsd:element name="dispatcher" type="dispatcher-type" minOccurs="0" maxOccurs="1"/>

      <xsd:element ref="dispatcher" minOccurs="0" maxOccurs="1"/>

      <xsd:element ref="beans:property" minOccurs="0" maxOccurs="unbounded"/>

    </xsd:sequence>

Where

<xsd:element name="dispatcher" type="dispatcher-type"/>

[Oops sent to early, let me finish my reply!] 

[Rich Dougherty]

Thanks for running that validation. The problem seems to be declarations like:

   <xsd:sequence>

      <xsd:element name="remote" type="remote-type" minOccurs="0" maxOccurs="1"/>

      <xsd:element name="dispatcher" type="dispatcher-type" minOccurs="0" maxOccurs="1"/>

      <xsd:element ref="dispatcher" minOccurs="0" maxOccurs="1"/>

      <xsd:element ref="beans:property" minOccurs="0" maxOccurs="unbounded"/>

    </xsd:sequence>

Where the ref="dispatcher" refers to:

  <xsd:element name="dispatcher" type="dispatcher-type"/>

So basically (I think) the two "dispatcher" declarations in the sequence are equivalent. The validator's complaining that it doesn't know which one it should pick when parsing.

The fix is probably just to eliminate one of the equivalent element declarations from the sequence declaration. I've raised a ticket, although I'm not sure about the maintenance status of Akka 1.3.

Do you know for sure that this fix would solve your problem? You could try by patching the XSD to make it valid and then loading it locally.

Cheers

Rich

On Thu, Jan 17, 2013 at 6:39 PM, Varsha Neelesh <varsha....@gmail.com> wrote:

Looks like the xsd has errors as per the w3 xsd validator. I tried to verify it at http://www.w3.org/2001/03/webdata/xsv and see the error 

Schema representation errors

Detected during instance validation

http://repo.akka.io/akka-1.3.1.xsd:192:3: Invalid: non-deterministic content model for type untyped-actor-type: {http://akka.io/schema/akka}:dispatcher/{http://akka.io/schema/akka}:dispatcher

http://repo.akka.io/akka-1.3.1.xsd:132:3: Invalid: non-deterministic content model for type typed-actor-type: {http://akka.io/schema/akka}:dispatcher/{http://akka.io/schema/akka}:dispatcher

You can see the error at

http://www.w3.org/2001/03/webdata/xsv?docAddrs=http%3A%2F%2Frepo.akka.io%2Fakka-1.3.1.xsd&warnings=on&independent=on&style=xsl#

Regards,

Varsha

On Wednesday, January 16, 2013 4:53:45 PM UTC-8, √ wrote:

[John MacAuley]

Just tried using the Spring Akka integration and my XML editor is failing on the Akka schema definition for the same issue.  I have run into this before a few times.  The issue is definitely the following two lines:

      <xsd:element name="dispatcher" type="dispatcher-type" minOccurs="0" maxOccurs="1"/>

      <xsd:element ref="dispatcher" minOccurs="0" maxOccurs="1"/>

If the first dispatcher element was mandatory there would not be an issue, however, because it is optional the validator cannot tell if the first or second dispatcher element was included.

Is there a timeframe for a fix?

Thanks!

[√iktor Ҡlang]

What Akka version?

--
>>>>>>>>>> Read the docs: http://akka.io/docs/

>>>>>>>>>> Check the FAQ: http://doc.akka.io/docs/akka/current/additional/faq.html

>>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user
---
You received this message because you are subscribed to the Google Groups "Akka User List" group.

To unsubscribe from this group and stop receiving emails from it, send an email to akka-user+...@googlegroups.com.

To post to this group, send email to akka...@googlegroups.com.

Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

--

Cheers,

√