You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commons-dev@ws.apache.org by Jeremy Boynes <jb...@apache.org> on 2006/09/20 21:23:58 UTC

stax-api version

 From the POMs in the repo, AXIOM is using v1.0.1 but XMLSchema is  
still using 1.0
Would it be possible to update XmlSchema to 1.0.1 as well to make  
them consistent?

Thanks
--
Jeremy


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


Re: stax-api version

Posted by Jeremy Hughes <hu...@apache.org>.
+1 to a release of ws-commons-java5 (in case this wasn't already being
done) - we could use that in Woden too.

Thx,
Jeremy

On 9/24/06, Jeremy Boynes <jb...@apache.org> wrote:
> On Sep 22, 2006, at 1:07 PM, Davanum Srinivas wrote:
>
> > Jeremy,
> >
> > please check latest pom.xml and project.xml
> >
>
> Thanks - I built this locally and it seems to have solved our stax
> conflict problem. Can we release these (ws-commons-java5 and XmlSchema)?
> --
> Jeremy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: commons-dev-help@ws.apache.org
>
>

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


Re: stax-api version

Posted by Jeremy Boynes <jb...@apache.org>.
On Sep 22, 2006, at 1:07 PM, Davanum Srinivas wrote:

> Jeremy,
>
> please check latest pom.xml and project.xml
>

Thanks - I built this locally and it seems to have solved our stax  
conflict problem. Can we release these (ws-commons-java5 and XmlSchema)?
--
Jeremy

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


Re: stax-api version

Posted by Davanum Srinivas <da...@gmail.com>.
Jeremy,

please check latest pom.xml and project.xml

thanks,
dims

On 9/22/06, Jeremy Boynes <jb...@apache.org> wrote:
> On Sep 22, 2006, at 11:00 AM, Eran Chinthaka wrote:
>
> > Jeremy Boynes wrote:
> >> On Sep 21, 2006, at 5:38 AM, Jeremy Hughes wrote:
> >>>>
> >>
> >> It needs NamespaceContext as well so that one won't work.
> >
> > I didn't see that. Thanks.
> >
> >>
> >> We can still use stax-api, but how about scoping it to provided/
> >> optional
> >> so that it is not pulled in as a transitive dependency.
> >
> > No since QName is so common and used everywhere.
>
> That's kind of why we don't want to pull it in - by doing so we
> increase the potential for conflict with other things (which is what
> we have now in the form of a conflict with axiom/axis2). This is even
> worse in that we are pulling in an API (stax) that we are not
> actually using.
>
> >> The downside
> >> will mean the user needs to provide a version of javax.xml.namespace,
> >> but that is already part of both J2EE1.4 and Java5
> >
> > Remember our minimum requirement is JDK 1.4 nothing else and it
> > doesn't
> > contain QName, IIRC.
>
> Right and we need to support that. However, by hard-coding a
> dependency here we are introducing a direct conflict with two very
> common environments. IMO, better to say that in basic 1.4
> environments the user should supply their own version of
> javax.xml.namespace (which is what they need to do outside a Maven2
> environment anyway) rather than forcing stax on them.
>
> So basically, the only thing we are not supporting is users who use
> Maven2 on JDK1.4 and who want to use a transitive dependency from
> XmlSchema to get javax.xml.namespace onto the classpath. The upside
> is we avoid conflicts for all other users.
>
> --
> Jeremy
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: commons-dev-help@ws.apache.org
>
>


-- 
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)

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


Re: stax-api version

Posted by Jeremy Boynes <jb...@apache.org>.
On Sep 22, 2006, at 11:00 AM, Eran Chinthaka wrote:

> Jeremy Boynes wrote:
>> On Sep 21, 2006, at 5:38 AM, Jeremy Hughes wrote:
>>>>
>>
>> It needs NamespaceContext as well so that one won't work.
>
> I didn't see that. Thanks.
>
>>
>> We can still use stax-api, but how about scoping it to provided/ 
>> optional
>> so that it is not pulled in as a transitive dependency.
>
> No since QName is so common and used everywhere.

That's kind of why we don't want to pull it in - by doing so we  
increase the potential for conflict with other things (which is what  
we have now in the form of a conflict with axiom/axis2). This is even  
worse in that we are pulling in an API (stax) that we are not  
actually using.

>> The downside
>> will mean the user needs to provide a version of javax.xml.namespace,
>> but that is already part of both J2EE1.4 and Java5
>
> Remember our minimum requirement is JDK 1.4 nothing else and it  
> doesn't
> contain QName, IIRC.

