Re: http polling-connector schema definition missing in 2.0.1

I agree that schema changes should be dealt with a lot more sensitivity, it oh so easy to break a lot of apps out there depending on published  schemas. I would expect such changes to require a version change in the schema. I fact any schema change should require a version change. If mule developers agree that the 2.0 branch can get schema changes in 2.0.x releases, than i would expect published schemas like http://www.mulesource.org/schema/mule/core/2.0.2/ . It would certaily clear a few things up... Sorry, just felt like ranting a bit, I still think mule rules.

Thank you for your time, I'll let you know how it went with 2.0.2 SNAPSHOT

Jure

2008/7/4 Daniel Feist <dfeist@...>:

Hi,

It seems this polling-connector was added sometime after 2.0.1 was released.

I'm unsure why the schemas were updated, as the hosted schemas should match the latest release, which is 2.0.1 in this case.

If I were you I would use 2.0.2-SNAPSHOT until 2.0.2 is released, this has the updated schema, new polling http connector and a number of other improvements.

Dam

On Jul 4, 2008, at 3:29 AM, Jure Lodrant wrote:

Hi,

I'm trying to use http polling-connector in Mule 2.0.1, part of the http
transport. My mule config validates nicely using public xsd schema from
http://www.mulesource.org/schema/mule/http/2.0/mule-http.xsd.

A simple junit test, on the other hand, loading the same config fails during
schema validation with:

27   [main] ERROR org.mule.config.builders.AbstractConfigurationBuilder  -
Configuration with "org.mule.config.spring.SpringXmlConfigurationBuilder"
failed.
org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: Line 39
in XML document from URL
[file:/home/jurel/maven/upis-collector/target/test-classes/test-http-missing-interval.xml]
is invalid; nested exception is org.xml.sax.SAXParseException:
cvc-complex-type.2.4.a: Invalid content was found starting with
element 'http:polling-connector'. One
of '{"http://www.springframework.org/schema/beans":beans, "http://www.springframework.org/schema/beans":bean, "http://www.springframework.org/schema/context":property-placeholder, "http://www.mulesource.org/schema/mule/core/2.0":global-property, "http://www.mulesource.org/schema/mule/core/2.0":configuration, "http://www.mulesource.org/schema/mule/core/2.0":notifications, "http://www.mulesource.org/schema/mule/core/2.0":abstract-extension, "http://www.mulesource.org/schema/mule/core/2.0":abstract-security-manager, "http://www.mulesource.org/schema/mule/core/2.0":abstract-transaction-manager, "http://www.mulesource.org/schema/mule/core/2.0":abstract-connector, "http://www.mulesource.org/schema/mule/core/2.0":abstract-global-endpoint, "http://www.mulesource.org/schema/mule/core/2.0":abstract-transformer, "http://www.mulesource.org/schema/mule/core/2.0":abstract-filter, "http://www.mulesource.org/schema/mule/core/2.0":abstract-model}'
is expected.

I checked the mule-http.xsd included in mule-transport-http.jar (using maven
builds) and indeed, there is no definition of polling-connector (there is one
in http://www.mulesource.org/schema/mule/http/2.0/mule-http.xsd.

Can anyone provide any further insight? I'm failrly new to mule and still
fighting hard over available documentation (or lack thereof) so please be
gentle on me...

Thanks,

Jure

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

  http://xircles.codehaus.org/manage_email

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

  http://xircles.codehaus.org/manage_email