Are Java actions first class citizens?

[Minto van der Sluis]

Hi,

I have been scratching the surface of Openwhisk and I like it a lot. But 
since Java is the eco system (language + tooling) I am most comfortable 
with, I would like to create my actions in java. Luckily Openwhisk 
supports Java.


Unfortunately diving a bit deeper somehow gives me the impression that 
Java is not really a first class citizen. Why do I get this impression? 
There are a number of reasons:


1) Examples

I can hardly find any decent Java based examples beyond hello world. In 
particular how to invoke other actions from within a Java action.


Seaching on Github with "Openwhisk java" results in only 4 projects :-( 
and one of them is mine (see 2)


2) Openwhisk java client API

Searching for Openwhisk client libraries results in libraries for 
javascript, swift, go and python. Unfortunately none for java. There is 
however a feature request: 
https://github.com/apache/incubator-openwhisk/issues/2466


I had a little go at it myself. The API is mostly generated from the 
swagger file. Unfortunately the Swagger code generator generates 
unusable code for one the most important data structures, KeyValue.


My Openwhisk Java API can be found at: 
https://github.com/misl/openwhisk-client-java


Yes it desperately needs some additional documentation, but first I want 
to fix the KeyValue issue. And example of using the library from outside 
openwhisk can be found in the code at: 
https://github.com/misl/openwhisk-client-java/blob/master/openwhisk-api-client-retrofit/src/test/java/SimpleTest.java


3) Fully qualified method name does not work for Java action handlers 
(see: wsk action create --main)


For this I already created an issue: 
https://github.com/apache/incubator-openwhisk/issues/2590


I even tried solving this one myself, have a look at my fork at: 
https://github.com/misl/incubator-openwhisk


Fixing the issue was easy, but testing it seems to be much more complex. 
Maybe I need a little help here to be able to complete this one.



All this gives me the impression that the focus for Openwhisk is on a 
lot of languages but not on Java. Or am I totally wrong here?


Please share your thoughts.

Kind regards,

misl

PS 1: For the interested I might have another project worth taking a 
look at. Openwhisk Package and Action annotations - 
https://github.com/misl/xup-openwhisk-annotations . It includes a script 
to quickly upload the generated Jar file. This one is also still needs 
documentation, but to see how it works have a look at the examples.


PS 2: Oh by the way, If any of these projects are of interest, I am 
willing to donate.

Tech Interchange Agenda and Volunteer

[Carlos Santana]

Our next meeting is this Wednesday

What Items you want to be discuss or watch demo of?


I'm feeling sick this week, it must be the weather change or something.

Can someone lead the meeting Wednesday? I might not attend depending how I
feel by then.


--Carlos

Re: Podling Report Reminder - September 2017

[Matt Rutkowski]

Hi John and Sergio,

I posted a draft report on our CWIKI (started Friday).  Could you help me 
post it (belatedly) with the other podling reports?

Here is the link: 
https://cwiki.apache.org/confluence/display/OPENWHISK/2017+September

Kind regards,
Matt 




From:   "John D. Ament" 
To: 
Date:   09/10/2017 07:43 PM
Subject:Re: Podling Report Reminder - September 2017



Sergio,

I'm a bit surprised that no one stepped up to do OpenWhisk's report, 
considering the on list activity.  Who has done them in the past?

John

On 2017-09-07 20:46, Sergio Fernández  wrote: 
> nobody? deadline is already over!
> 
> On Sep 7, 2017 06:45, "Sergio Fernández"  wrote:
> 
> > volunteer?
> >
> > On Sep 5, 2017 18:40,  wrote:
> >
> >> Dear podling,
> >>
> >> This email was sent by an automated system on behalf of the Apache
> >> Incubator PMC. It is an initial reminder to give you plenty of time 
to
> >> prepare your quarterly board report.
> >>
> >> The board meeting is scheduled for Wed, 20 September 2017, 10:30 am 
PDT.
> >> The report for your podling will form a part of the Incubator PMC
> >> report. The Incubator PMC requires your report to be submitted 2 
weeks
> >> before the board meeting, to allow sufficient time for review and
> >> submission (Wed, September 06).
> >>
> >> Please submit your report with sufficient time to allow the Incubator
> >> PMC, and subsequently board members to review and digest. Again, the
> >> very latest you should submit your report is 2 weeks prior to the 
board
> >> meeting.
> >>
> >> Thanks,
> >>
> >> The Apache Incubator PMC
> >>
> >> Submitting your Report
> >>
> >> --
> >>
> >> Your report should contain the following:
> >>
> >> *   Your project name
> >> *   A brief description of your project, which assumes no knowledge 
of
> >> the project or necessarily of its field
> >> *   A list of the three most important issues to address in the move
> >> towards graduation.
> >> *   Any issues that the Incubator PMC or ASF Board might wish/need to 
be
> >> aware of
> >> *   How has the community developed since the last report
> >> *   How has the project developed since the last report.
> >> *   How does the podling rate their own maturity.
> >>
> >> This should be appended to the Incubator Wiki page at:
> >>
> >> 
https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.apache.org_incubator_September2017=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=6zQLM7Gc0Sv1iwayKOKa4_SFxRIxS478q2gZlAJj4Zw=DEqKgS77wu0-phlKn7c4im2YsVZkq3Jm3HZTCIr_6Ec=QiCez8UveYmU4mj_PFhkn3KbX0yHHdVUTn7ugGuAJh0=
 

> >>
> >> Note: This is manually populated. You may need to wait a little 
before
> >> this page is created from a template.
> >>
> >> Mentors
> >> ---
> >>
> >> Mentors should review reports for their project(s) and sign them off 
on
> >> the Incubator wiki page. Signing off reports shows that you are
> >> following the project - projects that are not signed may raise alarms
> >> for the Incubator PMC.
> >>
> >> Incubator PMC
> >>
> >
>