Right and we need to support that. However, by hard-coding a  
dependency here we are introducing a direct conflict with two very  
common environments. IMO, better to say that in basic 1.4  
environments the user should supply their own version of  
javax.xml.namespace (which is what they need to do outside a Maven2  
environment anyway) rather than forcing stax on them.

So basically, the only thing we are not supporting is users who use  
Maven2 on JDK1.4 and who want to use a transitive dependency from  
XmlSchema to get javax.xml.namespace onto the classpath. The upside  
is we avoid conflicts for all other users.

--
Jeremy


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


Re: stax-api version

Posted by Eran Chinthaka <ch...@opensource.lk>.
Jeremy Boynes wrote:
> On Sep 21, 2006, at 5:38 AM, Jeremy Hughes wrote:
>>>
> 
> It needs NamespaceContext as well so that one won't work.

I didn't see that. Thanks.

> 
> We can still use stax-api, but how about scoping it to provided/optional
> so that it is not pulled in as a transitive dependency. 

No since QName is so common and used everywhere.

> The downside
> will mean the user needs to provide a version of javax.xml.namespace,
> but that is already part of both J2EE1.4 and Java5

Remember our minimum requirement is JDK 1.4 nothing else and it doesn't
contain QName, IIRC.

-- Chinthaka


Re: stax-api version

Posted by Jeremy Boynes <jb...@apache.org>.
On Sep 21, 2006, at 5:38 AM, Jeremy Hughes wrote:

> Chinthaka,
>
> If it's just QName you need, WSDL4J has a qname.jar with just that  
> class in it:
>
> http://www.ibiblio.org/pub/packages/maven2/wsdl4j/wsdl4j-qname/ 
> 1.5.2/wsdl4j-qname-1.5.2.jar
>

It needs NamespaceContext as well so that one won't work.

We can still use stax-api, but how about scoping it to provided/ 
optional so that it is not pulled in as a transitive dependency. The  
downside will mean the user needs to provide a version of  
javax.xml.namespace, but that is already part of both J2EE1.4 and Java5

--
Jeremy

Index: pom.xml
===================================================================
--- pom.xml     (revision 448996)
+++ pom.xml     (working copy)
@@ -357,8 +357,9 @@
          <dependency>
              <groupId>stax</groupId>
              <artifactId>stax-api</artifactId>
-            <version>1.0</version>
-            <scope>compile</scope>
+            <version>1.0.1</version>
+            <scope>provided</scope>
+            <optional>true</optional>
          </dependency>
      </dependencies>
      <reporting>


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


Re: stax-api version

Posted by Jeremy Hughes <hu...@apache.org>.
Chinthaka,

If it's just QName you need, WSDL4J has a qname.jar with just that class in it:

http://www.ibiblio.org/pub/packages/maven2/wsdl4j/wsdl4j-qname/1.5.2/wsdl4j-qname-1.5.2.jar

Regards,
Jeremy


On 9/21/06, Eran Chinthaka <ch...@opensource.lk> wrote:
> A small note on this.
>
> There is no huge difference between the two jars for XmlSchema. We are
> using the Stax-api jar just to get QName class. No other functionality
> of that jar is being used inside XmlSchema.
>
> Anyway, for consistency we can update it to the proper version.
>
> -- Chinthaka
>
> Jeremy Boynes wrote:
> > Dims
> >
> > I made the change locally and build "mvn package" with no problems - is
> > there anything else I should do before committing it?
> >
> > Thanks
> > --
> > Jeremy
> >
> > Index: pom.xml
> > ===================================================================
> > --- pom.xml     (revision 448415)
> > +++ pom.xml     (working copy)
> > @@ -357,7 +357,7 @@
> >          <dependency>
> >              <groupId>stax</groupId>
> >              <artifactId>stax-api</artifactId>
> > -            <version>1.0</version>
> > +            <version>1.0.1</version>
> >              <scope>compile</scope>
> >          </dependency>
> >      </dependencies>
> >
> > On Sep 20, 2006, at 12:26 PM, Davanum Srinivas wrote:
> >
> >> Jeremy,
> >>
> >> You have karma. Please go ahead and do the needful.
> >>
> >> -- dims
> >>
> >> On 9/20/06, Jeremy Boynes <jb...@apache.org> wrote:
> >>>  From the POMs in the repo, AXIOM is using v1.0.1 but XMLSchema is
> >>> still using 1.0
> >>> Would it be possible to update XmlSchema to 1.0.1 as well to make
> >>> them consistent?
> >>>
> >>> Thanks
> >>> --
> >>> Jeremy
> >>>
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: commons-dev-unsubscribe@ws.apache.org
> >>> For additional commands, e-mail: commons-dev-help@ws.apache.org
> >>>
> >>>
> >>
> >>
> >> --Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service
> >> Developers)
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: commons-dev-unsubscribe@ws.apache.org
> >> For additional commands, e-mail: commons-dev-help@ws.apache.org
> >>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: commons-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: commons-dev-help@ws.apache.org
> >
> >
>
>
>
>
>

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


