Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [osbea-wg] Participation Request

Hi Chris,

That's really great! Congratulations again for the willingness to start and drive such an initiative!

I will not be able to join this time in Stuttgart on-site, but would be very happy, if I could join remotely via Skype, Zoom or any other or at least to see a recording of the meeting afterwards if it is possible.

I would like to contact you directly to discuss this in more details, because you gave answers below, which raised much more questions from my side __
Is it fine for you?


On 12.05.18, 8:59, "osbea-wg-bounces@xxxxxxxxxxx" <osbea-wg-bounces@xxxxxxxxxxx> wrote:

    Hi Nidelcho,
    thank you for enrolling on the OS.bea mailing list. 
    Well, I (we) also assume that there should be some common integration points. Reading your mail, I guess that you might have some questions on how OSBP, the platform the OS.bea working group is supporting, is designed. I hope that after the following lines of explanation you will find your questions answered and it will give you an overview of what can be done with the OSB platform, but if not just ask you questions and we will give more answers... 
    One of the main objectives of the OS.bea is to help OSBP to integrate as many as possible helpful frameworks and to target any platforms required as well as to make industry specific functionalities available to enable the generation of software in as many industries as possible with a minimum of effort. A minimum of effort for us means that depending on the domain in which software shall be implemented we prefer either no-code (visual), low-code (DSL-based) or traditional tools, depending on what is optimal. If traditional software development e.g. in Java is necessary we normally wrap the developed functionality in no- or low-code tools, so the next time it is used the effort needed is minimized.
    To answer your question about the backend: we, for the moment, use Jetty as backend, but any other shall also work and if not we will make it work. 
    Regarding the present tooling part I recommend to read the following link: and, yes, all tools are integrated, so that they can be used within Eclipse's IDE. 
    You might have read at the end of the following link that the working group will meet in Stuttgart, Germany (not far away from you HQ) on 6th of June. Until know the OSB platform has been driven by end-users requests and we would also love to integrate participants which can contribute technical aspects. So, if you have any idea who could participate, contribute, give us any suggestions or hints let us know. 
    Feel free to ask any further question. We will keep you updated via the OS.bea mailing list.
    Have nice week-end.
    -----Ursprüngliche Nachricht-----
    Von: osbea-wg-bounces@xxxxxxxxxxx [mailto:osbea-wg-bounces@xxxxxxxxxxx] Im Auftrag von Delchev, Nedelcho
    Gesendet: Freitag, 11. Mai 2018 21:23
    An: osbea-wg@xxxxxxxxxxx
    Betreff: [osbea-wg] Participation Request
    Dear OS.bea Members,
    This initiative sounds very interesting for us as soon as Eclipse Dirigible is targeting exactly what is defined below – “a no-code and low-code full-stack business and enterprise application development platform based on open source technologies”.
    I assume that the main target here for the tooling part is Eclipse IDE (EMF,GEF, etc.) and for the application server probably Jakarta EE implementation (or any other Java based backend – Jetty, Tomcat, Vertx?), but probably we can find a lots of integration points and/or standardized approaches for building the business applications. Hence, you can count Eclipse Dirigible (and me personally) as an interesting party for this working group.
    osbea-wg mailing list
    To change your delivery options, retrieve your password, or unsubscribe from this list, visit
    osbea-wg mailing list
    To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Back to the top