Re: MD files or adoc files.

[Alex Soto]

Yes, and there is a converter in Asciidoctor page that does for you
automatically

El jue., 27 dic. 2018 13:43, Puneeth PS  escribió:

> Hi,
>
> I am using md as the file format for documentation and I recently saw a
> task wherein migration to adoc format is happening, is adoc the preferred
> format for documentation? If so should I start converting md files to adoc?
>
> Regards,
> Puneeth
>

Re: JUnit5 Jupiter support with Arquillian

[Alex Soto]

No, it is not supported.

Missatge de Bruno Baptista  del dia dl., 11 de març
2019 a les 19:28:

> Hi Jean-Louis,
>
> I'm hacking a comparison between multiple frameworks and all apart from
> Arquillian seem to support JUnit 5 already.
>
> I was hopping to be missing something, but it seems it's not supported yet.
>
> Cheers
>
> Bruno Baptista
> https://twitter.com/brunobat_
>
>
> On 11/03/19 18:22, Jean-Louis Monteiro wrote:
> > Hey Bruno,
> >
> > I don't know and did not try yet.
> > What does it bring out of curiosity?
> > --
> > Jean-Louis Monteiro
> > http://twitter.com/jlouismonteiro
> > http://www.tomitribe.com
> >
> >
> > On Mon, Mar 11, 2019 at 7:15 PM Bruno Baptista 
> wrote:
> >
> >> Hi Folks,
> >>
> >> Any idea if we can run tests using the Jupiter engine of JUnit 5 with
> >> Arquillian on TomEE?
> >>
> >> Has anyone tried it?
> >>
> >> Cheers
> >>
> >> --
> >> Bruno Baptista
> >> https://twitter.com/brunobat_
> >>
> >>
> >>
>


-- 
+--+
  Alex Soto Bueno - Computer Engineer
  www.lordofthejars.com
+--+

TomEE and database multitenancy

[Alex Soto]

Hi guys, as I mention on the twitter, currently I am developing a PoC for
solving the problem of multi-tenancy with schema-based approach. This means
that for each tenant has its own schema inside database. Moreover the same
approach can be used just in case of database-based approach.

Another of the requirements we are having in my company is that a tenant
should any tenant should be able to be added dynamically, without having to
stop the server.

To implement this in TomEE I have implemented my own Router. Of course it
is a PoC so some parts needs more validations and/or some refactor, but I
think that as first approach to see the idea is enough.
You can see the code here: https://github.com/lordofthejars/multi

I think that TomEE could provide this feature out of the box, it is really
not so hard and with the inclusion of CDI you will see that it is pretty
simple.
This email is only to open the discussion about if it is interesting to add
it in TomEE or not.

My next steps will be present the solution to my teams, and after some
discussions, implement it as final solution (which I am sure we will be
able if you agree to implement it as module inside TomEE).

And that's all, for any question about the PoC feel free to ask it.

Alex.

Re: TomEE and database multitenancy

[Alex Soto]

>  wonder if it couldnt reuse ImportSql class and just use a well know file

Sure, but this is just only an example. In fact in our production
environment it won't be as easier as this. Probably there will be a person
who pushes the button of "create the schema".

> I'd add few more things like the name of the id of theresource

Sure this is only a basic class.

> why not using a request scope bean

Don't catch you about this hehehe. You mean NewTenantListener scope, or add
a @RequestScope for TenantId instead of setting it?

> Note that the thread local should be clean up

So true I have implemented it.

> provide your own API and hide internals behind something

Had this on mind, but to not complicate now the example I decided to reuse
existing classes.

> replace CDI by an extension

When you say replace CDI you mean only for registration or also the CDI
annotations used like @Inject or Observers?

Alex.

El dj., 4 juny 2015 a les 16:45, Romain Manni-Bucau ()
va escriure:

> Hi
>
> few notes but this looks a super great start:
> -
>
> https://github.com/lordofthejars/multi/blob/master/src/main/java/com/scytl/multi/CreateDatabaseSchemaListener.java
> :
> wonder if it couldnt reuse ImportSql class and just use a well know file
> -
>
> https://github.com/lordofthejars/multi/blob/master/src/main/java/com/scytl/multi/CreatedDataSourceEvent.java
> :
> I'd add few more things like the name of the id of theresource
> (logging/audit purpose)
> -
>
> https://github.com/lordofthejars/multi/blob/master/src/main/java/com/scytl/multi/MultitenancyRouter.java
> :
> why not using a request scope bean? would make the code simpler for webapps
> (but wouldnt support batches/async). Note that the thread local should be
> clean up otherwise it will leak or can have side effect if you reuse an old
> value (better to fail if you forget to set it than using previous customer
> datasource)
> - I would probably get rid of org.apache.openejb imports in events (provide
> your own API and hide internals behind something)
>
> Now the issues to bring it in tomee would surely be to:
> - have a flag in application.properties to switch it on
> - replace CDI by an extension (with the META-INF/service registration but
> the flag will add it or not) to ensure it works even if the container jar
> is not scanned
>
> Nothing blocking but a small rework to do
>
> wdyt?
>
>
>
>
> Romain Manni-Bucau
> @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> <http://rmannibucau.wordpress.com> | Github <
> https://github.com/rmannibucau> |
> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
> <http://www.tomitribe.com>
>
> 2015-06-04 16:32 GMT+02:00 Alex Soto :
>
> > Hi guys, as I mention on the twitter, currently I am developing a PoC for
> > solving the problem of multi-tenancy with schema-based approach. This
> means
> > that for each tenant has its own schema inside database. Moreover the
> same
> > approach can be used just in case of database-based approach.
> >
> > Another of the requirements we are having in my company is that a tenant
> > should any tenant should be able to be added dynamically, without having
> to
> > stop the server.
> >
> > To implement this in TomEE I have implemented my own Router. Of course it
> > is a PoC so some parts needs more validations and/or some refactor, but I
> > think that as first approach to see the idea is enough.
> > You can see the code here: https://github.com/lordofthejars/multi
> >
> > I think that TomEE could provide this feature out of the box, it is
> really
> > not so hard and with the inclusion of CDI you will see that it is pretty
> > simple.
> > This email is only to open the discussion about if it is interesting to
> add
> > it in TomEE or not.
> >
> > My next steps will be present the solution to my teams, and after some
> > discussions, implement it as final solution (which I am sure we will be
> > able if you agree to implement it as module inside TomEE).
> >
> > And that's all, for any question about the PoC feel free to ask it.
> >
> > Alex.
> >
>

Re: DISCUSS: Milestone of TomEE 7

[Alex Soto]

Hello,
in my company we are currently waiting for five things.

The first one is JAXRS 2 asynchronous management.
The second one using bean validation in JAXRS methods (it can be done in
TomEE 1.7 by using a system property)
The third one concurrency utils to be able to access a pool of executors
The fourth the JSON-P spec.
And last although not sure the Batch capabilities.

If we get this from next milestone, then we will be able to start playing a
bit with it.

Alex.



El dc., 10 juny 2015 a les 7:33, Andy Gumbrecht ()
va escriure:

> I took a branch at the very last green build already. So, yes.
>
> http://www.tomitribe.com - @AndyGeeDe - On a small screen device.
> On 10 Jun 2015 05:47, "David Blevins"  wrote:
>
> > Should we finally cut this?  Doesn't have to be perfect, but the movement
> > would be welcomed I think.
> >
> > We've been contemplating a milestone for quite a while now.
> >
> > Many of us will be together at DevoxxUK next week.  If this is something
> > the community wants, we could hack on it.
> >
> > Thoughts?
> >
> >
> > --
> > David Blevins
> > http://twitter.com/dblevins
> > http://www.tomitribe.com
> >
> >
>

Re: DISCUSS: Milestone of TomEE 7

[Alex Soto]

I know that we can do this by ourselves, in fact we are adding JSON-P as
external dependency.

El dc., 10 juny 2015 a les 10:04, Romain Manni-Bucau ()
va escriure:

> 2015-06-10 10:01 GMT+02:00 Alex Soto :
>
> > Hello,
> > in my company we are currently waiting for five things.
> >
> > The first one is JAXRS 2 asynchronous management.
> > The second one using bean validation in JAXRS methods (it can be done in
> > TomEE 1.7 by using a system property)
> > The third one concurrency utils to be able to access a pool of executors
> > The fourth the JSON-P spec.
> > And last although not sure the Batch capabilities.
> >
> > If we get this from next milestone, then we will be able to start
> playing a
> > bit with it.
> >
> >
> will be :)
>
> side note: JBatch and JSON-P are usable in 1.x adding the right libs. Other
> ones are a bit more complicated.
>
>
> > Alex.
> >
> >
> >
> > El dc., 10 juny 2015 a les 7:33, Andy Gumbrecht (<
> agumbre...@tomitribe.com
> > >)
> > va escriure:
> >
> > > I took a branch at the very last green build already. So, yes.
> > >
> > > http://www.tomitribe.com - @AndyGeeDe - On a small screen device.
> > > On 10 Jun 2015 05:47, "David Blevins"  wrote:
> > >
> > > > Should we finally cut this?  Doesn't have to be perfect, but the
> > movement
> > > > would be welcomed I think.
> > > >
> > > > We've been contemplating a milestone for quite a while now.
> > > >
> > > > Many of us will be together at DevoxxUK next week.  If this is
> > something
> > > > the community wants, we could hack on it.
> > > >
> > > > Thoughts?
> > > >
> > > >
> > > > --
> > > > David Blevins
> > > > http://twitter.com/dblevins
> > > > http://www.tomitribe.com
> > > >
> > > >
> > >
> >
>

AbstractService properties immutable

[Alex Soto]

Hi, currently I am developing an application which I am registering
dynamically resources using Assembler class.

I have seen that AbstractService has a field called properties that you can
only get information from it but not set it. All other fields has its own
getter/setter except this one. I think that if there is nothing against it
it should have a setter too so I can dynamically set properties too.

The class is here:
https://github.com/apache/tomee/blob/master/container/openejb-core/src/main/java/org/apache/openejb/config/sys/AbstractService.java

I can provide a PR if you agree.

Alex.

Re: AbstractService properties immutable

[Alex Soto]

Yes but it is a bit antinatural if all other methods follows the
getter/setter, maybe a setter and an append methid in case of properties
could have more sense.

El dc., 17 juny 2015 a les 11:16, Romain Manni-Bucau ()
va escriure:

> Not sure i got it. You use getProperties to mutate it
>  Le 17 juin 2015 10:01, "Alex Soto"  a écrit :
>
> > Hi, currently I am developing an application which I am registering
> > dynamically resources using Assembler class.
> >
> > I have seen that AbstractService has a field called properties that you
> can
> > only get information from it but not set it. All other fields has its own
> > getter/setter except this one. I think that if there is nothing against
> it
> > it should have a setter too so I can dynamically set properties too.
> >
> > The class is here:
> >
> >
> https://github.com/apache/tomee/blob/master/container/openejb-core/src/main/java/org/apache/openejb/config/sys/AbstractService.java
> >
> > I can provide a PR if you agree.
> >
> > Alex.
> >
>

Re: AbstractService properties immutable

[Alex Soto]

Yes, but as you said consistent with jaxb tree but what's happening if you
want to use it as simple POJO for dynamic registration? Well it was only a
suggestion, of course it is not blocker.



El dc., 17 juny 2015 a les 11:25, Romain Manni-Bucau ()
va escriure:

> Yes and no. It is javadoc-ed and consistent in our "jaxb tree".
>  Le 17 juin 2015 10:19, "Alex Soto"  a écrit :
>
> > Yes but it is a bit antinatural if all other methods follows the
> > getter/setter, maybe a setter and an append methid in case of properties
> > could have more sense.
> >
> > El dc., 17 juny 2015 a les 11:16, Romain Manni-Bucau (<
> > rmannibu...@gmail.com>)
> > va escriure:
> >
> > > Not sure i got it. You use getProperties to mutate it
> > >  Le 17 juin 2015 10:01, "Alex Soto"  a écrit :
> > >
> > > > Hi, currently I am developing an application which I am registering
> > > > dynamically resources using Assembler class.
> > > >
> > > > I have seen that AbstractService has a field called properties that
> you
> > > can
> > > > only get information from it but not set it. All other fields has its
> > own
> > > > getter/setter except this one. I think that if there is nothing
> against
> > > it
> > > > it should have a setter too so I can dynamically set properties too.
> > > >
> > > > The class is here:
> > > >
> > > >
> > >
> >
> https://github.com/apache/tomee/blob/master/container/openejb-core/src/main/java/org/apache/openejb/config/sys/AbstractService.java
> > > >
> > > > I can provide a PR if you agree.
> > > >
> > > > Alex.
> > > >
> > >
> >
>

Re: AbstractService properties immutable

[Alex Soto]

Ok, no worries, for now this is ok

El dc., 17 juny 2015 a les 11:34, Romain Manni-Bucau ()
va escriure:

> 2015-06-17 11:27 GMT+02:00 Alex Soto :
>
> > Yes, but as you said consistent with jaxb tree but what's happening if
> you
> > want to use it as simple POJO for dynamic registration? Well it was only
> a
> > suggestion, of course it is not blocker.
> >
> >
> sure but that's the common pattern for collections. Setters are fine for
> single valued fields IMO, optional for others.
>
> A builder would be better than a setter IMO. Think David started few things
> about it butwe never finished the API AFAIK.
>
>
> >
> >
> > El dc., 17 juny 2015 a les 11:25, Romain Manni-Bucau (<
> > rmannibu...@gmail.com>)
> > va escriure:
> >
> > > Yes and no. It is javadoc-ed and consistent in our "jaxb tree".
> > >  Le 17 juin 2015 10:19, "Alex Soto"  a écrit :
> > >
> > > > Yes but it is a bit antinatural if all other methods follows the
> > > > getter/setter, maybe a setter and an append methid in case of
> > properties
> > > > could have more sense.
> > > >
> > > > El dc., 17 juny 2015 a les 11:16, Romain Manni-Bucau (<
> > > > rmannibu...@gmail.com>)
> > > > va escriure:
> > > >
> > > > > Not sure i got it. You use getProperties to mutate it
> > > > >  Le 17 juin 2015 10:01, "Alex Soto"  a écrit :
> > > > >
> > > > > > Hi, currently I am developing an application which I am
> registering
> > > > > > dynamically resources using Assembler class.
> > > > > >
> > > > > > I have seen that AbstractService has a field called properties
> that
> > > you
> > > > > can
> > > > > > only get information from it but not set it. All other fields has
> > its
> > > > own
> > > > > > getter/setter except this one. I think that if there is nothing
> > > against
> > > > > it
> > > > > > it should have a setter too so I can dynamically set properties
> > too.
> > > > > >
> > > > > > The class is here:
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://github.com/apache/tomee/blob/master/container/openejb-core/src/main/java/org/apache/openejb/config/sys/AbstractService.java
> > > > > >
> > > > > > I can provide a PR if you agree.
> > > > > >
> > > > > > Alex.
> > > > > >
> > > > >
> > > >
> > >
> >
>