Re: stax-api version

Posted by Eran Chinthaka <ch...@opensource.lk>.
A small note on this.

There is no huge difference between the two jars for XmlSchema. We are
using the Stax-api jar just to get QName class. No other functionality
of that jar is being used inside XmlSchema.

Anyway, for consistency we can update it to the proper version.

-- Chinthaka

Jeremy Boynes wrote:
> Dims
> 
> I made the change locally and build "mvn package" with no problems - is
> there anything else I should do before committing it?
> 
> Thanks
> -- 
> Jeremy
> 
> Index: pom.xml
> ===================================================================
> --- pom.xml     (revision 448415)
> +++ pom.xml     (working copy)
> @@ -357,7 +357,7 @@
>          <dependency>
>              <groupId>stax</groupId>
>              <artifactId>stax-api</artifactId>
> -            <version>1.0</version>
> +            <version>1.0.1</version>
>              <scope>compile</scope>
>          </dependency>
>      </dependencies>
> 
> On Sep 20, 2006, at 12:26 PM, Davanum Srinivas wrote:
> 
>> Jeremy,
>>
>> You have karma. Please go ahead and do the needful.
>>
>> -- dims
>>
>> On 9/20/06, Jeremy Boynes <jb...@apache.org> wrote:
>>>  From the POMs in the repo, AXIOM is using v1.0.1 but XMLSchema is
>>> still using 1.0
>>> Would it be possible to update XmlSchema to 1.0.1 as well to make
>>> them consistent?
>>>
>>> Thanks
>>> -- 
>>> Jeremy
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: commons-dev-unsubscribe@ws.apache.org
>>> For additional commands, e-mail: commons-dev-help@ws.apache.org
>>>
>>>
>>
>>
>> --Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service
>> Developers)
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: commons-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: commons-dev-help@ws.apache.org
>>
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: commons-dev-help@ws.apache.org
> 
> 



Re: stax-api version

Posted by Jeremy Boynes <jb...@apache.org>.
Dims

I made the change locally and build "mvn package" with no problems -  
is there anything else I should do before committing it?

Thanks
--
Jeremy

Index: pom.xml
===================================================================
--- pom.xml     (revision 448415)
+++ pom.xml     (working copy)
@@ -357,7 +357,7 @@
          <dependency>
              <groupId>stax</groupId>
              <artifactId>stax-api</artifactId>
-            <version>1.0</version>
+            <version>1.0.1</version>
              <scope>compile</scope>
          </dependency>
      </dependencies>

On Sep 20, 2006, at 12:26 PM, Davanum Srinivas wrote:

> Jeremy,
>
> You have karma. Please go ahead and do the needful.
>
> -- dims
>
> On 9/20/06, Jeremy Boynes <jb...@apache.org> wrote:
>>  From the POMs in the repo, AXIOM is using v1.0.1 but XMLSchema is
>> still using 1.0
>> Would it be possible to update XmlSchema to 1.0.1 as well to make
>> them consistent?
>>
>> Thanks
>> --
>> Jeremy
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: commons-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: commons-dev-help@ws.apache.org
>>
>>
>
>
> -- 
> Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service  
> Developers)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: commons-dev-help@ws.apache.org
>


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


Re: stax-api version

Posted by Davanum Srinivas <da...@gmail.com>.
Jeremy,

You have karma. Please go ahead and do the needful.

-- dims

On 9/20/06, Jeremy Boynes <jb...@apache.org> wrote:
>  From the POMs in the repo, AXIOM is using v1.0.1 but XMLSchema is
> still using 1.0
> Would it be possible to update XmlSchema to 1.0.1 as well to make
> them consistent?
>
> Thanks
> --
> Jeremy
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: commons-dev-help@ws.apache.org
>
>


-- 
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)

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