taverna-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dmitry <redmi...@list.ru>
Subject Re: woden vs woden-api
Date Tue, 31 Mar 2015 16:21:24 GMT
The library is completely written by myself, but the copyright is BSC/INB.
As a developer I hate all these issues :-).

Both libraries are not released and for the practical use for Taverna 
are equal.

Dmitry

On 3/31/2015 6:09 PM, Stian Soiland-Reyes wrote:
> If you want to contribute it to Apache Taverna, then we can try to do
> an IP Clearance
>
> https://incubator.apache.org/ip-clearance/
>
>
> If it is only you who made it, then you just need to ask yourself (and
> your employer) as the copyright holder if you can relicense it and
> just change the license where it is now.
>
> ..then Apache Taverna can depend on it even if it's not contributed.
>
>
> On 31 March 2015 at 17:02, Dmitry <redmitry@list.ru> wrote:
>>> Perhaps your code depends on something that has changed after M9, and
>>> we would need to backdate it?
>> No. The only issue is the Apache XML Schema library version.
>> Note that because the interface is VERY similar M9 works with both versions.
>> This is because woden doesn't do anything to parse schema.
>>
>>> I think in the long run we should aim for your easyWSDL - is that a
>>> library you would be willing to donate to Apache Taverna or release
>>> separately to Maven Central from Github under a compatible license?
>>>
>>> (Name check: http://easywsdl.ow2.org/)
>> No. This is the parser that doesn't work.
>> The promised the 3d version many years ago...
>>
>> My parser is
>> http://sourceforge.net/projects/tinywsdl/
>>
>> The problem is that it is licensed as LGPL so I (?) have to relicense it.
>>
>>
>> On 3/31/2015 5:47 PM, Stian Soiland-Reyes wrote:
>>> M9 is still released Maven-wise, the SNAPSHOT could break tomorrow and
>>> is not a stable point release.  (You can hardcode timestamped
>>> SNAPSHOTS, but it's not ideal, and the maven release plugin would
>>> still bail out)
>>>
>>>
>>> Would you be able to figure out which dependencies we need from M9?
>>>
>>> Perhaps your code depends on something that has changed after M9, and
>>> we would need to backdate it?
>>>
>>> I think in the long run we should aim for your easyWSDL - is that a
>>> library you would be willing to donate to Apache Taverna or release
>>> separately to Maven Central from Github under a compatible license?
>>>
>>> (Name check: http://easywsdl.ow2.org/)
>>>
>>>
>>>
>>> On 31 March 2015 at 16:41, Dmitry <redmitry@list.ru> wrote:
>>>> Well, they have no any release version.
>>>>
>>>> M9 is milestone version.
>>>> https://ws.apache.org/woden/dev/1.0/milestoneplan.html
>>>>
>>>> It supposed to be a release 7 years ago.
>>>>
>>>> This situation was one of the reasons I developed "tinyWSDL".
>>>> Other reasons was that tinyWSDL supports WSDL generation, something that
>>>> woden fails to do.
>>>> It also supports HTTP bindings (REST).
>>>>
>>>> In defense of woden I may say that parsing is quite robust and had no
>>>> problems with it.
>>>>
>>>> tinyWSDL also has some issues with JAXB bugs:
>>>> https://java.net/jira/browse/JAXB-918
>>>> https://java.net/jira/browse/JAXB-935
>>>>
>>>> Hopefully these bugs doesn't affect SOAP bindings.
>>>> For our internal JBoss server I use a patched JAXB versions.
>>>>
>>>> Another WSDL 2.0 parser - EasyWSDL just doesn't work.
>>>>
>>>> So we have a little choice here.
>>>>
>>>> D.
>>>>
>>>>
>>>> On 3/31/2015 5:22 PM, Stian Soiland-Reyes wrote:
>>>>> do we need to depend on 1.0-SNAPSHOT? Then we can't release
>>>>> taverna-common-activities until woden 1.0 has been released.
>>>>>
>>>>>
>>>>>                    <dependency>
>>>>>                        <groupId>org.apache.woden</groupId>
>>>>>                        <artifactId>woden-core</artifactId>
>>>>>                        <version>1.0M9</version>
>>>>>                    </dependency>
>>>>>
>>>>> does not exist.
>>>>>
>>>>> Might be worth checking on dev@woden how their progress is going..
>>>>> (1.0M9 from last year is not even listed on their News list at
>>>>> https://ws.apache.org/woden/  yet :-( )
>>>>>
>>>>>
>>>>> On 31 March 2015 at 16:12, Dmitry <redmitry@list.ru> wrote:
>>>>>> <dependency>
>>>>>>        <groupId>org.apache.woden</groupId>
>>>>>>        <artifactId>woden-core</artifactId>
>>>>>>        <version>1.0-SNAPSHOT</version>
>>>>>> </dependency>
>>>>>>
>>>>>> works for me. at least dependencies graph shows that it is based
on
>>>>>> Apache
>>>>>> XML Schema 2.1.1
>>>>>>
>>>>>>
>>>>>>
>>>>>> On 3/31/2015 5:00 PM, Dmitry wrote:
>>>>>>> Hello Stian,
>>>>>>>
>>>>>>> I think there are more "woden-*" libraries than "woden-impl-dom"...
>>>>>>> On the other hand I see no difference in "woden-1.0M9.jar" and
>>>>>>> "woden-api-1.0M9.jar" apart of pom file.
>>>>>>>
>>>>>>> My environment is Netbeans 8. I just pull the git and build the
>>>>>>> modules
>>>>>>> of
>>>>>>> choice.
>>>>>>>
>>>>>>> The Error is something that worry me.
>>>>>>> Woden uses Apache XML Schema library version 1.4.7, while my
generic
>>>>>>> parser is based on version 2.1.
>>>>>>>
>>>>>>> Strangely enough, when I use "woden" artifactId, it doesn't put
1.4.7
>>>>>>> on
>>>>>>> dependency, but "woden-api" does.
>>>>>>> This makes two libraries clash - I see both in dependencies.
>>>>>>>
>>>>>>> I have been asked on Woden mail-list and was told that this is
fixed
>>>>>>> on
>>>>>>> v1
>>>>>>> https://issues.apache.org/jira/browse/WODEN-234
>>>>>>>
>>>>>>> On the other hand the snapshot version keeps reference to 1.4.7
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> https://repository.apache.org/content/groups/snapshots/org/apache/woden/woden/1.0-SNAPSHOT/woden-1.0-SNAPSHOT.pom
>>>>>>>
>>>>>>> Probably I should ask about this issue again
>>>>>>>
>>>>>>> Dmitry
>>>>>>>
>>>>>>> On 3/31/2015 4:26 PM, Stian Soiland-Reyes wrote:
>>>>>>>> Ideally in the OSGi world you would let the final user choose
- but I
>>>>>>>> think as wsdl-generic is meant to be a "WSDL in a box" library,
then
>>>>>>>> I agree that we should also depend on the chosen implementation.
>>>>>>>>
>>>>>>>> But if I add to
>>>>>>>> incubator-taverna-common-activities/taverna-wsdl-generic
on the
>>>>>>>> master
>>>>>>>> branch:
>>>>>>>>
>>>>>>>>                     <dependency>
>>>>>>>> <groupId>org.apache.woden</groupId>
>>>>>>>> <artifactId>woden-impl-dom</artifactId>
>>>>>>>>                         <version>1.0M9</version>
>>>>>>>>                     </dependency>
>>>>>>>>
>>>>>>>>
>>>>>>>> then it's still not compiling:
>>>>>>>>
>>>>>>>> [ERROR] COMPILATION ERROR :
>>>>>>>> [INFO] -------------------------------------------------------------
>>>>>>>> [ERROR]
>>>>>>>>
>>>>>>>>
>>>>>>>> /home/stain/src/taverna/incubator-taverna-common-activities/taverna-wsdl-generic/src/main/java/org/apache/taverna/wsdl/parser/TypeDescriptors.java:[61,34]
>>>>>>>> incompatible types: org.xml.sax.InputSource cannot be converted
to
>>>>>>>> org.w3c.dom.Element
>>>>>>>> [ERROR]
>>>>>>>>
>>>>>>>>
>>>>>>>> /home/stain/src/taverna/incubator-taverna-common-activities/taverna-wsdl-generic/src/main/java/org/apache/taverna/wsdl/parser/TypeDescriptors.java:[109,38]
>>>>>>>> cannot find symbol
>>>>>>>>       symbol:   method getParent()
>>>>>>>>       location: variable element of type
>>>>>>>> org.apache.ws.commons.schema.XmlSchemaElement
>>>>>>>> [ERROR]
>>>>>>>>
>>>>>>>>
>>>>>>>> /home/stain/src/taverna/incubator-taverna-common-activities/taverna-wsdl-generic/src/main/java/org/apache/taverna/wsdl/parser/TypeDescriptors.java:[111,48]
>>>>>>>> cannot find symbol
>>>>>>>>       symbol:   method getParent()
>>>>>>>>       location: variable xmlSchema of type
>>>>>>>> org.apache.ws.commons.schema.XmlSchema
>>>>>>>> [ERROR]
>>>>>>>>
>>>>>>>>
>>>>>>>> /home/stain/src/taverna/incubator-taverna-common-activities/taverna-wsdl-generic/src/main/java/org/apache/taverna/wsdl/parser/TypeDescriptors.java:[122,35]
>>>>>>>> cannot find symbol
>>>>>>>>       symbol:   method getParent()
>>>>>>>>       location: variable type of type
>>>>>>>> org.apache.ws.commons.schema.XmlSchemaType
>>>>>>>>
>>>>>>>> Is there something missing or wrong on the classpath here?
How have
>>>>>>>> you got it set up in your dev environment?
>>>>>>>>
>>>>>>>> On 30 March 2015 at 16:57, Dmitry <redmitry@list.ru>
wrote:
>>>>>>>>>> I could not get Maven to find the dependency with
just "woden"
>>>>>>>>>> (which
>>>>>>>>>> is
>>>>>>>>>> just a pom), are you sure we should depend on say
"woden-dom"? (Or
>>>>>>>>>> -om)?
>>>>>>>>>
>>>>>>>>> Well the library itself would compile just with the API,
but the
>>>>>>>>> execution
>>>>>>>>> (and tests) will definitely require the implementation.
>>>>>>>>>
>>>>>>>>>> Are we able to pick the implementation through OSGi
at the
>>>>>>>>>> product-level,
>>>>>>>>>> or do we simply choose one for wsdl-generic?
>>>>>>>>>
>>>>>>>>> I am not sure what do you mean here.
>>>>>>>>> Do we need to put a woden-version variable?
>>>>>>>>>
>>>>>>>>> I think the idea of wsdl-generic is to provide a transparent
parser
>>>>>>>>> so
>>>>>>>>> no-one else should care about which version of wsdl is
there...
>>>>>>>>>
>>>>>>>>> Dmitry
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On 3/30/2015 5:40 PM, Stian Soiland-Reyes wrote:
>>>>>>>>>> I could not get Maven to find the dependency with
just "woden"
>>>>>>>>>> (which
>>>>>>>>>> is
>>>>>>>>>> just a pom), are you sure we should depend on say
"woden-dom"? (Or
>>>>>>>>>> -om)?
>>>>>>>>>>
>>>>>>>>>> Are we able to pick the implementation through OSGi
at the
>>>>>>>>>> product-level,
>>>>>>>>>> or do we simply choose one for wsdl-generic?
>>>>>>>>>> On 30 Mar 2015 10:36, "Dmitry" <redmitry@list.ru>
wrote:
>>>>>>>>>>
>>>>>>>>>>> Hello,
>>>>>>>>>>>
>>>>>>>>>>> Woden WSDL 2.0 maven artifact should be "woden"
and not
>>>>>>>>>>> "woden-api".
>>>>>>>>>>> "woden" is the implementation of "woden-api"
(actually there are
>>>>>>>>>>> two
>>>>>>>>>>> implementations  - "woden-dom" and "woden-om").
>>>>>>>>>>>
>>>>>>>>>>> Cheers,
>>>>>>>>>>>
>>>>>>>>>>> Dmitry
>>>>>>>>>>>
>>>
>
>


Mime
View raw message