Chiradeep,
Whats the progress on this?
Cheers,
Hugo
On 22 jan. 2014, at 23:35, Chiradeep Vittal chiradeep.vit...@citrix.com wrote:
Reached out to @strikesme and @danwendlandt
On 1/21/14 10:14 PM, Hugo Trippaers htrippa...@schubergphilis.com
wrote:
We are now again at the exact same
I just pinged the attorney again (there is a live one assigned to this
question on the VMWare side).
What options will work? If we can provide some concrete options, perhaps
they will pick
1. Provide generated SDK jars in maven repo
2. Explicitly add ASL to WSDL
3. ?
--
Chiradeep
On 2/18/14
#1 would still need licensing sorted - explicitly it would need to be
a Cat A or Cat B license.
https://www.apache.org/legal/3party.html
#2 or similar would work I think (though I'd imagine they'd choose
MIT or BSD if going that route)
#3 A statement that they don't consider the WSDL
I'd say option 1 is the easiest to digest.
On that note, are we gaining anything (legal-wise) by switching to vijava?
I just uncompressed the download[1]. It bundles the compiled classes found
in vim25.jar which is (presumably) VMWare proprietary.
[1] http://vijava.sourceforge.net/
On 2/18/14
Option 1 still needs licensing sorted. Being on a maven repo still
doesn't fix the problem for us and our users.
WRT to vijava the classes in source all appear to have a copyright
header indicating that Steve is the author and licensed under BSD.
In example:
Not all.
http://sourceforge.net/p/vijava/code/283/tree/trunk/src/com/vmware/vim25/mo
/Alarm.java
On 2/18/14 12:05 PM, David Nalley da...@gnsa.us wrote:
Option 1 still needs licensing sorted. Being on a maven repo still
doesn't fix the problem for us and our users.
WRT to vijava the classes in
That's still licensed as BSD (the license header is in the file)
--David
On Tue, Feb 18, 2014 at 3:54 PM, Chiradeep Vittal
chiradeep.vit...@citrix.com wrote:
Not all.
http://sourceforge.net/p/vijava/code/283/tree/trunk/src/com/vmware/vim25/mo
/Alarm.java
On 2/18/14 12:05 PM, David Nalley
If vim25.jar source is BSD then why are we including it in noredist?
mvn install:install-file -Dfile=vim25_51.jar
-DgroupId=com.cloud.com.vmware -DartifactId=vmware-vim25-Dversion=5.1
-Dpackaging=jar
On 2/18/14 1:51 PM, David Nalley da...@gnsa.us wrote:
That's still licensed as BSD (the
The reason why it ended up at noredist build is that the binary jars are
copied from VMware SDK, we are not sure about the license implication and
we don’t build it from source.
In VMware 5.1 SDK, vim25.jar is generated from importing WSDL plus a
fix-up, the fix-up step is performed by a tool
Why do we need the WSDL at all? Why can't we check in vim25 sources like
the vijava project has done?
On 2/18/14 2:42 PM, Kelven Yang kelven.y...@citrix.com wrote:
The reason why it ended up at noredist build is that the binary jars are
copied from VMware SDK, we are not sure about the license
Where do we get the source code of vim25.jar the first place? VMware only
releases WSDL but not the java source, we can either copy it from vijava
or generate it ourselves to put it into our source repo, but if we do
generate, it would be easier to maintain the code base if this generation
step is
We don't know that it is. We know the vim25.jar is distributed to us
from the vmware SDK with different licensing.
On Tue, Feb 18, 2014 at 5:07 PM, Chiradeep Vittal
chiradeep.vit...@citrix.com wrote:
If vim25.jar source is BSD then why are we including it in noredist?
mvn install:install-file
On 2/18/14, 2:43 PM, Chiradeep Vittal chiradeep.vit...@citrix.com
wrote:
Why do we need the WSDL at all? Why can't we check in vim25 sources like
the vijava project has done?
We don’t have the vim25 source directly, further investigation showed that
vijava actually uses a different Web service
Reached out to @strikesme and @danwendlandt
On 1/21/14 10:14 PM, Hugo Trippaers htrippa...@schubergphilis.com
wrote:
We are now again at the exact same point as where Darren was.
This is the legal ticket relevant to the license discussion:
Heya,
Does anyone know about the current status the legal discussions around
including the WSDL or code generated by parsing the WSDL?
I would really like to have the vmware support in the normal build instead of
just in the noredist build. It would probably boost adoption amongst people
I bet we never got an answer. Frankly, I'd like to see us use
something where the licensing is clear. That, or we don't include the
WSDL in our repo / distro.
On Tue, Jan 21, 2014 at 3:40 AM, Hugo Trippaers h...@trippaers.nl wrote:
Heya,
Does anyone know about the current status the legal
On Tue, Jan 21, 2014 at 9:46 AM, Chip Childers chipchild...@apache.org wrote:
I bet we never got an answer. Frankly, I'd like to see us use
something where the licensing is clear. That, or we don't include the
WSDL in our repo / distro.
Additionally, we are an open source project that is in
Hugo,
I think we seems to come to a census that to use WSDL to generate the java
stub which is pretty much compatible to what we have right now.
Kelven
On 1/21/14, 12:40 AM, Hugo Trippaers h...@trippaers.nl wrote:
Heya,
Does anyone know about the current status the legal discussions around
Suboptimal for?
Wouldn't the ACS user want the best / supported client libraries?
Alternatively, can't we just compile the WSDL and check in the generated
sources? Not check-in the WSDL, but the client sources.
On 1/21/14 7:18 AM, David Nalley da...@gnsa.us wrote:
On Tue, Jan 21, 2014 at 9:46
Let's not repeat the previous discussion. We allready agreed that the wsdl is
the way forward. However we can't get any legal entity to say that it is ok to
do so.
Hence my proposal to at least move forward even if it means to temporarily use
vijava.
I really don't care what we do, as long
Chiradeep,
Even on the generated sources nobody seems willing to state that it is ok to
include them at the moment. Otherwise I would have put them in already.
Hugo
Sent from my iPhone
On 21 jan. 2014, at 19:32, Chiradeep Vittal chiradeep.vit...@citrix.com
wrote:
Suboptimal for?
Apparently we can
https://communities.vmware.com/docs/DOC-7983
http://markmail.org/thread/ttamcfb4d6azzbw7
On 1/21/14 2:46 PM, Hugo Trippaers trip...@gmail.com wrote:
Chiradeep,
Even on the generated sources nobody seems willing to state that it is ok
to include them at the moment. Otherwise
Q. Can I redistribute the VI SDK libraries and sample code?
A. You can redistribute only those parts of the SDK package that have been
designated as ³distributable code².
In VI SDK 2.5, the following components can be redistributed: vim.jar,
vim25.jar. To note developers typically generate web
Kelven, Chiradeep,
What license governs the redistribution, what do we include in our notice file
and is that license compatible with the ASF license policy?
Hugo
Sent from my iPhone
On 22 jan. 2014, at 00:44, Kelven Yang kelven.y...@citrix.com wrote:
Q. Can I redistribute the VI SDK
We are now again at the exact same point as where Darren was.
This is the legal ticket relevant to the license discussion:
https://issues.apache.org/jira/plugins/servlet/mobile#issue/LEGAL-180
Either we get an ok from legal or we need to find an alternative. Kelven,
Chiradeep, are you guys
I created https://issues.apache.org/jira/browse/LEGAL-180 for this.
Darren
Darren,
Any update on the vmware patch? Did you get the patch tested already? Would be
nice to get this in for the next release.
Cheers,
Hugo
On Sep 26, 2013, at 6:23 AM, David Nalley da...@gnsa.us wrote:
On Tue, Sep 24, 2013 at 8:01 PM, Alex Huang alex.hu...@citrix.com wrote:
Wow good
No update on this. I mentally got blocked on the emailing legal@
about it. Should I go ahead and email them? Whats the full email
address? From a technical perspective I know this will work, I did
some bytecode analysis and we can produce basically the exact same
thing as what's in the jar
On Wed, Oct 2, 2013 at 4:23 PM, Darren Shepherd
darren.s.sheph...@gmail.com wrote:
No update on this. I mentally got blocked on the emailing legal@
about it. Should I go ahead and email them? Whats the full email
address? From a technical perspective I know this will work, I did
some
On Tue, Sep 24, 2013 at 8:01 PM, Alex Huang alex.hu...@citrix.com wrote:
Wow good guess...Hugo had me scratching my head on that oneIs Prussian
some code name for Apache legalShould I askWould it make me look
stupid if I askedall sorts of doubts going through my mind.
--Alex
something with
VMware or
why something isn't working, I'd rather point them to the VMware
SDK
documentation than vijava. I would assume that there is going to
be more
information about the VMware library then there would be for
vijava
on
stackoverflow and google in general.
Google it, so far you
when it finally gets mature.
-Original Message-
From: Kelven Yang [mailto:kelven.y...@citrix.com]
Sent: Tuesday, September 24, 2013 11:59 AM
To: dev@cloudstack.apache.org
Subject: Re: VmWare SDK to vijava
We have commercial releases on top of existing code base and there are lots
-
From: Kelven Yang [mailto:kelven.y...@citrix.com]
Sent: Tuesday, September 24, 2013 11:59 AM
To: dev@cloudstack.apache.org
Subject: Re: VmWare SDK to vijava
We have commercial releases on top of existing code base and there are
lots of
testing efforts behind it, dramatic switch means
-
From: Kelven Yang [mailto:kelven.y...@citrix.com]
Sent: Tuesday, September 24, 2013 2:06 PM
To: dev@cloudstack.apache.org
Subject: Re: VmWare SDK to vijava
It is about the interface layer between CloudStack and VMware, Spring
can only
help to what it can, ultimately, we need to refactor
-
From: Kelven Yang [mailto:kelven.y...@citrix.com]
Sent: Tuesday, September 24, 2013 2:06 PM
To: dev@cloudstack.apache.org
Subject: Re: VmWare SDK to vijava
It is about the interface layer between CloudStack and VMware, Spring can
only help to what it can, ultimately, we need to refactor
@cloudstack.apache.org
Subject: Re: VmWare SDK to vijava
It is about the interface layer between CloudStack and VMware, Spring
can
only help to what it can, ultimately, we need to refactor the interface
layer to
take in vijava as one of its implementations.
We also need to consider of another situation
-Original Message-
From: Alex Huang [mailto:alex.hu...@citrix.com]
Sent: Tuesday, September 24, 2013 4:23 PM
To: dev@cloudstack.apache.org
Subject: RE: VmWare SDK to vijava
So this discussion took a big turn that I did not expect. I am very strongly
against creating a plugin
the help with the conversion process.
Additionally, if somebody wants to know how to do something with
VMware or
why something isn't working, I'd rather point them to the VMware
SDK
documentation than vijava. I would assume that there is going to
be more
information about the VMware library
On 9/24/13 4:54 PM, Alex Huang alex.hu...@citrix.com wrote:
-Original Message-
From: Alex Huang [mailto:alex.hu...@citrix.com]
Sent: Tuesday, September 24, 2013 4:23 PM
To: dev@cloudstack.apache.org
Subject: RE: VmWare SDK to vijava
So this discussion took a big turn that I did
the help with the conversion process.
Additionally, if somebody wants to know how to do something with
VMware or
why something isn't working, I'd rather point them to the VMware
SDK
documentation than vijava. I would assume that there is going
to
be more
information about the VMware
a bit
deeper and i could use the help with the conversion process.
Additionally, if somebody wants to know how to do something with
VMware or
why something isn't working, I'd rather point them to the VMware
SDK
documentation than vijava. I would assume that there is going to
be more
.
Additionally, if somebody wants to know how to do something with
VMware or
why something isn't working, I'd rather point them to the VMware
SDK
documentation than vijava. I would assume that there is going to
be more
information about the VMware library then there would be for
vijava
...@gmail.com]
Sent: Tuesday, September 24, 2013 6:07 PM
To: dev@cloudstack.apache.org
Cc: dev@cloudstack.apache.org
Subject: Re: VmWare SDK to vijava
My extensive testing consisted of it compiles! So somebody needs to
validate it, I don't have a vmware setup handy. The wsdl generation route
of vijava. I'd say dig a
bit
deeper and i could use the help with the conversion process.
Additionally, if somebody wants to know how to do something
with
VMware or
why something isn't working, I'd rather point them to the
VMware
SDK
documentation than vijava. I would assume that there is
going
the help with the conversion process.
Additionally, if somebody wants to know how to do something
with
VMware or
why something isn't working, I'd rather point them to the
VMware
SDK
documentation than vijava. I would assume that there is
going to
be more
information about the VMware library
, I'd rather point them to the
VMware
SDK
documentation than vijava. I would assume that there is
going to
be more
information about the VMware library then there would be for
vijava
on
stackoverflow and google in general.
Google it, so far you are right, but java projects
...@citrix.com]
Sent: Tuesday, September 24, 2013 7:01 PM
To: dev@cloudstack.apache.org
Subject: Re: VmWare SDK to vijava
Ha! Prussians == Prasanna?
Godawful autocorrect.
On 9/24/13 6:47 PM, Hugo Trippaers trip...@gmail.com wrote:
Darren, you can probably work with Prussians to get
wants to know how to do something with VMware or
why something isn't working, I'd rather point them to the VMware SDK
documentation than vijava. I would assume that there is going to be more
information about the VMware library then there would be for vijava on
stackoverflow and google
with VMware or
why something isn't working, I'd rather point them to the VMware SDK
documentation than vijava. I would assume that there is going to be more
information about the VMware library then there would be for vijava on
stackoverflow and google in general.
Google it, so far you
When I upgraded vmware sdk from 4.x to 5.1 before, I looked into the build
script used by Vmware published SDK. It seems that besides normal jawxs
generated client stubs from wsdl, Vmware sdk published build script has
another post processing done on VimService.java class generated. The post
How'd you know about the post processing? I generated the stubs and it compile
perfectly and ACS compile against the stubs too. I have no clue if it work as
I never ran it though. One thing I ran into was that you had to generate for
jaxws 2.1.
Darren
On Sep 23, 2013, at 11:25 AM, Min
This is the code snippet from the build.sh bundled with Vmware SDK:
if [ x${1} != x-w ]
then
echo Generating vim25 stubs from wsdl
if [ -d com/vmware/vim25 ]
then
rm -rf com/vmware/vim25
fi
mkdir -p com/vmware/vim25
cp -f ../../../wsdl/vim25/*.* com/vmware/vim25/
with
VMware or
why something isn't working, I'd rather point them to the VMware SDK
documentation than vijava. I would assume that there is going to
be more
information about the VMware library then there would be for vijava
on
stackoverflow and google in general.
Google it, so far you
working, I'd rather point them to the VMware SDK
documentation than vijava. I would assume that there is going to
be more
information about the VMware library then there would be for vijava
on
stackoverflow and google in general.
Google it, so far you are right, but java projects are switching
I was looking at the vmware jar and realized it's just a jaxws generated
client stubs. I'm sure this has been discussed before, so I'm curious why
we can't just download the wsdl and generate the stubs ourselves? I assume
we can't distribute the wsdl's, so we can just check in the java code
Hey Darren,
There is actually just a bit more to the vijava library than just processing
the wsdl. It simplifies some of the weirder parts of the vmware sdk. And in
general it seems a well maintained piece of code. I'd rather use that that have
to keep another set of bindings in sync with the
xml/soap framework one guy wrote.
Additionally, if somebody wants to know how to do something with VMware or
why something isn't working, I'd rather point them to the VMware SDK
documentation than vijava. I would assume that there is going to be more
information about the VMware library
.
Additionally, if somebody wants to know how to do something with VMware or
why something isn't working, I'd rather point them to the VMware SDK
documentation than vijava. I would assume that there is going to be more
information about the VMware library then there would be for vijava
is replaced by 20-something lines of
vijava. I'd say dig a bit deeper and i could use the help with the conversion
process.
Additionally, if somebody wants to know how to do something with VMware or
why something isn't working, I'd rather point them to the VMware SDK
documentation than
59 matches
Mail list logo