Re: AbstractService properties immutable

[Alex Soto]

Yes I was thinking the same as Romain. But please I can be wrong, this is
something that I have noticed today when I tried to generate and register
resources dynamically instead of loading in static way from resources.xml

Alex.

El dc., 17 juny 2015 a les 18:17, Romain Manni-Bucau ()
va escriure:

> well even if that is no more strictly true (we rewrap for several cases it
> in super properties) we could still wrap the properties in the setter
>
>
> Romain Manni-Bucau
> @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> <http://rmannibucau.wordpress.com> | Github <
> https://github.com/rmannibucau> |
> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
> <http://www.tomitribe.com>
>
> 2015-06-17 18:12 GMT+02:00 David Blevins :
>
> > Hi Alex!
> >
> > The motivation there is slightly more than philosophical.  The properties
> > in AbstractService is actually not the standard java.util.Properties, but
> > rather an implementation which is case-insensitive.  The library we use
> to
> > construct the services themselves, xbean-reflect, is also setup to use
> > case-insensitive object attributes.
> >
> > If we were to add a setProperties method, we'd have to in some way ensure
> > it has the same feature or pull all the properties out and move them in.
> >
> >
> > --
> > David Blevins
> > http://twitter.com/dblevins
> > http://www.tomitribe.com
> >
> > On Jun 17, 2015, at 10:00 AM, Alex Soto  wrote:
> >
> > > Hi, currently I am developing an application which I am registering
> > > dynamically resources using Assembler class.
> > >
> > > I have seen that AbstractService has a field called properties that you
> > can
> > > only get information from it but not set it. All other fields has its
> own
> > > getter/setter except this one. I think that if there is nothing against
> > it
> > > it should have a setter too so I can dynamically set properties too.
> > >
> > > The class is here:
> > >
> >
> https://github.com/apache/tomee/blob/master/container/openejb-core/src/main/java/org/apache/openejb/config/sys/AbstractService.java
> > >
> > > I can provide a PR if you agree.
> > >
> > > Alex.
> >
> >
>

Apache TomEE official image

[Alex Soto]

Hi mates I have been working on creating a TomEE image in Docker.
I am closely to be able to release an Apache TomEE official repository on
docker hub, but I prefer you take a look first.

First of all I have decided to change from official openjdk image which is
based on debian, to official Alpine image. This change is pretty simple,
the Alpine docker image is a light docker image (only 5MB) and following
the philosophy of TomEE of light yet powerful distribution, I think this is
a really good movement in these terms. Now the TomEE Docker image is 200MB
less than the one using Debian. Concretely 191MB in front of 379MB.

Let me share with you the Dockerfile content:

FROM alpine:3.2

RUN apk --update add bash
RUN apk --update add curl
RUN apk --update add openjdk7
RUN apk --update add gnupg

# add our user and group first to make sure their IDs get assigned
consistently, regardless of whatever dependencies get added
RUN addgroup -S tomee && adduser -S -G tomee tomee

ENV PATH /usr/local/tomee/bin:$PATH
RUN mkdir -p /usr/local/tomee
RUN chown tomee:tomee /usr/local/tomee
WORKDIR /usr/local/tomee
USER tomee

RUN curl -SL http://www.apache.org/dist/tomee/KEYS -o KEYS \
&& gpg --import KEYS

RUN curl -SL
https://dist.apache.org/repos/dist/release/tomee/tomee-1.7.2/apache-tomee-1.7.2-webprofile.tar.gz.asc
-o
tomee.tar.gz.asc

RUN curl -SL
http://apache.rediris.es/tomee/tomee-1.7.2/apache-tomee-1.7.2-webprofile.tar.gz
-o
tomee.tar.gz \
&& tar -zxvf tomee.tar.gz  \
&& gpg --verify tomee.tar.gz.asc tomee.tar.gz \
&& mv apache-tomee-webprofile-1.7.2/* /usr/local/tomee \
&& rm -Rf apache-tomee-plus-1.7.2 \
&& rm bin/*.bat \
&& rm tomee.tar.gz*

EXPOSE 8080
CMD ["catalina.sh", "run"]

But it has two drawback is that alpine 3.2 still don't have support in APK
for openjdk8, but it will be added for alpine 3.3 so I am quite confident
that the best way to proceed is wait until it is released and then update
our Dockerfile and finally release our image as official image with
OpenJDK8.

The second problem is that we are setting alpine linux as default image in
our distribution and not a more popular like Debian.

Another message I have seen while creating the image was this one:

gpg: Signature made Sun May 17 22:18:30 2015 UTC using DSA key ID D297D428
gpg: Good signature from "Jonathan Gallimore "
[unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg:  There is no indication that the signature belongs to the
owner.
Primary key fingerprint: DBCC D103 B8B2 4F86 FFAA  B025 C8BB 472C D297 D428

I don't know if Jonathan's key was not created by a trusted key.

Well that's all, let me know what you think about this change or what you
would like to see in official TomEE image.

Alex.

Re: [VOTE] OpenEJB 7.0.0-M1/TomEE 7.0.0-M1 (staging-1052)

[Alex Soto]

Take care Andy, cool as soon as TomEE7 M1 is released I will update Docker
image too.

El ds., 20 juny 2015 a les 22:06, Andy Gumbrecht ()
va escriure:

> Hi all,
>
> As you know, some of us had a busy but truly fantastic week at DevoxxUK.
> Everyone will need some R&R once getting home. We'd still like carry on
> with the vote and push this through. I'll clean up all the minor issues and
> most definitely roll another in a few weeks.
>
> Take care, have a quiet Sunday. I'll do the tally on Monday.
>
> Andy.
>
> http://www.tomitribe.com - @AndyGeeDe - On a small screen device.
> On 18 Jun 2015 08:28, "Romain Manni-Bucau"  wrote:
>
> > 2015-06-18 8:46 GMT+02:00 Mark Struberg :
> >
> > > Nontheless a
> > >
> > > +1
> > >
> > > from me.
> > >
> > > All the smallish issues mentioned can easily be fixed in the next
> > release.
> > > But it is REALLY important to get something out of the door.
> > >
> > > LieGrue,
> > > strub
> > >
> > >
> > >
> > > > Am 18.06.2015 um 08:44 schrieb Mark Struberg :
> > > >
> > > > Well he could. Just adding the staging repo would have done the
> trick.
> > > >
> > > > Otoh owb-1.6.1 is perfectly compatible to 1.6.0 thus it is a drop-in
> > > replacement.
> > > > If you use the tomee-maven-plugin then simply add it via .
> > > > If you use TomEE standalone then just replace the jars in the ./lib
> > > folder.
> > > >
> > >
> >
> > Just as a side note:
> >
> > all these solutions are irrelevant for a release Mark, it is like saying
> > "yes there is a bug but you can rebuild it yourself from trunk"
> >
> > repackaging the server is (still) rarely fine
> >
> >
> > > > LieGrue,
> > > > strub
> > > >
> > > >> Am 18.06.2015 um 00:35 schrieb Jean-Louis Monteiro <
> > > jlmonte...@tomitribe.com>:
> > > >>
> > > >>
> > > >> as you mentioned, OWB 1.6.1 hasn't been released so Andy could not
> > > embed it.
> > > >> It's a milestone so no issue so far in my opinion
> > > >
> > >
> > >
> >
>

Re: Apache TomEE official image

[Alex Soto]

Thanks well I am still not 100% happy, what I am wondering is if debian
image or alpine image. I m hesitant about this :)

El dl., 22 juny 2015 a les 23:23, Jean-Louis Monteiro (<
jlmonte...@tomitribe.com>) va escriure:

> This is awesome Alex.
> Thanks for driving this from start to end.
>
> Really great contribution.
>
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
> On Thu, Jun 18, 2015 at 11:03 AM, Alex Soto  wrote:
>
> > Hi mates I have been working on creating a TomEE image in Docker.
> > I am closely to be able to release an Apache TomEE official repository on
> > docker hub, but I prefer you take a look first.
> >
> > First of all I have decided to change from official openjdk image which
> is
> > based on debian, to official Alpine image. This change is pretty simple,
> > the Alpine docker image is a light docker image (only 5MB) and following
> > the philosophy of TomEE of light yet powerful distribution, I think this
> is
> > a really good movement in these terms. Now the TomEE Docker image is
> 200MB
> > less than the one using Debian. Concretely 191MB in front of 379MB.
> >
> > Let me share with you the Dockerfile content:
> >
> > FROM alpine:3.2
> >
> > RUN apk --update add bash
> > RUN apk --update add curl
> > RUN apk --update add openjdk7
> > RUN apk --update add gnupg
> >
> > # add our user and group first to make sure their IDs get assigned
> > consistently, regardless of whatever dependencies get added
> > RUN addgroup -S tomee && adduser -S -G tomee tomee
> >
> > ENV PATH /usr/local/tomee/bin:$PATH
> > RUN mkdir -p /usr/local/tomee
> > RUN chown tomee:tomee /usr/local/tomee
> > WORKDIR /usr/local/tomee
> > USER tomee
> >
> > RUN curl -SL http://www.apache.org/dist/tomee/KEYS -o KEYS \
> > && gpg --import KEYS
> >
> > RUN curl -SL
> >
> >
> https://dist.apache.org/repos/dist/release/tomee/tomee-1.7.2/apache-tomee-1.7.2-webprofile.tar.gz.asc
> > -o
> > tomee.tar.gz.asc
> >
> > RUN curl -SL
> >
> >
> http://apache.rediris.es/tomee/tomee-1.7.2/apache-tomee-1.7.2-webprofile.tar.gz
> > -o
> > tomee.tar.gz \
> > && tar -zxvf tomee.tar.gz  \
> > && gpg --verify tomee.tar.gz.asc tomee.tar.gz \
> > && mv apache-tomee-webprofile-1.7.2/* /usr/local/tomee \
> > && rm -Rf apache-tomee-plus-1.7.2 \
> > && rm bin/*.bat \
> > && rm tomee.tar.gz*
> >
> > EXPOSE 8080
> > CMD ["catalina.sh", "run"]
> >
> > But it has two drawback is that alpine 3.2 still don't have support in
> APK
> > for openjdk8, but it will be added for alpine 3.3 so I am quite confident
> > that the best way to proceed is wait until it is released and then update
> > our Dockerfile and finally release our image as official image with
> > OpenJDK8.
> >
> > The second problem is that we are setting alpine linux as default image
> in
> > our distribution and not a more popular like Debian.
> >
> > Another message I have seen while creating the image was this one:
> >
> > gpg: Signature made Sun May 17 22:18:30 2015 UTC using DSA key ID
> D297D428
> > gpg: Good signature from "Jonathan Gallimore "
> > [unknown]
> > gpg: WARNING: This key is not certified with a trusted signature!
> > gpg:  There is no indication that the signature belongs to the
> > owner.
> > Primary key fingerprint: DBCC D103 B8B2 4F86 FFAA  B025 C8BB 472C D297
> D428
> >
> > I don't know if Jonathan's key was not created by a trusted key.
> >
> > Well that's all, let me know what you think about this change or what you
> > would like to see in official TomEE image.
> >
> > Alex.
> >
>

Re: Apache TomEE official image

[Alex Soto]

Guys what do you prefer for official Docker image. Be light with Alpine or
be versatile with Debian?

El dl., 22 juny 2015 a les 23:59, Alex Soto () va
escriure:

> Thanks well I am still not 100% happy, what I am wondering is if debian
> image or alpine image. I m hesitant about this :)
>
> El dl., 22 juny 2015 a les 23:23, Jean-Louis Monteiro (<
> jlmonte...@tomitribe.com>) va escriure:
>
>> This is awesome Alex.
>> Thanks for driving this from start to end.
>>
>> Really great contribution.
>>
>> --
>> Jean-Louis Monteiro
>> http://twitter.com/jlouismonteiro
>> http://www.tomitribe.com
>>
>> On Thu, Jun 18, 2015 at 11:03 AM, Alex Soto  wrote:
>>
>> > Hi mates I have been working on creating a TomEE image in Docker.
>> > I am closely to be able to release an Apache TomEE official repository
>> on
>> > docker hub, but I prefer you take a look first.
>> >
>> > First of all I have decided to change from official openjdk image which
>> is
>> > based on debian, to official Alpine image. This change is pretty simple,
>> > the Alpine docker image is a light docker image (only 5MB) and following
>> > the philosophy of TomEE of light yet powerful distribution, I think
>> this is
>> > a really good movement in these terms. Now the TomEE Docker image is
>> 200MB
>> > less than the one using Debian. Concretely 191MB in front of 379MB.
>> >
>> > Let me share with you the Dockerfile content:
>> >
>> > FROM alpine:3.2
>> >
>> > RUN apk --update add bash
>> > RUN apk --update add curl
>> > RUN apk --update add openjdk7
>> > RUN apk --update add gnupg
>> >
>> > # add our user and group first to make sure their IDs get assigned
>> > consistently, regardless of whatever dependencies get added
>> > RUN addgroup -S tomee && adduser -S -G tomee tomee
>> >
>> > ENV PATH /usr/local/tomee/bin:$PATH
>> > RUN mkdir -p /usr/local/tomee
>> > RUN chown tomee:tomee /usr/local/tomee
>> > WORKDIR /usr/local/tomee
>> > USER tomee
>> >
>> > RUN curl -SL http://www.apache.org/dist/tomee/KEYS -o KEYS \
>> > && gpg --import KEYS
>> >
>> > RUN curl -SL
>> >
>> >
>> https://dist.apache.org/repos/dist/release/tomee/tomee-1.7.2/apache-tomee-1.7.2-webprofile.tar.gz.asc
>> > -o
>> > tomee.tar.gz.asc
>> >
>> > RUN curl -SL
>> >
>> >
>> http://apache.rediris.es/tomee/tomee-1.7.2/apache-tomee-1.7.2-webprofile.tar.gz
>> > -o
>> > tomee.tar.gz \
>> > && tar -zxvf tomee.tar.gz  \
>> > && gpg --verify tomee.tar.gz.asc tomee.tar.gz \
>> > && mv apache-tomee-webprofile-1.7.2/* /usr/local/tomee \
>> > && rm -Rf apache-tomee-plus-1.7.2 \
>> > && rm bin/*.bat \
>> > && rm tomee.tar.gz*
>> >
>> > EXPOSE 8080
>> > CMD ["catalina.sh", "run"]
>> >
>> > But it has two drawback is that alpine 3.2 still don't have support in
>> APK
>> > for openjdk8, but it will be added for alpine 3.3 so I am quite
>> confident
>> > that the best way to proceed is wait until it is released and then
>> update
>> > our Dockerfile and finally release our image as official image with
>> > OpenJDK8.
>> >
>> > The second problem is that we are setting alpine linux as default image
>> in
>> > our distribution and not a more popular like Debian.
>> >
>> > Another message I have seen while creating the image was this one:
>> >
>> > gpg: Signature made Sun May 17 22:18:30 2015 UTC using DSA key ID
>> D297D428
>> > gpg: Good signature from "Jonathan Gallimore "
>> > [unknown]
>> > gpg: WARNING: This key is not certified with a trusted signature!
>> > gpg:  There is no indication that the signature belongs to the
>> > owner.
>> > Primary key fingerprint: DBCC D103 B8B2 4F86 FFAA  B025 C8BB 472C D297
>> D428
>> >
>> > I don't know if Jonathan's key was not created by a trusted key.
>> >
>> > Well that's all, let me know what you think about this change or what
>> you
>> > would like to see in official TomEE image.
>> >
>> > Alex.
>> >
>>
>

Re: Apache TomEE official image

[Alex Soto]

well for final users doesn't have a deep impact since containers abstracts
from all these kind of things. But for example I see that if your
application is going to have more than container, you would like to have
same containers as based containers so Debian is a distribution more
generic and spread across developers. But of course we are paying the cost
of not being as light as Alpine.

On the other hand official images also offers the dockerfile so anyone can
build its own image with his favourite distro.

El dt., 23 juny 2015 a les 17:41, Romain Manni-Bucau ()
va escriure:

> debian is more known IMO but not sure it changes much things for final
> users, what's your opinion Alex?
>
>
> Romain Manni-Bucau
> @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> <http://rmannibucau.wordpress.com> | Github <
> https://github.com/rmannibucau> |
> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
> <http://www.tomitribe.com>
>
> 2015-06-23 17:31 GMT+02:00 Alex Soto :
>
> > Guys what do you prefer for official Docker image. Be light with Alpine
> or
> > be versatile with Debian?
> >
> > El dl., 22 juny 2015 a les 23:59, Alex Soto () va
> > escriure:
> >
> > > Thanks well I am still not 100% happy, what I am wondering is if debian
> > > image or alpine image. I m hesitant about this :)
> > >
> > > El dl., 22 juny 2015 a les 23:23, Jean-Louis Monteiro (<
> > > jlmonte...@tomitribe.com>) va escriure:
> > >
> > >> This is awesome Alex.
> > >> Thanks for driving this from start to end.
> > >>
> > >> Really great contribution.
> > >>
> > >> --
> > >> Jean-Louis Monteiro
> > >> http://twitter.com/jlouismonteiro
> > >> http://www.tomitribe.com
> > >>
> > >> On Thu, Jun 18, 2015 at 11:03 AM, Alex Soto 
> wrote:
> > >>
> > >> > Hi mates I have been working on creating a TomEE image in Docker.
> > >> > I am closely to be able to release an Apache TomEE official
> repository
> > >> on
> > >> > docker hub, but I prefer you take a look first.
> > >> >
> > >> > First of all I have decided to change from official openjdk image
> > which
> > >> is
> > >> > based on debian, to official Alpine image. This change is pretty
> > simple,
> > >> > the Alpine docker image is a light docker image (only 5MB) and
> > following
> > >> > the philosophy of TomEE of light yet powerful distribution, I think
> > >> this is
> > >> > a really good movement in these terms. Now the TomEE Docker image is
> > >> 200MB
> > >> > less than the one using Debian. Concretely 191MB in front of 379MB.
> > >> >
> > >> > Let me share with you the Dockerfile content:
> > >> >
> > >> > FROM alpine:3.2
> > >> >
> > >> > RUN apk --update add bash
> > >> > RUN apk --update add curl
> > >> > RUN apk --update add openjdk7
> > >> > RUN apk --update add gnupg
> > >> >
> > >> > # add our user and group first to make sure their IDs get assigned
> > >> > consistently, regardless of whatever dependencies get added
> > >> > RUN addgroup -S tomee && adduser -S -G tomee tomee
> > >> >
> > >> > ENV PATH /usr/local/tomee/bin:$PATH
> > >> > RUN mkdir -p /usr/local/tomee
> > >> > RUN chown tomee:tomee /usr/local/tomee
> > >> > WORKDIR /usr/local/tomee
> > >> > USER tomee
> > >> >
> > >> > RUN curl -SL http://www.apache.org/dist/tomee/KEYS -o KEYS \
> > >> > && gpg --import KEYS
> > >> >
> > >> > RUN curl -SL
> > >> >
> > >> >
> > >>
> >
> https://dist.apache.org/repos/dist/release/tomee/tomee-1.7.2/apache-tomee-1.7.2-webprofile.tar.gz.asc
> > >> > -o
> > >> > tomee.tar.gz.asc
> > >> >
> > >> > RUN curl -SL
> > >> >
> > >> >
> > >>
> >
> http://apache.rediris.es/tomee/tomee-1.7.2/apache-tomee-1.7.2-webprofile.tar.gz
> > >> > -o
> > >> > tomee.tar.gz \
> > >> > && tar -zxvf tomee.tar.gz  \
> > >> > && gpg --verify tomee.tar.gz.asc tomee.tar.gz \
> > >> > && mv apache

Re: Apache TomEE official image

[Alex Soto]

well having twice of work when we release a new version of TomEE :) because
you need to do some steps with github to create a file which points to each
commit. Not critical work but more work. Moreover another think that I see
is that I haven not find any official image that is provided with two
different distros.

El dt., 23 juny 2015 a les 17:48, Romain Manni-Bucau ()
va escriure:

> what's the cost of havingboth BTW?
>
>
> Romain Manni-Bucau
> @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> <http://rmannibucau.wordpress.com> | Github <
> https://github.com/rmannibucau> |
> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
> <http://www.tomitribe.com>
>
> 2015-06-23 17:46 GMT+02:00 Mark Struberg :
>
> > I really like Alpine. Gives you apk as well but is really down to the
> core
> > without any useless ballast.
> >
> > LieGrue,
> > strub
> >
> >
> > > Am 23.06.2015 um 17:40 schrieb Romain Manni-Bucau <
> rmannibu...@gmail.com
> > >:
> > >
> > > debian is more known IMO but not sure it changes much things for final
> > > users, what's your opinion Alex?
> > >
> > >
> > > Romain Manni-Bucau
> > > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > > <http://rmannibucau.wordpress.com> | Github <
> > https://github.com/rmannibucau> |
> > > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
> > > <http://www.tomitribe.com>
> > >
> > > 2015-06-23 17:31 GMT+02:00 Alex Soto :
> > >
> > >> Guys what do you prefer for official Docker image. Be light with
> Alpine
> > or
> > >> be versatile with Debian?
> > >>
> > >> El dl., 22 juny 2015 a les 23:59, Alex Soto () va
> > >> escriure:
> > >>
> > >>> Thanks well I am still not 100% happy, what I am wondering is if
> debian
> > >>> image or alpine image. I m hesitant about this :)
> > >>>
> > >>> El dl., 22 juny 2015 a les 23:23, Jean-Louis Monteiro (<
> > >>> jlmonte...@tomitribe.com>) va escriure:
> > >>>
> > >>>> This is awesome Alex.
> > >>>> Thanks for driving this from start to end.
> > >>>>
> > >>>> Really great contribution.
> > >>>>
> > >>>> --
> > >>>> Jean-Louis Monteiro
> > >>>> http://twitter.com/jlouismonteiro
> > >>>> http://www.tomitribe.com
> > >>>>
> > >>>> On Thu, Jun 18, 2015 at 11:03 AM, Alex Soto 
> > wrote:
> > >>>>
> > >>>>> Hi mates I have been working on creating a TomEE image in Docker.
> > >>>>> I am closely to be able to release an Apache TomEE official
> > repository
> > >>>> on
> > >>>>> docker hub, but I prefer you take a look first.
> > >>>>>
> > >>>>> First of all I have decided to change from official openjdk image
> > >> which
> > >>>> is
> > >>>>> based on debian, to official Alpine image. This change is pretty
> > >> simple,
> > >>>>> the Alpine docker image is a light docker image (only 5MB) and
> > >> following
> > >>>>> the philosophy of TomEE of light yet powerful distribution, I think
> > >>>> this is
> > >>>>> a really good movement in these terms. Now the TomEE Docker image
> is
> > >>>> 200MB
> > >>>>> less than the one using Debian. Concretely 191MB in front of 379MB.
> > >>>>>
> > >>>>> Let me share with you the Dockerfile content:
> > >>>>>
> > >>>>> FROM alpine:3.2
> > >>>>>
> > >>>>> RUN apk --update add bash
> > >>>>> RUN apk --update add curl
> > >>>>> RUN apk --update add openjdk7
> > >>>>> RUN apk --update add gnupg
> > >>>>>
> > >>>>> # add our user and group first to make sure their IDs get assigned
> > >>>>> consistently, regardless of whatever dependencies get added
> > >>>>> RUN addgroup -S tomee && adduser -S -G tomee tomee
> > >>>>>
> > >>>>> ENV PATH /usr/local/tomee/bin:$PATH
> > >>>>> RUN mkdir -p /usr/local/tomee
&g

Re: Apache TomEE official image

[Alex Soto]

Ok so we have Jean-Louis and Romain that we can say they are neutral, Mark
for alpine and Andy for Debian.
For me Alpine is the best one in terms of performance but we are tight to
apk which is far always from being as good as debian apt get
El dt., 23 de juny, 2015 a les 21.25 Andy Gumbrecht <
agumbre...@tomitribe.com> va escriure:

> Jumping in late. This image will be used as a foundation for others to
> extend with many different features. Therefore I think the image should
> provide as much flexibility as possible
>
> Thanks for all your work Alex.
>
> Andy.
>
> http://www.tomitribe.com - @AndyGeeDe - On a small screen device.
> On 23 Jun 2015 17:26, "Mark Struberg"  wrote:
>
> > almost nothing.
> > 2 Dockerfiles and a bit of storage ;)
> >
> > LieGrue,
> > strub
> >
> >
> > > Am 23.06.2015 um 17:48 schrieb Romain Manni-Bucau <
> rmannibu...@gmail.com
> > >:
> > >
> > > what's the cost of havingboth BTW?
> > >
> > >
> > > Romain Manni-Bucau
> > > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > > <http://rmannibucau.wordpress.com> | Github <
> > https://github.com/rmannibucau> |
> > > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
> > > <http://www.tomitribe.com>
> > >
> > > 2015-06-23 17:46 GMT+02:00 Mark Struberg :
> > >
> > >> I really like Alpine. Gives you apk as well but is really down to the
> > core
> > >> without any useless ballast.
> > >>
> > >> LieGrue,
> > >> strub
> > >>
> > >>
> > >>> Am 23.06.2015 um 17:40 schrieb Romain Manni-Bucau <
> > rmannibu...@gmail.com
> > >>> :
> > >>>
> > >>> debian is more known IMO but not sure it changes much things for
> final
> > >>> users, what's your opinion Alex?
> > >>>
> > >>>
> > >>> Romain Manni-Bucau
> > >>> @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > >>> <http://rmannibucau.wordpress.com> | Github <
> > >> https://github.com/rmannibucau> |
> > >>> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
> > >>> <http://www.tomitribe.com>
> > >>>
> > >>> 2015-06-23 17:31 GMT+02:00 Alex Soto :
> > >>>
> > >>>> Guys what do you prefer for official Docker image. Be light with
> > Alpine
> > >> or
> > >>>> be versatile with Debian?
> > >>>>
> > >>>> El dl., 22 juny 2015 a les 23:59, Alex Soto ()
> va
> > >>>> escriure:
> > >>>>
> > >>>>> Thanks well I am still not 100% happy, what I am wondering is if
> > debian
> > >>>>> image or alpine image. I m hesitant about this :)
> > >>>>>
> > >>>>> El dl., 22 juny 2015 a les 23:23, Jean-Louis Monteiro (<
> > >>>>> jlmonte...@tomitribe.com>) va escriure:
> > >>>>>
> > >>>>>> This is awesome Alex.
> > >>>>>> Thanks for driving this from start to end.
> > >>>>>>
> > >>>>>> Really great contribution.
> > >>>>>>
> > >>>>>> --
> > >>>>>> Jean-Louis Monteiro
> > >>>>>> http://twitter.com/jlouismonteiro
> > >>>>>> http://www.tomitribe.com
> > >>>>>>
> > >>>>>> On Thu, Jun 18, 2015 at 11:03 AM, Alex Soto 
> > >> wrote:
> > >>>>>>
> > >>>>>>> Hi mates I have been working on creating a TomEE image in Docker.
> > >>>>>>> I am closely to be able to release an Apache TomEE official
> > >> repository
> > >>>>>> on
> > >>>>>>> docker hub, but I prefer you take a look first.
> > >>>>>>>
> > >>>>>>> First of all I have decided to change from official openjdk image
> > >>>> which
> > >>>>>> is
> > >>>>>>> based on debian, to official Alpine image. This change is pretty
> > >>>> simple,
> > >>>>>>> the Alpine docker image is a light docker image (only 5MB) and
> > >>>> following
> > >&g

Re: Apache TomEE official image

[Alex Soto]

Well it is an official image, not sure if people would use for demos only
or not.

El dc., 24 juny 2015 a les 8:47, Andy Gumbrecht ()
va escriure:

> Sure, but I know at least one interested party that will want to add
> substantial packages. So they would need their own image I guess. If this
> lightweight image is just for demos and showcasing, then sure, as small as
> possible.
>
> http://www.tomitribe.com - @AndyGeeDe - On a small screen device.
> On 23 Jun 2015 23:38, "Jean-Louis Monteiro" 
> wrote:
>
> > Let's refine if it helps.
> > Alpine is lightweight and sounds like closer to what TomEE tries to do.
> >
> > +1 for Alpine then
> >
> > --
> > Jean-Louis Monteiro
> > http://twitter.com/jlouismonteiro
> > http://www.tomitribe.com
> >
> > On Tue, Jun 23, 2015 at 5:16 PM, Alex Soto  wrote:
> >
> > > Ok so we have Jean-Louis and Romain that we can say they are neutral,
> > Mark
> > > for alpine and Andy for Debian.
> > > For me Alpine is the best one in terms of performance but we are tight
> to
> > > apk which is far always from being as good as debian apt get
> > > El dt., 23 de juny, 2015 a les 21.25 Andy Gumbrecht <
> > > agumbre...@tomitribe.com> va escriure:
> > >
> > > > Jumping in late. This image will be used as a foundation for others
> to
> > > > extend with many different features. Therefore I think the image
> should
> > > > provide as much flexibility as possible
> > > >
> > > > Thanks for all your work Alex.
> > > >
> > > > Andy.
> > > >
> > > > http://www.tomitribe.com - @AndyGeeDe - On a small screen device.
> > > > On 23 Jun 2015 17:26, "Mark Struberg"  wrote:
> > > >
> > > > > almost nothing.
> > > > > 2 Dockerfiles and a bit of storage ;)
> > > > >
> > > > > LieGrue,
> > > > > strub
> > > > >
> > > > >
> > > > > > Am 23.06.2015 um 17:48 schrieb Romain Manni-Bucau <
> > > > rmannibu...@gmail.com
> > > > > >:
> > > > > >
> > > > > > what's the cost of havingboth BTW?
> > > > > >
> > > > > >
> > > > > > Romain Manni-Bucau
> > > > > > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > > > > > <http://rmannibucau.wordpress.com> | Github <
> > > > > https://github.com/rmannibucau> |
> > > > > > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
> > > > > > <http://www.tomitribe.com>
> > > > > >
> > > > > > 2015-06-23 17:46 GMT+02:00 Mark Struberg :
> > > > > >
> > > > > >> I really like Alpine. Gives you apk as well but is really down
> to
> > > the
> > > > > core
> > > > > >> without any useless ballast.
> > > > > >>
> > > > > >> LieGrue,
> > > > > >> strub
> > > > > >>
> > > > > >>
> > > > > >>> Am 23.06.2015 um 17:40 schrieb Romain Manni-Bucau <
> > > > > rmannibu...@gmail.com
> > > > > >>> :
> > > > > >>>
> > > > > >>> debian is more known IMO but not sure it changes much things
> for
> > > > final
> > > > > >>> users, what's your opinion Alex?
> > > > > >>>
> > > > > >>>
> > > > > >>> Romain Manni-Bucau
> > > > > >>> @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > > > > >>> <http://rmannibucau.wordpress.com> | Github <
> > > > > >> https://github.com/rmannibucau> |
> > > > > >>> LinkedIn <https://www.linkedin.com/in/rmannibucau> |
> Tomitriber
> > > > > >>> <http://www.tomitribe.com>
> > > > > >>>
> > > > > >>> 2015-06-23 17:31 GMT+02:00 Alex Soto :
> > > > > >>>
> > > > > >>>> Guys what do you prefer for official Docker image. Be light
> with
> > > > > Alpine
> > > > > >> or
> > > > > >>>> be versatile with Debian?
> > > > > >>>>
> > > > > >>>> 

Re: Apache TomEE official image

[Alex Soto]

I have the same opinion of Adam but of course I don t have the vision of
what almost all companies will do
El dc., 24 de juny, 2015 a les 18.33 Adam Cornett 
va escriure:

> I don't think it is possible to create a "one-size-fits-all" image.  The
> official one could be very useful for trying out TomEE and getting
> started.  But I think in many cases people would take the Docker file and
> use it as a starting point to create their own image when using it for a
> production application. For instance doing things like replacing OpenJDK
> with Oracle Java or using the distro of choice for the system admin.
>
> I think having an official image that meets the Java EE 7 spec, is
> lightweight, and 'just works' is the best plan and it can serve as a
> starting point for those wishing to create a more tailored container.
>
>
> On Wed, Jun 24, 2015 at 4:10 AM, Alex Soto  wrote:
>
> > Well it is an official image, not sure if people would use for demos only
> > or not.
> >
> > El dc., 24 juny 2015 a les 8:47, Andy Gumbrecht (<
> agumbre...@tomitribe.com
> > >)
> > va escriure:
> >
> > > Sure, but I know at least one interested party that will want to add
> > > substantial packages. So they would need their own image I guess. If
> this
> > > lightweight image is just for demos and showcasing, then sure, as small
> > as
> > > possible.
> > >
> > > http://www.tomitribe.com - @AndyGeeDe - On a small screen device.
> > > On 23 Jun 2015 23:38, "Jean-Louis Monteiro" 
> > > wrote:
> > >
> > > > Let's refine if it helps.
> > > > Alpine is lightweight and sounds like closer to what TomEE tries to
> do.
> > > >
> > > > +1 for Alpine then
> > > >
> > > > --
> > > > Jean-Louis Monteiro
> > > > http://twitter.com/jlouismonteiro
> > > > http://www.tomitribe.com
> > > >
> > > > On Tue, Jun 23, 2015 at 5:16 PM, Alex Soto 
> wrote:
> > > >
> > > > > Ok so we have Jean-Louis and Romain that we can say they are
> neutral,
> > > > Mark
> > > > > for alpine and Andy for Debian.
> > > > > For me Alpine is the best one in terms of performance but we are
> > tight
> > > to
> > > > > apk which is far always from being as good as debian apt get
> > > > > El dt., 23 de juny, 2015 a les 21.25 Andy Gumbrecht <
> > > > > agumbre...@tomitribe.com> va escriure:
> > > > >
> > > > > > Jumping in late. This image will be used as a foundation for
> others
> > > to
> > > > > > extend with many different features. Therefore I think the image
> > > should
> > > > > > provide as much flexibility as possible
> > > > > >
> > > > > > Thanks for all your work Alex.
> > > > > >
> > > > > > Andy.
> > > > > >
> > > > > > http://www.tomitribe.com - @AndyGeeDe - On a small screen
> device.
> > > > > > On 23 Jun 2015 17:26, "Mark Struberg"  wrote:
> > > > > >
> > > > > > > almost nothing.
> > > > > > > 2 Dockerfiles and a bit of storage ;)
> > > > > > >
> > > > > > > LieGrue,
> > > > > > > strub
> > > > > > >
> > > > > > >
> > > > > > > > Am 23.06.2015 um 17:48 schrieb Romain Manni-Bucau <
> > > > > > rmannibu...@gmail.com
> > > > > > > >:
> > > > > > > >
> > > > > > > > what's the cost of havingboth BTW?
> > > > > > > >
> > > > > > > >
> > > > > > > > Romain Manni-Bucau
> > > > > > > > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > > > > > > > <http://rmannibucau.wordpress.com> | Github <
> > > > > > > https://github.com/rmannibucau> |
> > > > > > > > LinkedIn <https://www.linkedin.com/in/rmannibucau> |
> > Tomitriber
> > > > > > > > <http://www.tomitribe.com>
> > > > > > > >
> > > > > > > > 2015-06-23 17:46 GMT+02:00 Mark Struberg  >:
> > > > > > > >
> > > > > > > >> I really like Alpine. Gives you apk as wel

Protocol of Arquillian Embedded Adapter

[Alex Soto]

Hello mates,

I send this email to start a discussion for a change on TomEE Arquillian
Adapter.

The other day, because of the book (Arquillian In Action), I checked the
protocol used by different adapters. I noticed that only Weld adapter and
TomEE embedded adapter are using the local protocol,all other ones are
using the Servlet 3.0 protocol. And maybe you are asking why this is
important? Well the problem is that a lot of extensions requires this
protocol to work, for example Arquillian Persistence extension or Arquillan
Warp extension. In case a user wants to use  embedded TomEE and one
extension that requires servlet protocol, it would get a cryptic exception.
Of course there is a workaround and it is overriding the default protocol
by using protocol special tag in arquillian.xml and adding the
servlet-protocol dependency.

I think that it would be easier for everyone if all adapters works in the
same way. With the release of TomEE 7 I think it could be a good
opportunity to make this change in the Arquillian embedded adapter as well
and align with the rest of the containers.

The change to be done is very simple in terms of code (Adding one
dependency and change one String of the adapter).

What do you think? From the point of view of Arquillian community it would
be the logic step.

Alex.

Arquillian Chameleon

[Alex Soto]

Hello, I don't know if you are aware of arquillian chameleon (
https://github.com/arquillian/arquillian-container-chameleon) basically
this project acts as a container proxy  for resolving which container and
mode you want to use in your tests, so you only need to modify one string
to change from one implementation or mode to another. For example:



wildfly:8.0.0.Final:managed
standalone-full.xml




Notice that if you want to change to another version of wildfly, you only
need to change one string, Chameleon takes care of resolving the
dependencies and modifying the classpath. Currently we have support for
Wildfly, JBoss, Glassfish (with all modes) and also we have support for
TomEE managed. But we are facing some classloader problems with embedded
mode. You can see the commit here:
https://github.com/arquillian/arquillian-container-chameleon/commit/ead79be84b5db3e6f72211218384e6b9f1179030

We think that Arquillian Chameleon is going to be the future of Arquillian
for configuring the containers as well as it is going to be Arquillian
Universe (https://github.com/arquillian/arquillian-universe-bom) for
defining extensions.

I send this thread in the dev list because maybe this issue might require a
lot of discussion and maybe changes on code.

Cheers,
Alex.

Re: Arquillian Chameleon

[Alex Soto]

The idea is standarize how to define containers, it is not a substitution
but it is a way to group all of this so users don t need to learn of each
dependency of each server. So you can use the old way (current) but also
the chameleon way, and it seems that it is having a lot of acceptance in
arquillian users. So I think that adding support for TomEE would be nice to
have the complete profile there. As I said there is a starting point and it
the problem is only the embedded mode

Alex
El dg, 4 oct 2015 a les 7:51 Romain Manni-Bucau  va
escriure:

> Hi
>
> Tomee supports it since years so not sure chamaleon would be used with
> tomee in practise
> Le 3 oct. 2015 23:31, "Alex Soto"  a écrit :
>
> > Hello, I don't know if you are aware of arquillian chameleon (
> > https://github.com/arquillian/arquillian-container-chameleon) basically
> > this project acts as a container proxy  for resolving which container and
> > mode you want to use in your tests, so you only need to modify one string
> > to change from one implementation or mode to another. For example:
> >
> > 
> > 
> >  > name="chameleonTarget">wildfly:8.0.0.Final:managed
> > standalone-full.xml
> > 
> > 
> >
> >
> > Notice that if you want to change to another version of wildfly, you only
> > need to change one string, Chameleon takes care of resolving the
> > dependencies and modifying the classpath. Currently we have support for
> > Wildfly, JBoss, Glassfish (with all modes) and also we have support for
> > TomEE managed. But we are facing some classloader problems with embedded
> > mode. You can see the commit here:
> >
> >
> https://github.com/arquillian/arquillian-container-chameleon/commit/ead79be84b5db3e6f72211218384e6b9f1179030
> >
> > We think that Arquillian Chameleon is going to be the future of
> Arquillian
> > for configuring the containers as well as it is going to be Arquillian
> > Universe (https://github.com/arquillian/arquillian-universe-bom) for
> > defining extensions.
> >
> > I send this thread in the dev list because maybe this issue might
> require a
> > lot of discussion and maybe changes on code.
> >
> > Cheers,
> > Alex.
> >
>

Re: Protocol of Arquillian Embedded Adapter

[Alex Soto]

If there are bugs/improvements let s do it. I am thinking in terms of doing
the life of developers easier and in fact changing the protocol to servlet
dos not introduce (a priori) any back incompatibility but a lot of
extensions are going to work with embedded mode.

Alex.

El dg, 4 oct 2015 a les 7:53 Romain Manni-Bucau  va
escriure:

> Hi Alex
>
> Local protocol allows nicer start so very tempted to keep it like that.
> Servlet protocol has few bugs/issues and is not what you target by default
> with embedded adapters IMO.
> Le 4 oct. 2015 01:25, "John D. Ament"  a écrit :
>
> > Hey Alex,
> >
> > To be honest, I find the protocol section of arquillian the most
> confusing
> > for new users to pick up.  Why should they care what the protocol
> > transferring the test data is using?  I remember at the beginning, AS7
> had
> > a JMX protocol.  This made tons of sense, since it didn't impact the
> > running application.  No one understood why their tests stopped work
> > though!  Truth be told, the fact that most people end up relying on
> > servlet, without even realizing that its the arquillian runtime starting
> an
> > HTTP request makes it confusing to understand scope.  Basically, users
> end
> > up relying on the servlet protocol to start their HTTP request for them,
> > instead of starting an HTTP request for their test invocation.
> >
> > Just curious, is this out on discourse somewhere? I can continue my whine
> > fest there :-)
> >
> > John
> >
> > On Sat, Oct 3, 2015 at 4:58 PM Alex Soto  wrote:
> >
> > > Hello mates,
> > >
> > > I send this email to start a discussion for a change on TomEE
> Arquillian
> > > Adapter.
> > >
> > > The other day, because of the book (Arquillian In Action), I checked
> the
> > > protocol used by different adapters. I noticed that only Weld adapter
> and
> > > TomEE embedded adapter are using the local protocol,all other ones are
> > > using the Servlet 3.0 protocol. And maybe you are asking why this is
> > > important? Well the problem is that a lot of extensions requires this
> > > protocol to work, for example Arquillian Persistence extension or
> > Arquillan
> > > Warp extension. In case a user wants to use  embedded TomEE and one
> > > extension that requires servlet protocol, it would get a cryptic
> > exception.
> > > Of course there is a workaround and it is overriding the default
> protocol
> > > by using protocol special tag in arquillian.xml and adding the
> > > servlet-protocol dependency.
> > >
> > > I think that it would be easier for everyone if all adapters works in
> the
> > > same way. With the release of TomEE 7 I think it could be a good
> > > opportunity to make this change in the Arquillian embedded adapter as
> > well
> > > and align with the rest of the containers.
> > >
> > > The change to be done is very simple in terms of code (Adding one
> > > dependency and change one String of the adapter).
> > >
> > > What do you think? From the point of view of Arquillian community it
> > would
> > > be the logic step.
> > >
> > > Alex.
> > >
> >
>

Re: Protocol of Arquillian Embedded Adapter

[Alex Soto]

But what is the advantage of using local instead of http? I am sure that
the performance is going to be pretty similar.

El dl., 5 oct. 2015 a les 14:01, Romain Manni-Bucau ()
va escriure:

> You can see it the opposite as well ie you go through http where you can
> not desire it.
>
> 50-50 case i think.
> Le 5 oct. 2015 13:52, "John D. Ament"  a écrit :
>
> > The fundamental problem (if I had to guess) is that let's say I'm
> testing a
> > REST API (heck even using the REST extension), persistence extension
> > doesn't know that my request went through since I'm controlling it, so
> its
> > call backs won't take effect.  By running embedded, you're more likely to
> > not be inside the same transaction, which is one of the things being
> banked
> > on I'm sure.
> >
> > John
> >
> > On Mon, Oct 5, 2015 at 3:26 AM Alex Soto  wrote:
> >
> > > If there are bugs/improvements let s do it. I am thinking in terms of
> > doing
> > > the life of developers easier and in fact changing the protocol to
> > servlet
> > > dos not introduce (a priori) any back incompatibility but a lot of
> > > extensions are going to work with embedded mode.
> > >
> > > Alex.
> > >
> > > El dg, 4 oct 2015 a les 7:53 Romain Manni-Bucau  >
> > va
> > > escriure:
> > >
> > > > Hi Alex
> > > >
> > > > Local protocol allows nicer start so very tempted to keep it like
> that.
> > > > Servlet protocol has few bugs/issues and is not what you target by
> > > default
> > > > with embedded adapters IMO.
> > > > Le 4 oct. 2015 01:25, "John D. Ament"  a
> écrit
> > :
> > > >
> > > > > Hey Alex,
> > > > >
> > > > > To be honest, I find the protocol section of arquillian the most
> > > > confusing
> > > > > for new users to pick up.  Why should they care what the protocol
> > > > > transferring the test data is using?  I remember at the beginning,
> > AS7
> > > > had
> > > > > a JMX protocol.  This made tons of sense, since it didn't impact
> the
> > > > > running application.  No one understood why their tests stopped
> work
> > > > > though!  Truth be told, the fact that most people end up relying on
> > > > > servlet, without even realizing that its the arquillian runtime
> > > starting
> > > > an
> > > > > HTTP request makes it confusing to understand scope.  Basically,
> > users
> > > > end
> > > > > up relying on the servlet protocol to start their HTTP request for
> > > them,
> > > > > instead of starting an HTTP request for their test invocation.
> > > > >
> > > > > Just curious, is this out on discourse somewhere? I can continue my
> > > whine
> > > > > fest there :-)
> > > > >
> > > > > John
> > > > >
> > > > > On Sat, Oct 3, 2015 at 4:58 PM Alex Soto 
> wrote:
> > > > >
> > > > > > Hello mates,
> > > > > >
> > > > > > I send this email to start a discussion for a change on TomEE
> > > > Arquillian
> > > > > > Adapter.
> > > > > >
> > > > > > The other day, because of the book (Arquillian In Action), I
> > checked
> > > > the
> > > > > > protocol used by different adapters. I noticed that only Weld
> > adapter
> > > > and
> > > > > > TomEE embedded adapter are using the local protocol,all other
> ones
> > > are
> > > > > > using the Servlet 3.0 protocol. And maybe you are asking why this
> > is
> > > > > > important? Well the problem is that a lot of extensions requires
> > this
> > > > > > protocol to work, for example Arquillian Persistence extension or
> > > > > Arquillan
> > > > > > Warp extension. In case a user wants to use  embedded TomEE and
> one
> > > > > > extension that requires servlet protocol, it would get a cryptic
> > > > > exception.
> > > > > > Of course there is a workaround and it is overriding the default
> > > > protocol
> > > > > > by using protocol special tag in arquillian.xml and adding the
> > > > > > servlet-protocol dependency.
> > > > > >
> > > > > > I think that it would be easier for everyone if all adapters
> works
> > in
> > > > the
> > > > > > same way. With the release of TomEE 7 I think it could be a good
> > > > > > opportunity to make this change in the Arquillian embedded
> adapter
> > as
> > > > > well
> > > > > > and align with the rest of the containers.
> > > > > >
> > > > > > The change to be done is very simple in terms of code (Adding one
> > > > > > dependency and change one String of the adapter).
> > > > > >
> > > > > > What do you think? From the point of view of Arquillian community
> > it
> > > > > would
> > > > > > be the logic step.
> > > > > >
> > > > > > Alex.
> > > > > >
> > > > >
> > > >
> > >
> >
>

Re: PMD & Formatting

[Alex Soto]

I think that a  good way to maintain all code style using the same format
would be use a tool like Walkmod (http://walkmod.com/) it is only an ida of
course.

Alex

El dj., 19 nov. 2015 a les 16:29, Romain Manni-Bucau ()
va escriure:

> Go for it
> Le 19 nov. 2015 06:54, "Thiago Veronezi"  a écrit :
>
> > Hi guys,
> >
> > is anyone going to commit the files with the wrong line endings?
> >
> > []s,
> > Thiago.
> >
> >
> > On Thu, Nov 19, 2015 at 9:38 AM, Romain Manni-Bucau <
> rmannibu...@gmail.com
> > >
> > wrote:
> >
> > > +1
> > >
> > > Only note: we have a huge codebase so we shouldnt completely reformat
> it
> > > IMO. Said otherwise we should ensure the IDE reformatting keeps code as
> > it
> > > is in 99% of the case
> > >
> > > Ps: thks a lot for the github link!
> > > Le 19 nov. 2015 05:19, "Thiago Veronezi"  a
> écrit :
> > >
> > > > Formating >>
> > > >
> > > > When I introduced the pmd and checkstyle plugins, I've created a new
> > > maven
> > > > profile in order to keep the simple "mvn clean install" a bit faster.
> > > Maybe
> > > > we could make it run by default without the extra profile? This way,
> a
> > > > developer would know right away when she/he introduced any formatting
> > > > violation without depending on any IDE.
> > > >
> > > > []s,
> > > > Thiago.
> > > >
> > > >
> > > > On Thu, Nov 19, 2015 at 7:43 AM, Andy Gumbrecht <
> > > agumbre...@tomitribe.com>
> > > > wrote:
> > > >
> > > > > Hi everyone,
> > > > >
> > > > > We keep running into PMD and formatting issues, as well as line
> > ending
> > > > > issues. These are just some ideas I'd like to run by you all, but
> > > please
> > > > > check the line-ending doc. Whatever we decide upon needs to be
> > applied
> > > > asap.
> > > > >
> > > > > Line Endings
> > > > > -
> > > > > Line ending issues need to be resolved by everyone using this
> > > > > documentation (for your OS of choice):
> > > > > https://help.github.com/articles/dealing-with-line-endings/ - as
> > > > probably
> > > > > 99.9% of us are GitHub users, this should be the rule.
> > > > >
> > > > > Please feel free to add to and extend the attributes with anything
> > that
> > > > > may be missing, but do not remove the basic structure of:
> > > > > https://github.com/apache/tomee/blob/master/.gitattributes
> > > > >
> > > > > Formatting
> > > > > ---
> > > > > Basically, pressing CTRL+ALT+L (Reformat) should result it the same
> > for
> > > > > everyone that is hacking on TomEE. This includes all project files.
> > > > >
> > > > > The only way this is going to work is if we define a rigid guide
> or,
> > > even
> > > > > better, provide an Intellij-IDEA settings import/export file for
> > > everyone
> > > > > to use as a foundation.
> > > > >
> > > > > David, as the project lead and our glorious master of all things
> > magic,
> > > > it
> > > > > would be great if you could provide this. I'm going to update the
> > site
> > > a
> > > > > bit, so would be great to get this added as soon as possible.
> > > > >
> > > > > Once we have this then a global reformat should be possible across
> > the
> > > > > entire project base. Enabling and using @formatter:off/on should be
> > > used
> > > > to
> > > > > protect critical sections.
> > > > >
> > > > > Feedback welcome.
> > > > >
> > > > > Andy.
> > > > >
> > > > > --
> > > > >   Andy Gumbrecht
> > > > >   https://twitter.com/AndyGeeDe
> > > > >   http://www.tomitribe.com
> > > > >
> > > > >
> > > >
> > >
> >
>

Re: PMD & Formatting

[Alex Soto]

The good thing about Walkmod is that you don't relay on IDE configuration,
it is a separated process that can generate a PR with the changes so all
code is uniform.

El dj., 19 nov. 2015 a les 16:35, Andy Gumbrecht ()
va escriure:

> +1 on anything that promotes a globally uniform format.
>
> Still need the IDEA settings import/export to match whatever is configured.
>
> Someone on unix box will have to ensure everything is LF except maybe
> *.bat & *.cmd <- Not sure how to handle that, but can be done in
> .gitattributes I think?
>
> --
>Andy Gumbrecht
>https://twitter.com/AndyGeeDe
>http://www.tomitribe.com
>
>

Re: Vote new committer: Daniel Cunha

[Alex Soto]

I agree with Andy it is a transparent way so all community can know this.
Of course I cannot vote, but it is good to know that Daniel is here too :)

El dv., 20 nov. 2015 a les 15:58, Andy Gumbrecht ()
va escriure:

> I started it - Thought it was supposed to be on dev?
>
> On 20/11/2015 15:55, Romain Manni-Bucau wrote:
> >
> > How so does it happen on dev? Maybe missed something bit this kind of
> > discussion should be done on private.
> >
> > Le 20 nov. 2015 04:31, "Thiago Veronezi"  > > a écrit :
> >
> > +1
> >
> > Daniel is an awesome developer with deep JavaEE knowledge along
> > with deep
> > Linux understanding. He will definitely be a great addition to the
> > project.
> > Thank you for all your contributions Daniel!
> >
> > []s,
> > Thiago.
> >
> >
> > On Fri, Nov 20, 2015 at 7:19 AM, Andy Gumbrecht
> > mailto:agumbre...@tomitribe.com>>
> > wrote:
> >
> > > I would like to propose that we accept DeltaSpike committer
> > Daniel Cunha
> > > as a committer on the TomEE project.
> > > Dani has been a long time supporter and contributor to the TomEE
> > project.
> > >
> > > Please reposond with a +1, 0, or -1, and any rationale you would
> > like to
> > > provide.
> > >
> > > Voting ends one week from today.
> > >
> > > Regards,
> > > Andy
> > >
> > > --
> > >   Andy Gumbrecht
> > > https://twitter.com/AndyGeeDe
> > > http://www.tomitribe.com
> > >
> > >
> >
>
> --
>Andy Gumbrecht
>https://twitter.com/AndyGeeDe
>http://www.tomitribe.com
>
>

Re: [VOTE] staging-1069 - tomee-7.0.0-M1

[Alex Soto]

Do you need any kind of help on this in terms of downloading something in
clean environment and inspect something?

El dv., 20 nov. 2015 a les 16:56, Romain Manni-Bucau ()
va escriure:

> Hmm
>
> Maybe check we dont have git info in mvn artifacts otherwise binaries would
> be wrong then. Anyone recalls?
> Le 20 nov. 2015 07:55, "Andy Gumbrecht"  a
> écrit :
>
> > Me too. so no idea where it's gone? - I'm going to delete it and take it
> > from the tomee-7.0.0-M1 branch again
> >
> > --
> >   Andy Gumbrecht
> >   https://twitter.com/AndyGeeDe
> >   http://www.tomitribe.com
> >
> >
>

Maven to Gradle

[Alex Soto]

Hi mates, I would like to implement some day something
like tomee-maven-plugin/ but for Gradle. I think that one previous step
before implementing Gradle plugin would be extracting some none Maven logic
from Maven plugin to some kind of common, so the same logic can be reused
in both plugins and maintain the same behaviour in both.

So the question is, where do you think is the best place to put this
reusable code?

Alex.

Re: [VOTE] staging-1069 - tomee-7.0.0-M1

[Alex Soto]

Maybe Walkmod can help on this?

El dt., 1 des. 2015 a les 15:20, Romain Manni-Bucau ()
va escriure:

> We can surely share more - that said mvn plugin should do it by itself -
> but each distribution (tomee web, tomee plus, openejb) has different jars
> and then different notices so not sure we can reduce the number of files -
> that said sharing the header template is a good idea. Also we have to
> conform to apache standards to aggregate licenses in a single file so
> licenses dir is a potentially nice addition but not a replacement for
> current setup.
>
>
> Romain Manni-Bucau
> @rmannibucau  |  Blog
>  | Github <
> https://github.com/rmannibucau> |
> LinkedIn  | Tomitriber
> 
>
> 2015-12-01 15:14 GMT+01:00 Andy :
>
> > Cancelling.
> > We should take the opportunity to ensure these issues do not arise in the
> > future.
> >
> > There are many notice & license files, but I think we should just have
> one
> > for all with appropriate wording. Something like:
> >
> > NOTICE
> > --
> > Apache OpenEJB/TomEE
> > Copyright 1999-2015 The Apache Software Foundation
> >
> > =
> >==  NOTICE file corresponding to the section 4 d of
> > ==
> >==  the Apache License, Version 2.0,
> >  ==
> >==  in this case for the Apache OpenEJB/TomEE distributions.
> >  ==
> > =
> >
> >This product includes software developed by
> >The Apache Software Foundation (http://www.apache.org/).
> >
> >Please read the different LICENSE files present in the licenses
> > directory of
> >this distribution.
> >
> > Apache TomEE is distributed in several distinct packages. We thank all
> the
> > developers of all the Software that help make up the Apache TomEE
> > distributions.
> >
> > This distribution contains, or may contain software developed by and
> > attributed
> > to the following organizations and individuals:
> >
> > ...
> >
> > One license file containing all potential licences that is used for
> > assemblies.
> >
> > Andy.
> >
> >
> > --
> >   Andy Gumbrecht
> >   https://twitter.com/AndyGeeDe
> >
> >
>

Re: [ANNOUNCE] Apache TomEE 7.0.0-M2 released

[Alex Soto]

Official Docker image coming.

El dt., 1 març 2016 a les 9:26, Jean-Louis Monteiro (<
jlmonte...@tomitribe.com>) va escriure:

> Yeah !
>
> Awesome Romain
>
>
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
> On Tue, Mar 1, 2016 at 9:06 AM, Romain Manni-Bucau 
> wrote:
>
> > The Apache Team Team is pleased to announce the availability of:
> >
> > Apache TomEE 7.0.0-M2
> >
> > Apache TomEE 7 targets JavaEE 7 with the simplicity of Apache TomEE.
> >
> > The release notes can be reviewed at:
> >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12312320&version=12332828
> >
> > Distribution packages can be downloaded from:
> > https://tomee.apache.org/download/tomee-7.0.0-M2.html
> >
> > When downloading, please verify signatures using the KEYS file available
> > at:
> > http://www.apache.org/dist/tomee
> >
> > Maven artifacts are also available in the central Maven repository.
> >
> > The Apache TomEE Team
> >
>

Re: [ANNOUNCE] Apache TomEE 7.0.0-M2 released

[Alex Soto]

Hi, it seems there is a problem with signatures:

100 33.2M  100 33.2M0 0   771k  0  0:00:44  0:00:44 --:--:--
1102k
+ gpg --verify tomee.tar.gz.asc tomee.tar.gz
gpg: Signature made Tue 23 Feb 2016 09:37:03 AM UTC using DSA key ID
F17D8FEF
gpg: Can't check signature: public key not found

The Dockerfile used has not changed ( apart from the URL). You can see the
template here:
https://github.com/tomitribe/docker-tomee/blob/master/Dockerfile.template

Is it possible that this information has not been populated yet?

El dt., 1 març 2016 a les 9:33, Alex Soto () va escriure:

> Official Docker image coming.
>
> El dt., 1 març 2016 a les 9:26, Jean-Louis Monteiro (<
> jlmonte...@tomitribe.com>) va escriure:
>
>> Yeah !
>>
>> Awesome Romain
>>
>>
>> --
>> Jean-Louis Monteiro
>> http://twitter.com/jlouismonteiro
>> http://www.tomitribe.com
>>
>> On Tue, Mar 1, 2016 at 9:06 AM, Romain Manni-Bucau > >
>> wrote:
>>
>> > The Apache Team Team is pleased to announce the availability of:
>> >
>> > Apache TomEE 7.0.0-M2
>> >
>> > Apache TomEE 7 targets JavaEE 7 with the simplicity of Apache TomEE.
>> >
>> > The release notes can be reviewed at:
>> >
>> >
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12312320&version=12332828
>> >
>> > Distribution packages can be downloaded from:
>> > https://tomee.apache.org/download/tomee-7.0.0-M2.html
>> >
>> > When downloading, please verify signatures using the KEYS file available
>> > at:
>> > http://www.apache.org/dist/tomee
>> >
>> > Maven artifacts are also available in the central Maven repository.
>> >
>> > The Apache TomEE Team
>> >
>>
>

Re: [ANNOUNCE] Apache TomEE 7.0.0-M2 released

[Alex Soto]

Download area, you can see in dockerfile.template file
El 1 mar. 2016 9:52 a. m., "Romain Manni-Bucau" 
escribió:

> Hi Alex,
>
> where do you take it from?
> http://repo.maven.apache.org/maven2/org/apache/tomee/apache-tomee/7.0.0-M2/
> or the download area?
>
>
> Romain Manni-Bucau
> @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> <http://rmannibucau.wordpress.com> | Github <
> https://github.com/rmannibucau> |
> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
> <http://www.tomitribe.com>
>
> 2016-03-01 9:47 GMT+01:00 Alex Soto :
>
> > Hi, it seems there is a problem with signatures:
> >
> > 100 33.2M  100 33.2M0 0   771k  0  0:00:44  0:00:44 --:--:--
> > 1102k
> > + gpg --verify tomee.tar.gz.asc tomee.tar.gz
> > gpg: Signature made Tue 23 Feb 2016 09:37:03 AM UTC using DSA key ID
> > F17D8FEF
> > gpg: Can't check signature: public key not found
> >
> > The Dockerfile used has not changed ( apart from the URL). You can see
> the
> > template here:
> >
> https://github.com/tomitribe/docker-tomee/blob/master/Dockerfile.template
> >
> > Is it possible that this information has not been populated yet?
> >
> > El dt., 1 març 2016 a les 9:33, Alex Soto () va
> > escriure:
> >
> > > Official Docker image coming.
> > >
> > > El dt., 1 març 2016 a les 9:26, Jean-Louis Monteiro (<
> > > jlmonte...@tomitribe.com>) va escriure:
> > >
> > >> Yeah !
> > >>
> > >> Awesome Romain
> > >>
> > >>
> > >> --
> > >> Jean-Louis Monteiro
> > >> http://twitter.com/jlouismonteiro
> > >> http://www.tomitribe.com
> > >>
> > >> On Tue, Mar 1, 2016 at 9:06 AM, Romain Manni-Bucau <
> > rmannibu...@gmail.com
> > >> >
> > >> wrote:
> > >>
> > >> > The Apache Team Team is pleased to announce the availability of:
> > >> >
> > >> > Apache TomEE 7.0.0-M2
> > >> >
> > >> > Apache TomEE 7 targets JavaEE 7 with the simplicity of Apache TomEE.
> > >> >
> > >> > The release notes can be reviewed at:
> > >> >
> > >> >
> > >>
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12312320&version=12332828
> > >> >
> > >> > Distribution packages can be downloaded from:
> > >> > https://tomee.apache.org/download/tomee-7.0.0-M2.html
> > >> >
> > >> > When downloading, please verify signatures using the KEYS file
> > available
> > >> > at:
> > >> > http://www.apache.org/dist/tomee
> > >> >
> > >> > Maven artifacts are also available in the central Maven repository.
> > >> >
> > >> > The Apache TomEE Team
> > >> >
> > >>
> > >
> >
>

Re: [ANNOUNCE] Apache TomEE 7.0.0-M2 released

[Alex Soto]

Let me try again then.

El dt., 1 març 2016 a les 12:06, Romain Manni-Bucau ()
va escriure:

>  » gpg --verify apache-tomee-7.0.0-M2-webprofile.tar.gz.asc
> apache-tomee-7.0.0-M2-webprofile.tar.gz
> gpg: Signature made Tue, Feb 23, 2016 10:37:03 AM CET using DSA key ID
> F17D8FEF
> gpg: Good signature from "Romain Manni-Bucau "
>
>
> Romain Manni-Bucau
> @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> <http://rmannibucau.wordpress.com> | Github <
> https://github.com/rmannibucau> |
> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
> <http://www.tomitribe.com>
>
> 2016-03-01 10:53 GMT+01:00 Alex Soto :
>
> > Download area, you can see in dockerfile.template file
> > El 1 mar. 2016 9:52 a. m., "Romain Manni-Bucau" 
> > escribió:
> >
> > > Hi Alex,
> > >
> > > where do you take it from?
> > >
> >
> http://repo.maven.apache.org/maven2/org/apache/tomee/apache-tomee/7.0.0-M2/
> > > or the download area?
> > >
> > >
> > > Romain Manni-Bucau
> > > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > > <http://rmannibucau.wordpress.com> | Github <
> > > https://github.com/rmannibucau> |
> > > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
> > > <http://www.tomitribe.com>
> > >
> > > 2016-03-01 9:47 GMT+01:00 Alex Soto :
> > >
> > > > Hi, it seems there is a problem with signatures:
> > > >
> > > > 100 33.2M  100 33.2M0 0   771k  0  0:00:44  0:00:44
> > --:--:--
> > > > 1102k
> > > > + gpg --verify tomee.tar.gz.asc tomee.tar.gz
> > > > gpg: Signature made Tue 23 Feb 2016 09:37:03 AM UTC using DSA key ID
> > > > F17D8FEF
> > > > gpg: Can't check signature: public key not found
> > > >
> > > > The Dockerfile used has not changed ( apart from the URL). You can
> see
> > > the
> > > > template here:
> > > >
> > >
> >
> https://github.com/tomitribe/docker-tomee/blob/master/Dockerfile.template
> > > >
> > > > Is it possible that this information has not been populated yet?
> > > >
> > > > El dt., 1 març 2016 a les 9:33, Alex Soto () va
> > > > escriure:
> > > >
> > > > > Official Docker image coming.
> > > > >
> > > > > El dt., 1 març 2016 a les 9:26, Jean-Louis Monteiro (<
> > > > > jlmonte...@tomitribe.com>) va escriure:
> > > > >
> > > > >> Yeah !
> > > > >>
> > > > >> Awesome Romain
> > > > >>
> > > > >>
> > > > >> --
> > > > >> Jean-Louis Monteiro
> > > > >> http://twitter.com/jlouismonteiro
> > > > >> http://www.tomitribe.com
> > > > >>
> > > > >> On Tue, Mar 1, 2016 at 9:06 AM, Romain Manni-Bucau <
> > > > rmannibu...@gmail.com
> > > > >> >
> > > > >> wrote:
> > > > >>
> > > > >> > The Apache Team Team is pleased to announce the availability of:
> > > > >> >
> > > > >> > Apache TomEE 7.0.0-M2
> > > > >> >
> > > > >> > Apache TomEE 7 targets JavaEE 7 with the simplicity of Apache
> > TomEE.
> > > > >> >
> > > > >> > The release notes can be reviewed at:
> > > > >> >
> > > > >> >
> > > > >>
> > > >
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12312320&version=12332828
> > > > >> >
> > > > >> > Distribution packages can be downloaded from:
> > > > >> > https://tomee.apache.org/download/tomee-7.0.0-M2.html
> > > > >> >
> > > > >> > When downloading, please verify signatures using the KEYS file
> > > > available
> > > > >> > at:
> > > > >> > http://www.apache.org/dist/tomee
> > > > >> >
> > > > >> > Maven artifacts are also available in the central Maven
> > repository.
> > > > >> >
> > > > >> > The Apache TomEE Team
> > > > >> >
> > > > >>
> > > > >
> > > >
> > >
> >
>

Re: [ANNOUNCE] Apache TomEE 7.0.0-M2 released

[Alex Soto]

I am getting exactly the same error. I send the Dockerfile so you can try
it by yourself. Doing a docker build -t tomee7 . should be enough

Alex.

El dt., 1 març 2016 a les 12:17, Alex Soto () va
escriure:

> Let me try again then.
>
> El dt., 1 març 2016 a les 12:06, Romain Manni-Bucau (<
> rmannibu...@gmail.com>) va escriure:
>
>>  » gpg --verify apache-tomee-7.0.0-M2-webprofile.tar.gz.asc
>> apache-tomee-7.0.0-M2-webprofile.tar.gz
>> gpg: Signature made Tue, Feb 23, 2016 10:37:03 AM CET using DSA key ID
>> F17D8FEF
>> gpg: Good signature from "Romain Manni-Bucau "
>>
>>
>> Romain Manni-Bucau
>> @rmannibucau <https://twitter.com/rmannibucau> |  Blog
>> <http://rmannibucau.wordpress.com> | Github <
>> https://github.com/rmannibucau> |
>> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
>> <http://www.tomitribe.com>
>>
>> 2016-03-01 10:53 GMT+01:00 Alex Soto :
>>
>> > Download area, you can see in dockerfile.template file
>> > El 1 mar. 2016 9:52 a. m., "Romain Manni-Bucau" 
>> > escribió:
>> >
>> > > Hi Alex,
>> > >
>> > > where do you take it from?
>> > >
>> >
>> http://repo.maven.apache.org/maven2/org/apache/tomee/apache-tomee/7.0.0-M2/
>> > > or the download area?
>> > >
>> > >
>> > > Romain Manni-Bucau
>> > > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
>> > > <http://rmannibucau.wordpress.com> | Github <
>> > > https://github.com/rmannibucau> |
>> > > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
>> > > <http://www.tomitribe.com>
>> > >
>> > > 2016-03-01 9:47 GMT+01:00 Alex Soto :
>> > >
>> > > > Hi, it seems there is a problem with signatures:
>> > > >
>> > > > 100 33.2M  100 33.2M0 0   771k  0  0:00:44  0:00:44
>> > --:--:--
>> > > > 1102k
>> > > > + gpg --verify tomee.tar.gz.asc tomee.tar.gz
>> > > > gpg: Signature made Tue 23 Feb 2016 09:37:03 AM UTC using DSA key ID
>> > > > F17D8FEF
>> > > > gpg: Can't check signature: public key not found
>> > > >
>> > > > The Dockerfile used has not changed ( apart from the URL). You can
>> see
>> > > the
>> > > > template here:
>> > > >
>> > >
>> >
>> https://github.com/tomitribe/docker-tomee/blob/master/Dockerfile.template
>> > > >
>> > > > Is it possible that this information has not been populated yet?
>> > > >
>> > > > El dt., 1 març 2016 a les 9:33, Alex Soto () va
>> > > > escriure:
>> > > >
>> > > > > Official Docker image coming.
>> > > > >
>> > > > > El dt., 1 març 2016 a les 9:26, Jean-Louis Monteiro (<
>> > > > > jlmonte...@tomitribe.com>) va escriure:
>> > > > >
>> > > > >> Yeah !
>> > > > >>
>> > > > >> Awesome Romain
>> > > > >>
>> > > > >>
>> > > > >> --
>> > > > >> Jean-Louis Monteiro
>> > > > >> http://twitter.com/jlouismonteiro
>> > > > >> http://www.tomitribe.com
>> > > > >>
>> > > > >> On Tue, Mar 1, 2016 at 9:06 AM, Romain Manni-Bucau <
>> > > > rmannibu...@gmail.com
>> > > > >> >
>> > > > >> wrote:
>> > > > >>
>> > > > >> > The Apache Team Team is pleased to announce the availability
>> of:
>> > > > >> >
>> > > > >> > Apache TomEE 7.0.0-M2
>> > > > >> >
>> > > > >> > Apache TomEE 7 targets JavaEE 7 with the simplicity of Apache
>> > TomEE.
>> > > > >> >
>> > > > >> > The release notes can be reviewed at:
>> > > > >> >
>> > > > >> >
>> > > > >>
>> > > >
>> > >
>> >
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12312320&version=12332828
>> > > > >> >
>> > > > >> > Distribution packages can be downloaded from:
>> > > > >> > https://tomee.apache.org/download/tomee-7.0.0-M2.html
>> > > > >> >
>> > > > >> > When downloading, please verify signatures using the KEYS file
>> > > > available
>> > > > >> > at:
>> > > > >> > http://www.apache.org/dist/tomee
>> > > > >> >
>> > > > >> > Maven artifacts are also available in the central Maven
>> > repository.
>> > > > >> >
>> > > > >> > The Apache TomEE Team
>> > > > >> >
>> > > > >>
>> > > > >
>> > > >
>> > >
>> >
>>
>

Re: reworking the website?

[Alex Soto]

The site is awesome, I would simply change the Apache TomEE Embedded or
distributed to another typography/style, but well I am not a designer, not
sure how to do it exactly.

El dt., 5 abr. 2016 a les 8:55, Romain Manni-Bucau ()
va escriure:

> done
>
> Romain Manni-Bucau
> @rmannibucau |  Blog | Github | LinkedIn | Tomitriber
>
>
> 2016-04-01 21:51 GMT+02:00 Romain Manni-Bucau :
> > if noone objects I'll move the new website to /ng/ next week.
> >
> > Romain Manni-Bucau
> > @rmannibucau |  Blog | Github | LinkedIn | Tomitriber
> >
> >
> > 2016-03-24 17:59 GMT+01:00 Romain Manni-Bucau :
> >> up, would be great to have some feedback to know if we can move
> >> forward, switching the website or exposing it as a subwebsite
> >>
> >> Romain Manni-Bucau
> >> @rmannibucau |  Blog | Github | LinkedIn | Tomitriber
> >>
> >>
> >> 2016-03-21 21:51 GMT+01:00 Romain Manni-Bucau :
> >>> Hi Rafael,
> >>>
> >>> that's interesting but still needs some manual writing ;). That said
> >>> the organisation could be the file system one and
> >>> http://tomee.apache.org/examples/ could be generated easily, good
> >>> point.
> >>>
> >>> My main concern and why I thought starting manually was good was to
> >>> avoid to just "cat" all sources in a page and expose it. This doesn't
> >>> promote why the sample has been written so it is like not having it.
> >>>
> >>> Finally with javaeeX-samples (think the 8 is on his way) wonder if we
> >>> shouldn't just merge our portable examples and only keep proprietary
> >>> ones moving tests of other examples to our main tests.
> >>>
> >>> Any opinion on that points (rewriting them to make it obvious):
> >>>
> >>> - removing portable examples and ensuring they are in javaee-sample
> >>> initiative without loosing in test coverage (if that's the case)
> >>> - avoid to generate examples without documentation
> >>> - reorganize the structure to match the category (we should surely
> >>> rework it to have spec + proprietary features + tests + tools as
> >>> subparts)
> >>>
> >>>
> >>> Romain Manni-Bucau
> >>> @rmannibucau |  Blog | Github | LinkedIn | Tomitriber
> >>>
> >>>
> >>> 2016-03-21 21:38 GMT+01:00 Rafael Pestano :
>  Hi Romain,
> 
>  Nice work, just two ideas about how the examples could be generated:
> 
>  1 - read from the tests as hibernate user guide is doing¹. Here is
> the guide
>  <
> https://github.com/hibernate/hibernate-orm/tree/master/documentation/src/main/asciidoc/userguide
> >
>  and the tests
>  <
> https://github.com/hibernate/hibernate-orm/tree/master/documentation/src/test/java/org/hibernate/userguide
> >
>  .
>  2 - read from a github repo and parse sources as javaee-support² is
> doing.
>  Here are the sources <
> https://github.com/javaee-samples/javaee7-samples>
>  and here
>  <
> https://github.com/javaee-samples/javaee-samples.github.io/blob/develop/_ext/asciidocify.rb
> >
>  is how they are parsed.
> 
> 
>  [1] http://hibernate.org/validator/documentation/getting-started/
>  [2] http://javaee.support/
> 
> 
>  2016-03-21 13:54 GMT-03:00 Jean-Louis Monteiro <
> jlmonte...@tomitribe.com>:
> 
> > I'll have a deeper look tonight Romain.
> > Thanks for putting more content in there. Might be useful to see how
> it
> > renders.
> >
> > --
> > Jean-Louis Monteiro
> > http://twitter.com/jlouismonteiro
> > http://www.tomitribe.com
> >
> > On Mon, Mar 21, 2016 at 1:38 PM, Romain Manni-Bucau <
> rmannibu...@gmail.com
> > >
> > wrote:
> >
> > > Hi guys,
> > >
> > > pushed some more content and GUI fixes. What about deploying it
> live
> > > on tomee.apache.org/site-ng/?
> > >
> > > Main missing part ATM is the example page but not sure how to
> tackle
> > > it. Think it should be a manual task cause anything generated
> either
> > > doesn't render well or doesn't serve the end users very well in
> term
> > > of content. Can try to start hacking few of them or if anyone
> wants to
> > > join the website hacking he is very welcomed.
> > >
> > >
> > > Romain Manni-Bucau
> > > @rmannibucau |  Blog | Github | LinkedIn | Tomitriber
> > >
> > >
> > > 2016-03-17 19:57 GMT+01:00 Romain Manni-Bucau <
> rmannibu...@gmail.com>:
> > > > Tried to push current state/idea to avoid you to have to build it
> > > > locally: http://home.apache.org/~rmannibucau/tomeeng/#
> > > >
> > > > Romain Manni-Bucau
> > > > @rmannibucau |  Blog | Github | LinkedIn | Tomitriber
> > > >
> > > >
> > > > 2016-03-17 11:57 GMT+01:00 Robert Panzer  >:
> > > >> Hi,
> > > >>
> > > >> even though not a committer I’d like to give my 2 cents on this:
> > > >>
> > > >> Regarding a GH* based workflow:
> > > >>
> > > >> Having provided some updates to the documentation recently I
> think the
> > > current process does not really promote contributions an

Re: reworking the website?

[Alex Soto]

Hehehe As I said I am very bad, the truth is that I won't be able to do
anything useful :D

El dt., 5 abr. 2016 a les 9:51, Romain Manni-Bucau ()
va escriure:

> here it is
> https://github.com/rmannibucau/site-tomee-ng/blob/master/src/main/jbake/assets/css/cardio.css#L61
> ,
> feel free to play with it ;)
>
> Romain Manni-Bucau
> @rmannibucau |  Blog | Github | LinkedIn | Tomitriber
>
>
> 2016-04-05 9:35 GMT+02:00 Alex Soto :
> > The site is awesome, I would simply change the Apache TomEE Embedded or
> > distributed to another typography/style, but well I am not a designer,
> not
> > sure how to do it exactly.
> >
> > El dt., 5 abr. 2016 a les 8:55, Romain Manni-Bucau (<
> rmannibu...@gmail.com>)
> > va escriure:
> >
> >> done
> >>
> >> Romain Manni-Bucau
> >> @rmannibucau |  Blog | Github | LinkedIn | Tomitriber
> >>
> >>
> >> 2016-04-01 21:51 GMT+02:00 Romain Manni-Bucau :
> >> > if noone objects I'll move the new website to /ng/ next week.
> >> >
> >> > Romain Manni-Bucau
> >> > @rmannibucau |  Blog | Github | LinkedIn | Tomitriber
> >> >
> >> >
> >> > 2016-03-24 17:59 GMT+01:00 Romain Manni-Bucau  >:
> >> >> up, would be great to have some feedback to know if we can move
> >> >> forward, switching the website or exposing it as a subwebsite
> >> >>
> >> >> Romain Manni-Bucau
> >> >> @rmannibucau |  Blog | Github | LinkedIn | Tomitriber
> >> >>
> >> >>
> >> >> 2016-03-21 21:51 GMT+01:00 Romain Manni-Bucau  >:
> >> >>> Hi Rafael,
> >> >>>
> >> >>> that's interesting but still needs some manual writing ;). That said
> >> >>> the organisation could be the file system one and
> >> >>> http://tomee.apache.org/examples/ could be generated easily, good
> >> >>> point.
> >> >>>
> >> >>> My main concern and why I thought starting manually was good was to
> >> >>> avoid to just "cat" all sources in a page and expose it. This
> doesn't
> >> >>> promote why the sample has been written so it is like not having it.
> >> >>>
> >> >>> Finally with javaeeX-samples (think the 8 is on his way) wonder if
> we
> >> >>> shouldn't just merge our portable examples and only keep proprietary
> >> >>> ones moving tests of other examples to our main tests.
> >> >>>
> >> >>> Any opinion on that points (rewriting them to make it obvious):
> >> >>>
> >> >>> - removing portable examples and ensuring they are in javaee-sample
> >> >>> initiative without loosing in test coverage (if that's the case)
> >> >>> - avoid to generate examples without documentation
> >> >>> - reorganize the structure to match the category (we should surely
> >> >>> rework it to have spec + proprietary features + tests + tools as
> >> >>> subparts)
> >> >>>
> >> >>>
> >> >>> Romain Manni-Bucau
> >> >>> @rmannibucau |  Blog | Github | LinkedIn | Tomitriber
> >> >>>
> >> >>>
> >> >>> 2016-03-21 21:38 GMT+01:00 Rafael Pestano :
> >> >>>> Hi Romain,
> >> >>>>
> >> >>>> Nice work, just two ideas about how the examples could be
> generated:
> >> >>>>
> >> >>>> 1 - read from the tests as hibernate user guide is doing¹. Here is
> >> the guide
> >> >>>> <
> >>
> https://github.com/hibernate/hibernate-orm/tree/master/documentation/src/main/asciidoc/userguide
> >> >
> >> >>>> and the tests
> >> >>>> <
> >>
> https://github.com/hibernate/hibernate-orm/tree/master/documentation/src/test/java/org/hibernate/userguide
> >> >
> >> >>>> .
> >> >>>> 2 - read from a github repo and parse sources as javaee-support² is
> >> doing.
> >> >>>> Here are the sources <
> >> https://github.com/javaee-samples/javaee7-samples>
> >> >>>> and here
> >> >>>> <
> >>
> https://github.com/javaee-samples/javaee-samples.github.io/blob/develop/_ext/asciidocify.rb
&g

Re: Next release 7.1?

[Alex Soto]

+1
El 23 abr. 2016 11:18 a. m., "Romain Manni-Bucau" 
escribió:

> Hi guys
>
> Having tomcat 8.5 now I d like to move tomee to 7.1 to show coming release
> is not just another 7.0.
>
> Any objection?
>

Re: Next release 7.1?

[Alex Soto]

Option 1 looks good to me.

El dl., 25 abr. 2016 a les 11:23, Jean-Louis Monteiro (<
jlmonte...@tomitribe.com>) va escriure:

> Works for me
>
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
> On Mon, Apr 25, 2016 at 11:21 AM, Romain Manni-Bucau <
> rmannibu...@gmail.com>
> wrote:
>
> > Anyone against option 1?
> >
> >
> > Romain Manni-Bucau
> > @rmannibucau  |  Blog
> >  | Github <
> > https://github.com/rmannibucau> |
> > LinkedIn  | Tomitriber
> >  | JavaEE Factory
> > 
> >
> > 2016-04-25 11:20 GMT+02:00 Jean-Louis Monteiro  >:
> >
> > > My 2 cts
> > >
> > > We have 3 milestones of the TomEE 7.0.0. People already using it are
> > > expecting a final version, and I agree with that.
> > >
> > > Tomcat 8.5 already integrated to master brings an important feature
> > HTTP/2
> > > we want to have and offer to our users. Tomcat 8.5 is fully backward
> > > compatible with Tomcat 8.x ( x < 5).
> > >
> > > So I don't see any issue in having TomEE 7.0.0 final released on the
> > master
> > > and already integrating Tomcat 8.5.
> > >
> > > I understand Romain's point to reflect Tomcat jump in terms of version,
> > but
> > > having a TomEE 7.1.0 would appear weird if we don't have a TomEE 7.0.0.
> > >
> > > If we really want to follow Romain's point and reflect the Tomcat
> > > versioning jump, I'd go with first a 7.0.0 based on the M3 with a
> couple
> > of
> > > bugfixes but with Tomcat 8.x (x < 5) and also a TomEE 7.1.0 with Tomcat
> > 8.x
> > > (x >= 5).
> > >
> > > So my view is
> > >
> > > Option 1/
> > > TomEE 7.0.0 with Tomcat 8.x (x >= 5) with HTTP/2
> > >
> > > *or*
> > >
> > > Option 2/
> > > TomEE 7.0.0 with Tomcat 8.x (x < 5) without HTTP/2
> > > +
> > > TomEE 7.1.0 with Tomcat 8.x (x >= 5) with HTTP/2
> > >
> > >
> > > *Side note*: we don't have any Java EE 7 TCK yet and I don't expect it
> to
> > > happen anytime soon.
> > > So even if not certified, I'd still go with a final release (non
> > certified)
> > > of TomEE
> > >
> > > Jean-Louis
> > >
> > >
> > > --
> > > Jean-Louis Monteiro
> > > http://twitter.com/jlouismonteiro
> > > http://www.tomitribe.com
> > >
> > > On Mon, Apr 25, 2016 at 11:02 AM, Martin Funk 
> > > wrote:
> > >
> > > > To my impression there are customers out there with an eye on TomEE
> to
> > > get
> > > > the JEE 7 certification.
> > > > And with the current version scheme they expect the TomEE 7.0 to be
> > JEE 7
> > > > conform, so in
> > > > my believe they'd be surprised to see an TomEE 7.1 version before 7.0
> > is
> > > > JEE 7.
> > > > They'd expect it to be JEE 7 conforming before bumping up the minor
> > > version
> > > > number.
> > > >
> > > > Technically I think I understand the issue and I could explain, if I
> > can
> > > > get into discussion with the customer.
> > > > The problem are the customers that you can't discuss with, that are
> > > scared
> > > > of before you get a chance to talk to them.
> > > >
> > > > mf
> > > >
> > > > 2016-04-25 10:12 GMT+02:00 Romain Manni-Bucau  >:
> > > >
> > > > > Le 25 avr. 2016 09:39, "Martin Funk"  a
> écrit
> > :
> > > > > >
> > > > > > A user's opinion here.
> > > > > > Getting TomEE to be JEE 7 compliant is a big obstical whereever I
> > go.
> > > > > > So releasing a 7.1 before 7.0 is JEE 7 compliant would lead to a
> > big
> > > > need
> > > > > > of explenaiton.
> > > > > >
> > > > >
> > > > > What does miss in this thread as explanation? Trying to get how
> > people
> > > > > percieve versions. They asked for our versioning page and now they
> > ask
> > > us
> > > > > to not respect it I understand - so hopefully I miss something ;)
> > > > >
> > > > > > People I talk to will not touch TomEE before it is JEE 7
> compliant.
> > > > > >
> > > > >
> > > > > That's not a blocker or do I miss anything?
> > > > >
> > > > > > mf
> > > > > >
> > > > > > 2016-04-25 4:00 GMT+02:00 John D. Ament :
> > > > > >
> > > > > > > On Sun, Apr 24, 2016 at 6:59 PM Romain Manni-Bucau <
> > > > > rmannibu...@gmail.com>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Le 25 avr. 2016 00:36, "John D. Ament" <
> johndam...@apache.org>
> > a
> > > > > écrit :
> > > > > > > > >
> > > > > > > > > It doesn't make sense to jump to a 7.1 immediately without
> > even
> > > > > > > releasing
> > > > > > > > a
> > > > > > > > > 7.0.  Just confusing from a semantic versioning standpoint.
> > > > > > > >
> > > > > > > > Do you think releasing a version which changes structurally
> > with
> > > > the
> > > > > same
> > > > > > > > minor is less confusing - was my fear ?
> > > > > > > >
> > > > > > >
> > > > > > > Maybe your fears aren't clear.  Granted I haven't tried tomcat
> > 8.5.
> > > > > Are
> > > > > > > you saying that using Tomcat 8.5 causes TomEE to have a
> different
> > > > > directory
> > > > > > > structure or somet

Re: TomEE 7 and JPA 2.1

[Alex Soto]

Hi Ivan what I would do will be droppng openjpa jars and add Hibernate
since it is the solution that IMHO most of the people use.

There is a doc in tomee website that explains it

Alex
El 26 abr. 2016 5:52 a. m., "Mitia Alexandrov" 
escribió:

> OpenJpa 2.1 is not ready. Use EclipseLink for JPA 2.1, its shipped with
> latest Plume :)
>
> вт, 26 апр. 2016, 2:08 Ivan St. Ivanov :
>
> > Hi folks,
> >
> > We will be running a series of workshops in Bulgarian JUG to develop our
> > new website. We'll be using Java EE 7 and TomEE 7. I know it is still
> > milestone release and not fully EE 7 compatible. But we decided to take
> the
> > "risk".
> >
> > In the app we are using the new schema generation annotations coming with
> > JPA 2.1, but they did not work. When I turned back to the old,
> > implementation specific ones, it worked.
> >
> > Did I get it wrong that none of the WebProfile or PLUME distributions
> > supports the JPA 2.1 spec? In the former I find OpenJPA 2.4.0, while in
> the
> > latter I see EclipseLink 2.4.2.
> >
> > Do you plan to provide JPA 2.1 support at least in the PLUME distro?
> >
> > Thanks,
> > Ivan
> >
> > P.S. Roberto sent me a couple of weeks ago instructions how to integrate
> > Hibernate JPA, but I would like to keep the configuration steps as few as
> > possible as there will be a lot of people that will have to do them
> during
> > the workshop
> >
>

Re: Exposing RESTful web services from WEB-INF/lib

[Alex Soto]

At mobile now but have you tried adding classes in war project and see if
they work and then extract to jar?

El 16 jul. 2016 4:34 p. m., "Ivan St. Ivanov" 
escribió:

> Hi folks,
>
> I have the following case. I am developing a simple web application, which
> is empty for the moment, but contains a jar that exposes RESTful web
> services via JAX-RS. Here is the structure:
>
> - actuator.jar: contains class extending javax.ws.rs.core.Application as
> well as a class annotated with @Path and containing a method annotated with
> @GET
> - actuator.war packages actuator.jar in WEB-INF/lib and apart from that is
> empty
>
> The source code is here:
> https://github.com/ivannov/javaee-actuator/tree/split
>
> I deployed this into TomEE 7.0.1 Plume and when I tried to access my
> RESTful resource, I got 404. I don't see anything in the catalina log. And
> these are the application deployment messages form the console:
>
> INFO - Enterprise application
> "/opt/apache-tomee-plume-7.0.1/webapps/actuator" loaded.
> INFO - Assembling app: /opt/apache-tomee-plume-7.0.1/webapps/actuator
> INFO - Deployed
> Application(path=/opt/apache-tomee-plume-7.0.1/webapps/actuator)
> INFO - At least one JAR was scanned for TLDs yet contained no TLDs. Enable
> debug logging for this logger for a complete list of JARs that were scanned
> but no TLDs were found in them. Skipping unneeded JARs during scanning can
> improve startup time and JSP compilation time.
> INFO - Deployment of web application archive
> /opt/apache-tomee-plume-7.0.1/webapps/actuator.war has finished in 1,808 ms
>
> The same works fine in Wildfly 10. It works OK on TomEE as well when
> actuator.jar is actually a war and deploy it directly.
>
> Do I have to do anything special in order to make resources packaged in
> WEB-INF/lib discoverable in TomEE?
>
> Thanks,
> Ivan
>

Re: ClassNotFoundException: com.sun.el.ExpressionFactoryImpl in embedded Arquillian container

[Alex Soto]

Are you using arquillian 1.1.11, if so try with .10

El 23 ago. 2016 10:47 p. m., "Ivan St. Ivanov" 
escribió:

> Hi folks,
>
> I have an issue when I run Arquillian test in the TomEE embedded
> container, version 7.0.1. Originally I wanted to run a test as client
> (@RunAsClient) that checks a RESTful web service's response [1]. However,
> during the deployment of the ShrinkWrap archive I get the following
> exception:
>
> javax.el.ELException: Provider com.sun.el.ExpressionFactoryImpl not found
> at javax.el.FactoryFinder.newInstance(FactoryFinder.java:101)
> at javax.el.FactoryFinder.find(FactoryFinder.java:197)
> at javax.el.ExpressionFactory.newInstance(ExpressionFactory.java:197)
> at javax.el.ExpressionFactory.newInstance(ExpressionFactory.java:168)
> at org.apache.jasper.runtime.JspApplicationContextImpl.(
> JspApplicationContextImpl.java:46)
> at org.apache.jasper.runtime.JspApplicationContextImpl.getInstance(
> JspApplicationContextImpl.java:76)
> at org.apache.jasper.runtime.JspFactoryImpl.getJspApplicationContext(
> JspFactoryImpl.java:217)
> at org.apache.openejb.cdi.OpenEJBLifecycle.setJspELFactory(
> OpenEJBLifecycle.java:416)
> at org.apache.openejb.cdi.OpenEJBLifecycle.initializeServletContext(
> OpenEJBLifecycle.java:387)
> at org.apache.tomee.catalina.TomcatWebAppBuilder.startInternal(
> TomcatWebAppBuilder.java:1423)
>
> The whole exception trace is attached to this emal.
>
> I wondered what the problem is, so I added a dummy resource [2] that
> doesn't involve CDI. And then ran a test [3] as client and it went fine.
> Then I added a test that doesn't run as client and involves a class that
> uses CDI [4]. And I got the same exception as above.
>
> Do you know what is the reason for the failure? The same tests run
> successfully on the WildFly 10 managed container. And they keep failing on
> TomEE embedded even with an empty beans.xml added to the ShrinkWrap web
> archive.
>
> The app under test is runnable under TomEE 7 Plume as well as via the
> Maven plugin.
>
> Thank you,
> Ivan
>
> [1] https://github.com/ivannov/javaee-actuator/blob/
> arquillian/javaee-actuator/src/test/java/io/github/
> ivannov/actuator/resources/MetricsResourceTest.java
> [2] https://github.com/ivannov/javaee-actuator/blob/
> arquillian/javaee-actuator/src/main/java/io/github/
> ivannov/actuator/resources/HelloResource.java
> [3] https://github.com/ivannov/javaee-actuator/blob/
> arquillian/javaee-actuator/src/test/java/io/github/
> ivannov/actuator/resources/HelloResourceTest.java
> [4] https://github.com/ivannov/javaee-actuator/blob/
> arquillian/javaee-actuator/src/test/java/io/github/
> ivannov/actuator/resources/BeansResourceTest.java
>

Re: ClassNotFoundException: com.sun.el.ExpressionFactoryImpl in embedded Arquillian container

[Alex Soto]

Then now I have no idea, it seems emedded instance does not contain the
javax.el interpreter. Can you try using remote artifacts?

El 23 ago. 2016 11:19 p. m., "Ivan St. Ivanov" 
escribió:

> Hey Alex :)
>
> I'm using the Arquillian Universe BOM Alpha 3. Downgraded to Alpha 2, but
> getting the same exception.
>
> Cheers,
> Ivan
>
> On Wed, Aug 24, 2016 at 12:15 AM, Alex Soto  wrote:
>
> > Are you using arquillian 1.1.11, if so try with .10
> >
> > El 23 ago. 2016 10:47 p. m., "Ivan St. Ivanov"  >
> > escribió:
> >
> > > Hi folks,
> > >
> > > I have an issue when I run Arquillian test in the TomEE embedded
> > > container, version 7.0.1. Originally I wanted to run a test as client
> > > (@RunAsClient) that checks a RESTful web service's response [1].
> However,
> > > during the deployment of the ShrinkWrap archive I get the following
> > > exception:
> > >
> > > javax.el.ELException: Provider com.sun.el.ExpressionFactoryImpl not
> > found
> > > at javax.el.FactoryFinder.newInstance(FactoryFinder.java:101)
> > > at javax.el.FactoryFinder.find(FactoryFinder.java:197)
> > > at javax.el.ExpressionFactory.newInstance(ExpressionFactory.java:197)
> > > at javax.el.ExpressionFactory.newInstance(ExpressionFactory.java:168)
> > > at org.apache.jasper.runtime.JspApplicationContextImpl.(
> > > JspApplicationContextImpl.java:46)
> > > at org.apache.jasper.runtime.JspApplicationContextImpl.getInstance(
> > > JspApplicationContextImpl.java:76)
> > > at org.apache.jasper.runtime.JspFactoryImpl.getJspApplicationContext(
> > > JspFactoryImpl.java:217)
> > > at org.apache.openejb.cdi.OpenEJBLifecycle.setJspELFactory(
> > > OpenEJBLifecycle.java:416)
> > > at org.apache.openejb.cdi.OpenEJBLifecycle.initializeServletContext(
> > > OpenEJBLifecycle.java:387)
> > > at org.apache.tomee.catalina.TomcatWebAppBuilder.startInternal(
> > > TomcatWebAppBuilder.java:1423)
> > >
> > > The whole exception trace is attached to this emal.
> > >
> > > I wondered what the problem is, so I added a dummy resource [2] that
> > > doesn't involve CDI. And then ran a test [3] as client and it went
> fine.
> > > Then I added a test that doesn't run as client and involves a class
> that
> > > uses CDI [4]. And I got the same exception as above.
> > >
> > > Do you know what is the reason for the failure? The same tests run
> > > successfully on the WildFly 10 managed container. And they keep failing
> > on
> > > TomEE embedded even with an empty beans.xml added to the ShrinkWrap web
> > > archive.
> > >
> > > The app under test is runnable under TomEE 7 Plume as well as via the
> > > Maven plugin.
> > >
> > > Thank you,
> > > Ivan
> > >
> > > [1] https://github.com/ivannov/javaee-actuator/blob/
> > > arquillian/javaee-actuator/src/test/java/io/github/
> > > ivannov/actuator/resources/MetricsResourceTest.java
> > > [2] https://github.com/ivannov/javaee-actuator/blob/
> > > arquillian/javaee-actuator/src/main/java/io/github/
> > > ivannov/actuator/resources/HelloResource.java
> > > [3] https://github.com/ivannov/javaee-actuator/blob/
> > > arquillian/javaee-actuator/src/test/java/io/github/
> > > ivannov/actuator/resources/HelloResourceTest.java
> > > [4] https://github.com/ivannov/javaee-actuator/blob/
> > > arquillian/javaee-actuator/src/test/java/io/github/
> > > ivannov/actuator/resources/BeansResourceTest.java
> > >
> >
>

Re: JSON-P 1.1?

[Alex Soto]

Just one thing JSONP 1.1 requires Java 8 meanwhile Java EE 7 (TomEE 7)
minimum JDK should be Java 7.

El dv., 28 d’abr. 2017 a les 10:29, Romain Manni-Bucau (<
rmannibu...@gmail.com>) va escriure:

> Hi guys,
>
> even if part of EE 8 do we want to upgrade JSON-P to 1.1 on TomEE 7?
>
> IMO it doesnt hurt and can enable new use cases like jsonpatch one for
> instance.
>
> Romain Manni-Bucau
> @rmannibucau  |  Blog
>  | Old Blog
>  | Github <
> https://github.com/rmannibucau> |
> LinkedIn  | JavaEE Factory
> 
>