Re: Max public methods EJB can expose.

2019-01-10 Thread Gurkan Erdogdu
Hi
I wonder why do you have 5000 public methods  in one class? Any specific
requirement?
Regards.
Gurkan

On Thu, Jan 10, 2019 at 4:25 PM Vincenzo D'Aniello <
ict.management.tre...@gmail.com> wrote:

>
> Hello everyone.
> Time ago, I was preparing a remote interface (@Remote), and this interface
> had to expose more than 5,000 public methods.
>
> Practically though, when tomee was deploying the .war, it gave 'size limit
> exceeded' error, making me understand that there is a maximum limit of
> public methods under EJB, or at most the implementation of OpenEJB has this
> limit.
>
> In fact, by limiting the methods to 2500, the error no longer appeared.
>
> My question is, where can I technically understand how many public methods
> I
> can expose and if there is a way to extend this limit, thank you.
>
>
>
> --
> Sent from:
> http://tomee-openejb.979440.n4.nabble.com/TomEE-Users-f979441.html
>


Re: TomEE 8.0.0 production version release date

2019-01-10 Thread Gurkan Erdogdu
Hello Sujan
Currently we have been actively working on TomEE 8 branch. It includes lots
of updates (especially on Microprofile ) and may not be ready for the
production usage. If you want to help us, you can start from
http://tomee.apache.org/community/contributing/contribution-tips.html
You can download the latest release,
http://tomee.apache.org/download-ng.html, test it in your environment and
let us know if you face with any problem. You can also take the latest
source code, generate your own release and test it.
Regards.
Gurkan

On Wed, Jan 9, 2019 at 12:09 PM Sujan Suppala  wrote:

> Hello,
>
> When TomEE 8.0.0 production version will be released?
>
> It will be great if you can provide approximate date or month .
>
> Thanks
> Sujan
>


Re: [ANNOUNCE] Apache TomEE 7.1.0 Released

2018-09-07 Thread Gurkan Erdogdu
Great work! Thank you!
Gurkan

On Fri, Sep 7, 2018 at 6:08 PM Jonathan Gallimore 
wrote:

> I'm pleased to announce the release of Apache TomEE 7.1.0.
>
> Apache TomEE delivers enterprise application containers and services based
> on, but not limited to the Enterprise JavaBeans Specification and Java
> Enterprise Edition Specifications.
>
> This latest release is based on TomEE 7.0.5, but based on Java 8, and
> includes support for the Configuration, JWT Propagation and Fault Tolerance
> Microprofile specifications
>
> The downloads are available from
> http://tomee.staging.apache.org/download-ng.html.
>
> Enjoy!
>
> The Apache TomEE team
>


Re: No Factories configured for this Application. This happens if the faces-initialization does not work at all

2018-07-16 Thread Gurkan Erdogdu
Hello Emmanuel
This exception sometimes (generally) occurred because of duplicate JSF jars
in your application and some classloader issues. Could you please check
your application that has any duplicate JSF (myfaces for example) JARS?
Regards.
Gurkan

On Mon, Jul 16, 2018 at 2:54 PM, Emmanuel Touzery <
emmanuel.touz...@lit-transit.com> wrote:

> Hello,
>
> we have a TOMEE 7.0.3 application, which uses also JMS, which works
> without issues. We've recently made a new version of the application (one
> of the notable changes is a migration from using the JMS1.1 to the JMS2
> API).
>
> With the new version, we have an issue, but only on our PROD
> environment, where we get no errors in the catalina.out log file (but the
> application doesn't work), but an error in the localhost log file, the
> error being as in the title of the email, I put the info from the localhost
> log file at the end of this email.
>
> I can't put the source on github or something like that,
> unfortunately. What is strange is that this error does not occur on our
> staging or UAT environments, but it does occur every time (well, we tried
> multiple times to restart the application and it failed consistently) on
> the PROD environment. We copied the entire PROD tomee folder on another
> machine and failed to reproduce the issue. We also tried to simulate
> incoming traffic when restarting the application, and run it against a
> backup of the PROD database... Somehow we can't reproduce the error. We are
> guessing that maybe the PROD traffic is higher than what we can simulate
> and some incoming message comes at just the wrong time? But we don't know
> for sure.
>
> Now, studying the issue, we realized that we used to have this in our
> src/main/webapp/WEB-INF/faces-config.xml:
>
> http://java.sun.com/xml/ns/javaee; xmlns:xsi="http://www.w3.org/2
> 001/XMLSchema-instance" xsi:schemaLocation="http://jav
> a.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/jav
> aee/web-facesconfig_2_1.xsd" version="2.1"> anaged-bean-name>login class>com.lecip.tms.tms_core.application.Login bean-class>view >
>
> We believe the JSF version is not correct for JEE7 anymore, in
> addition the managed-bean annotation is not necessary, so we changed the
> file to now contain:
>
> 
> http://xmlns.jcp.org/xml/ns/javaee;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee
> http://xmlns.jcp.org/xml/ns/javaee/web-facesconfig_2_2.xsd;
>   version="2.2">
> 
>
> Could this be the cause for that error that we saw in our PROD
> environment? Or you would think the root cause would be something else? The
> problem is that it's pretty difficult for us to experiment with changes
> since any deployment on PROD must be first validated on staging and UAT...
> Any hints? Is there maybe some logging configuration flag we could activate
> to get more information about the error? Or any other place to look to get
> more information about the issue?
>
> The irony is that we use JSF only for the login screen and nowhere
> else...
>
> Regards,
>
> Emmanuel
>
> 12-Jul-2018 17:44:04.335 SEVERE [localhost-startStop-1]
> org.apache.tomcat.util.descriptor.web.SecurityConstraint.findUncoveredHttpMethods
> For security constraints with URL pattern [/*] only the HTTP methods [TRACE
> HEAD DELETE POST GET OPTIONS PUT] are covered. All other methods are
> uncovered.
> 12-Jul-2018 17:44:22.078 SEVERE [localhost-startStop-1]
> org.apache.catalina.core.ApplicationContext.log StandardWrapper.Throwable
>  java.lang.IllegalStateException: No Factories configured for this
> Application. This happens if the faces-initialization does not work at all
> - make sure that you properly include all configuration settings necessary
> for a basic faces application and that all the necessary libs are included.
> Also check the logging output of your web application and your container
> for any exceptions!
> If you did that and find nothing, the mistake might be due to the fact
> that you use some special web-containers which do not support registering
> context-listeners via TLD files and a context listener is not setup in your
> web.xml.
> A typical config looks like this;
> 
> org.apache.myfaces.webapp.StartupServletCont
> extListener
> 
>
> at javax.faces.FactoryFinder._getFactory(FactoryFinder.java:305)
> at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:225)
> at javax.faces.webapp.FacesServlet.init(FacesServlet.java:115)
> at org.apache.catalina.core.StandardWrapper.initServlet(Standar
> dWrapper.java:1183)
> at org.apache.catalina.core.StandardWrapper.loadServlet(Standar
> dWrapper.java:1099)
> at org.apache.catalina.core.StandardWrapper.load(StandardWrappe
> r.java:989)
> at org.apache.catalina.core.StandardContext.loadOnStartup(Stand
> ardContext.java:4913)
> at org.apache.catalina.core.StandardContext.startInternal(Stand
> 

Re: Embedded TomEE 7.0.4 and Arquillian and TLS

2018-06-18 Thread Gurkan Erdogdu
Also added test patch.

On Mon, Jun 18, 2018 at 4:45 PM, Romain Manni-Bucau 
wrote:

> Misses a test (but looks good) and surely something to fix in
> https://github.com/apache/tomee/blob/master/tomee/tomee-
> embedded/src/test/java/org/apache/tomee/embedded/SslTomEETest.java
> since it should have tested it
>
> Romain Manni-Bucau
> @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> <https://rmannibucau.metawerx.net/> | Old Blog
> <http://rmannibucau.wordpress.com> | Github <https://github.com/
> rmannibucau> |
> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
> <https://www.packtpub.com/application-development/java-
> ee-8-high-performance>
>
>
> Le lun. 18 juin 2018 à 15:39, Gurkan Erdogdu  a
> écrit :
>
> > Also added patch :)
> >
> > On Mon, Jun 18, 2018 at 4:37 PM, Gurkan Erdogdu 
> > wrote:
> >
> > > Hello
> > > I created the issue https://issues.apache.org/jira/browse/TOMEE-2196
> > > Best
> > > Gurkan
> > >
> > > On Mon, Jun 18, 2018 at 4:29 PM, Romain Manni-Bucau <
> > rmannibu...@gmail.com
> > > > wrote:
> > >
> > >> Hi Fabian,
> > >>
> > >> there is a bug for keystorefile, the property name is empty (
> > >> https://github.com/apache/tomee/blob/fb_tomee8/tomee/tomee-
> > >> embedded/src/main/java/org/apache/tomee/embedded/
> Container.java#L632),
> > >> feel free to submit a PR fixing that
> > >>
> > >> Romain Manni-Bucau
> > >> @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > >> <https://rmannibucau.metawerx.net/> | Old Blog
> > >> <http://rmannibucau.wordpress.com> | Github <
> > >> https://github.com/rmannibucau> |
> > >> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
> > >> <https://www.packtpub.com/application-development/java-ee-8-
> > >> high-performance>
> > >>
> > >>
> > >> Le lun. 18 juin 2018 à 14:55,  a
> > >> écrit :
> > >>
> > >> > Hi,
> > >> >
> > >> >
> > >> >
> > >> > I am migrating to TomEE 7.0.4 and our old TLS config in
> arquillian.xml
> > >> is
> > >> > not working any longer, the property
> > >> >
> > >> >
> > >> >
> > >> > property name="keystoreFile"
> > >> >
> > >> >
> > >> >
> > >> > seems to be ignored completely now, and ~/.keystore used instead.
> What
> > >> is
> > >> > the replacement? Where do I find documentation on arquillian.xml
> which
> > >> is
> > >> > up to date for the TomEE embedded driver?
> > >> >
> > >> >
> > >> >
> > >> > Thanks in advance and best
> > >> >
> > >> > Fabian
> > >> >
> > >> >
> > >> >
> > >> >
> > >> >
> > >>
> > >
> > >
> >
>


Re: Embedded TomEE 7.0.4 and Arquillian and TLS

2018-06-18 Thread Gurkan Erdogdu
Also added patch :)

On Mon, Jun 18, 2018 at 4:37 PM, Gurkan Erdogdu  wrote:

> Hello
> I created the issue https://issues.apache.org/jira/browse/TOMEE-2196
> Best
> Gurkan
>
> On Mon, Jun 18, 2018 at 4:29 PM, Romain Manni-Bucau  > wrote:
>
>> Hi Fabian,
>>
>> there is a bug for keystorefile, the property name is empty (
>> https://github.com/apache/tomee/blob/fb_tomee8/tomee/tomee-
>> embedded/src/main/java/org/apache/tomee/embedded/Container.java#L632),
>> feel free to submit a PR fixing that
>>
>> Romain Manni-Bucau
>> @rmannibucau <https://twitter.com/rmannibucau> |  Blog
>> <https://rmannibucau.metawerx.net/> | Old Blog
>> <http://rmannibucau.wordpress.com> | Github <
>> https://github.com/rmannibucau> |
>> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
>> <https://www.packtpub.com/application-development/java-ee-8-
>> high-performance>
>>
>>
>> Le lun. 18 juin 2018 à 14:55,  a
>> écrit :
>>
>> > Hi,
>> >
>> >
>> >
>> > I am migrating to TomEE 7.0.4 and our old TLS config in arquillian.xml
>> is
>> > not working any longer, the property
>> >
>> >
>> >
>> > property name="keystoreFile"
>> >
>> >
>> >
>> > seems to be ignored completely now, and ~/.keystore used instead. What
>> is
>> > the replacement? Where do I find documentation on arquillian.xml which
>> is
>> > up to date for the TomEE embedded driver?
>> >
>> >
>> >
>> > Thanks in advance and best
>> >
>> > Fabian
>> >
>> >
>> >
>> >
>> >
>>
>
>


Re: Embedded TomEE 7.0.4 and Arquillian and TLS

2018-06-18 Thread Gurkan Erdogdu
Hello
I created the issue https://issues.apache.org/jira/browse/TOMEE-2196
Best
Gurkan

On Mon, Jun 18, 2018 at 4:29 PM, Romain Manni-Bucau 
wrote:

> Hi Fabian,
>
> there is a bug for keystorefile, the property name is empty (
> https://github.com/apache/tomee/blob/fb_tomee8/tomee/
> tomee-embedded/src/main/java/org/apache/tomee/embedded/Container.java#L632
> ),
> feel free to submit a PR fixing that
>
> Romain Manni-Bucau
> @rmannibucau  |  Blog
>  | Old Blog
>  | Github  rmannibucau> |
> LinkedIn  | Book
>  ee-8-high-performance>
>
>
> Le lun. 18 juin 2018 à 14:55,  a
> écrit :
>
> > Hi,
> >
> >
> >
> > I am migrating to TomEE 7.0.4 and our old TLS config in arquillian.xml is
> > not working any longer, the property
> >
> >
> >
> > property name="keystoreFile"
> >
> >
> >
> > seems to be ignored completely now, and ~/.keystore used instead. What is
> > the replacement? Where do I find documentation on arquillian.xml which is
> > up to date for the TomEE embedded driver?
> >
> >
> >
> > Thanks in advance and best
> >
> > Fabian
> >
> >
> >
> >
> >
>


Re: Get JDBC pool capacity

2016-10-28 Thread Gurkan Erdogdu
> This is not true...depends 1. the usage, 2. the type of datasource
> 
> Also note we don't use dbcp but dbcp2 which got updated compared to dbcp 1on 
> several aspect 
I mean dbcp2 and it is a some bit preference to use dbcp2 or tomcat jdbc. But 
from our experience tomcat-jdbc is much faster and easy to work/debug
Could you give some example scenario of using dbcp2 against tomcat jdbc?

Gurkan-

> On 29 Oct 2016, at 00:13, Romain Manni-Bucau <rmannibu...@gmail.com> wrote:
> 
> 2016-10-28 23:10 GMT+02:00 Gurkan Erdogdu <gerdo...@managecat.com>:
> 
>> Hi
>> 
>> DBCP is not a good option against default one Tomcat JDBC Pool. I suggest
>> to stick with Tomcat JDBC Pool implementation against Common DBCP you set.
>> You can read more about Tomcat JDBC Pool in here,
>> http://tomcat.apache.org/tomcat-7.0-doc/jdbc-pool.html <
>> http://tomcat.apache.org/tomcat-7.0-doc/jdbc-pool.html>
>> 
> 
> This is not true...depends 1. the usage, 2. the type of datasource
> 
> Also note we don't use dbcp but dbcp2 which got updated compared to dbcp 1
> on several aspects.
> 
> 
>> 
>> Best
>> Gurkan
>> http://managecat.com <http://managecat.com/>
>> 
>>> On 29 Oct 2016, at 00:04, Zachary Bedell <zbed...@nycourts.gov> wrote:
>>> 
>>> As far as I know, I didn't do anything to change the pooling
>> implementation.
>>> 
>>> It does all start working if I add an explicit "DataSourceCreator dbcp"
>> to my datasource definitions in resource.xml.  With that, the datasources
>> section shows up in JMX, and I see all the stats I need.
>>> 
>>> I found a suggestion on this page (https://rmannibucau.
>> wordpress.com/2012/08/10/switching-of-datasource-connection-pooling-in-
>> tomeeopenejb/) that adding "openejb.jdbc.datasource-creator = dbcp" to
>> system.properties should do the same globally, but that didn't work for
>> me.  Adding that & removing the DataSourceCreator entry went back to no
>> stats.  Maybe there's any updated name for that property?
>>> 
>>> Not sure what about my config breaks the default configuration, but this
>> looks like it should do the trick for now.
>>> 
>>> Thanks for the pointers!
>>> 
>>> -Zac
>>> 
>>> 
>>> On Oct 28, 2016, at 16:14, Romain Manni-Bucau <rmannibu...@gmail.com
>> <mailto:rmannibu...@gmail.com>> wrote:
>>> 
>>> weird, try to reproduce your setup on github I'll check next week
>>> 
>>> only case I'm thiking about is you don't use dbcp or tomcat-jdbc pooling
>>> 
>>> 
>>> Romain Manni-Bucau
>>> @rmannibucau <https://twitter.com/rmannibucau> |  Blog
>>> <https://blog-rmannibucau.rhcloud.com<https://blog-
>> rmannibucau.rhcloud.com/>> | Old Blog
>>> <http://rmannibucau.wordpress.com<http://rmannibucau.wordpress.com/>> |
>> Github <https://github.com/rmannibucau> |
>>> LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
>>> <https://javaeefactory-rmannibucau.rhcloud.com> //javaeefactory-rmannibucau.rhcloud.com/>>
>>> 
>>> 2016-10-28 22:12 GMT+02:00 Zachary Bedell <zbed...@nycourts.gov> bed...@nycourts.gov>>:
>>> 
>>> That doesn't exist for me at all in jconsole.
>>> 
>>> Screenshot: http://imgur.com/a/5mMgz
>>> 
>>> If I enumerate JMX using an ObjectName of "openejb.management:*" with
>>> something like the code below, there's no "datasources" in any of the
>> found
>>> objects.  Nothing matching the names of my pools either.
>>> 
>>> final ObjectName name = new ObjectName("openejb.management:*");
>>> final Set search = mbeanServer.queryMBeans(name, null);
>>> for(final ObjectInstance objectInstance : search) {
>>> System.out.println(objectInstance.getObjectName().getCanonicalName());
>>> }
>>> 
>>> -Zac
>>> 
>>> On Oct 28, 2016, at 15:55, Romain Manni-Bucau <rmannibu...@gmail.com
>> <mailto:rmannibu...@gmail.com>
>>> <mailto:rmannibu...@gmail.com>> wrote:
>>> 
>>> openejb.management > datasources
>>> 
>>> 
>>> 
>>> Romain Manni-Bucau
>>> @rmannibucau <https://twitter.com/rmannibucau> |  Blog
>>> <https://blog-rmannibucau.rhcloud.com<https://blog-
>> rmannibucau.rhcloud.com/>> | Old Blog
>>> <http://rmannibucau.wordpress.com<http://rmannibucau.wordpress

Re: Get JDBC pool capacity

2016-10-28 Thread Gurkan Erdogdu
Hi

DBCP is not a good option against default one Tomcat JDBC Pool. I suggest to 
stick with Tomcat JDBC Pool implementation against Common DBCP you set. You can 
read more about Tomcat JDBC Pool in here, 
http://tomcat.apache.org/tomcat-7.0-doc/jdbc-pool.html 


Best
Gurkan
http://managecat.com 

> On 29 Oct 2016, at 00:04, Zachary Bedell  wrote:
> 
> As far as I know, I didn't do anything to change the pooling implementation.
> 
> It does all start working if I add an explicit "DataSourceCreator dbcp" to my 
> datasource definitions in resource.xml.  With that, the datasources section 
> shows up in JMX, and I see all the stats I need.
> 
> I found a suggestion on this page 
> (https://rmannibucau.wordpress.com/2012/08/10/switching-of-datasource-connection-pooling-in-tomeeopenejb/)
>  that adding "openejb.jdbc.datasource-creator = dbcp" to system.properties 
> should do the same globally, but that didn't work for me.  Adding that & 
> removing the DataSourceCreator entry went back to no stats.  Maybe there's 
> any updated name for that property?
> 
> Not sure what about my config breaks the default configuration, but this 
> looks like it should do the trick for now.
> 
> Thanks for the pointers!
> 
> -Zac
> 
> 
> On Oct 28, 2016, at 16:14, Romain Manni-Bucau 
> > wrote:
> 
> weird, try to reproduce your setup on github I'll check next week
> 
> only case I'm thiking about is you don't use dbcp or tomcat-jdbc pooling
> 
> 
> Romain Manni-Bucau
> @rmannibucau  |  Blog
> > 
> | Old Blog
> > | 
> Github  |
> LinkedIn  | JavaEE Factory
> >
> 
> 2016-10-28 22:12 GMT+02:00 Zachary Bedell 
> >:
> 
> That doesn't exist for me at all in jconsole.
> 
> Screenshot: http://imgur.com/a/5mMgz
> 
> If I enumerate JMX using an ObjectName of "openejb.management:*" with
> something like the code below, there's no "datasources" in any of the found
> objects.  Nothing matching the names of my pools either.
> 
> final ObjectName name = new ObjectName("openejb.management:*");
> final Set search = mbeanServer.queryMBeans(name, null);
> for(final ObjectInstance objectInstance : search) {
> System.out.println(objectInstance.getObjectName().getCanonicalName());
> }
> 
> -Zac
> 
> On Oct 28, 2016, at 15:55, Romain Manni-Bucau 
> 
> > wrote:
> 
> openejb.management > datasources
> 
> 
> 
> Romain Manni-Bucau
> @rmannibucau  |  Blog
> > 
> | Old Blog
> > | 
> Github  rmannibucau> |
> LinkedIn  | JavaEE Factory
> >
> 
> 2016-10-28 21:41 GMT+02:00 Zachary Bedell 
>  bed...@nycourts.gov>>:
> 
> Would the stats show up in a different part of the tree?  I don't see the
> datasources entry at all under openejb.management.
> 
> I can find DataSourceFactory objects under:
> 
> Catalina:class=org.apache.openejb.resource.jdbc.DataSourceFactory,name="
> EARNAME/POOLNAME",resourcetype=Global,type=Resource
> 
> 
> The DataSource's themselves show up in every WAR they're injected into:
> 
> Catalina:type=DataSource,host=localhost,context=/WARNAME,
> class=javax.sql.DataSource,name="openejb/Resource/POOLNAME"
> 
> 
> Neither the DataSource nor DataSourceFactory expose anything that looks
> like active or max connections.
> 
> We're trying pretty hard to keep everything related to the app in its own
> EAR rather than globally in tomee.xml.  So far the only thing we have in
> tomee.xml is a  entry where we're dropping the EAR's.
> 
> -Zac
> 
> On Oct 28, 2016, at 15:28, Romain Manni-Bucau 
> 
> >
> wrote:
> 
> they are, name is just prefixed with app name
> 
> 
> Romain Manni-Bucau
> @rmannibucau  |  Blog
> > 
> | Old Blog
> > | 
> Github  rmannibucau> |
> LinkedIn  | JavaEE Factory
> 

Re: JSP named bean bug

2016-10-17 Thread Gurkan Erdogdu
Hi 

Just I tried with 7.0.2-SNAPHOT and it works perfectly :)

Best

Gurkan Erdogdu
http://twitter.com/gerdogdu <http://twitter.com/gerdogdu>
http://managecat.com <http://managecat.com/>

> On 17 Oct 2016, at 17:47, tonywestonuk <to...@totspics.com> wrote:
> 
> There... pretty straight forward.
> 
> https://github.com/tonywestonuk/tomeebug
> 
> 
> It affects 7.0.1
> 
> 
> 
> 
> 
> --
> View this message in context: 
> http://tomee-openejb.979440.n4.nabble.com/JSP-named-bean-bug-tp4680338p4680342.html
> Sent from the TomEE Users mailing list archive at Nabble.com.




Re: Question about Java EE certification TomEE and Plume

2016-01-15 Thread Gurkan Erdogdu
I mean EE 7 and above TCK

Sent from my iPhone

> On 15 Oca 2016, at 14:30, Andy Gumbrecht <agumbre...@tomitribe.com> wrote:
> 
> The ASF does have access to the EE6 TCK, and TomEE is always tested before
> a release.
> 
> So when ASF TomEE states that a TomEE distribution is Webprofile certified
> then you can be sure that it is.
> 
> @Devs  If we run PLUME through the TCK then surely that distribution would
> at least be a 'both' Webprofile certified & other JSR compatible solution?
> 
> Andy.
> 
>> On 14 January 2016 at 20:17, Gurkan Erdogdu <gerdo...@managecat.com> wrote:
>> 
>> To my knowledge, no, it is not the same. Actually without accessing TCK
>> suite ( and required to become a licensee of Oracle) , you can not use any
>> test and say that blabla server is compatible. Currently ASF is not
>> licensee of Oracle so no project in ASF can have access to TCK suite.
>> 
>> Best
>> Gurkan
>> 
>> Sent from my iPhone
>> 
>>> On 14 Oca 2016, at 20:45, Mark Struberg <strub...@yahoo.de> wrote:
>>> 
>>> With other words, most of the other vendor packages are strictly seen
>> also not ‚certified‘ but only ‚compliant‘.
>>> Which makes them not bad - it’s just that the terms often get mixed up
>> by marketing (knowingly or not? I don’t know) and confuse users.
>>> 
>>> LieGrue,
>>> strub
>>> 
>>> 
>>>> Am 11.01.2016 um 23:04 schrieb David Blevins <david.blev...@gmail.com>:
>>>> 
>>>> Correct and to be clear, there are two distinct words
>>>> 
>>>> - Certified = formal acknowledgement from Oracle for passing the Web
>> Profile or Full Profile TCK.  Oracle offers no other form of certification.
>>>> - Compliant = passes the respective tests or conforms to the related
>> spec.
>>>> 
>>>> In the majority of the thread the word “certified” is being used where
>> really “compliant” is more appropriate.
>>>> 
>>>> Per certification rules, there are just the two profiles (Web and
>> Full).  To be Web Profile certified by Oracle you have to implement and
>> pass the Web Profile technologies and ONLY the Web Profile technologies.
>> If you go one inch further and add JAX-WS, JMS or anything else, you cannot
>> call it “certified” even if you pass the respective tests.
>>>> 
>>>> If we wanted to have a Java EE 6 Web Profile certified version of TomEE
>> 1.x that includes EclipseLink and Mojarra, we could do that, but we’d have
>> to remove JAX-RS, JAX-WS, and JMS from the box as none of those are in the
>> Web Profile.
>>>> 
>>>> 
>>>> --
>>>> David Blevins
> 
> 
> 
> -- 
>  Andy Gumbrecht
>  https://twitter.com/AndyGeeDe
>  http://www.tomitribe.com


Re: Question about Java EE certification TomEE and Plume

2016-01-14 Thread Gurkan Erdogdu
To my knowledge, no, it is not the same. Actually without accessing TCK suite ( 
and required to become a licensee of Oracle) , you can not use any test and say 
that blabla server is compatible. Currently ASF is not licensee of Oracle so no 
project in ASF can have access to TCK suite.

Best
Gurkan

Sent from my iPhone

> On 14 Oca 2016, at 20:45, Mark Struberg  wrote:
> 
> With other words, most of the other vendor packages are strictly seen also 
> not ‚certified‘ but only ‚compliant‘.
> Which makes them not bad - it’s just that the terms often get mixed up by 
> marketing (knowingly or not? I don’t know) and confuse users.
> 
> LieGrue,
> strub
> 
> 
>> Am 11.01.2016 um 23:04 schrieb David Blevins :
>> 
>> Correct and to be clear, there are two distinct words
>> 
>> - Certified = formal acknowledgement from Oracle for passing the Web Profile 
>> or Full Profile TCK.  Oracle offers no other form of certification.
>> - Compliant = passes the respective tests or conforms to the related spec.
>> 
>> In the majority of the thread the word “certified” is being used where 
>> really “compliant” is more appropriate.
>> 
>> Per certification rules, there are just the two profiles (Web and Full).  To 
>> be Web Profile certified by Oracle you have to implement and pass the Web 
>> Profile technologies and ONLY the Web Profile technologies.  If you go one 
>> inch further and add JAX-WS, JMS or anything else, you cannot call it 
>> “certified” even if you pass the respective tests.
>> 
>> If we wanted to have a Java EE 6 Web Profile certified version of TomEE 1.x 
>> that includes EclipseLink and Mojarra, we could do that, but we’d have to 
>> remove JAX-RS, JAX-WS, and JMS from the box as none of those are in the Web 
>> Profile.
>> 
>> 
>> -- 
>> David Blevins


Re: Question about Java EE certification TomEE and Plume

2016-01-11 Thread Gurkan Erdogdu
Hi Francois

Only Java EE 6 web profile had been certified in TomEE which includes 
WebProfile + JAX-RS.

Regards.

Gurkan Erdogdu  
Founder, ManageCat 
p. +1 (909) - 366 – 9337
a. 340 S Lemon Ave #7996 Walnut, CA 91789
w. http://managecat.com
e gerdo...@managecat.com

> On 11 Jan 2016, at 09:58, COURTAULT Francois <francois.courta...@gemalto.com> 
> wrote:
> 
> Hello Romain,
> 
> If you go to http://tomee.apache.org/ you will see, in that page, that, for 
> Plume, it is written NOT Java EE6 Certified.
> So mistake in the tomee main page  ?
> 
> Best Regards.
> 
> -Original Message-
> From: Romain Manni-Bucau [mailto:rmannibu...@gmail.com]
> Sent: lundi 28 décembre 2015 13:50
> To: users@tomee.apache.org
> Subject: Re: Question about Java EE certification TomEE and Plume
> 
> Plume has been certified for ee6.
> 
> Now as default provider i hope to stick to openjpa as much as possible to not 
> break hundreds of applications.
> Le 28 déc. 2015 13:00, "Yann Blazart" <yann.blaz...@bycode.fr> a écrit :
> 
>> Hello, from my point of view, there's no problem.
>> 
>> You can change the JPA implementation following your needs, put
>> Hibernate for example.
>> 
>> I can garanty you that all my products running on webspehere and
>> weblogic was able to run in tomee. Sometimes some "proprietary" config
>> files to write or change, but this is part of Java EE specs.
>> 
>> You can test TomEE 7.0.0-M1, it's nearly readed to be released, and
>> it's a fantastic EE 7 server !
>> 
>> 2015-12-28 12:30 GMT+01:00 COURTAULT Francois <
>> francois.courta...@gemalto.com>:
>> 
>>> Hello everyone,
>>> 
>>> TomEE is quite nice but one thing which annoys me is about
>>> certification using EclipseLink.
>>> 
>>> Let me explain my concern:
>>> Some application servers like Weblogic and even Liberty, quite
>>> recently, uses EclipseLink as the JPA layer.
>>> But If I look at the TomEE docs, only the Plume delivery contains
>>> EclipseLink as the JPA layer, but this one is not Java EE 6 certified.
>>> 
>>> Just want to know, if there are future plans in order to have JAX-RS
>>> delivery be Java EE 6 or Java EE 7 web profile certified but using
>>> EclipselInk (alternative to OpenJPA) as the JPA layer ?
>>> I ask this question  because it will most probably ease our
>>> migration
>> from
>>> some commercial app vendors to TomEE.
>>> 
>>> Best Regards.
>>> 
>>> This message and any attachments are intended solely for the
>>> addressees and may contain confidential information. Any
>>> unauthorized use or disclosure, either whole or partial, is prohibited.
>>> E-mails are susceptible to alteration. Our company shall not be
>>> liable
>> for
>>> the message if altered, changed or falsified. If you are not the
>>> intended recipient of this message, please delete it and notify the sender.
>>> Although all reasonable efforts have been made to keep this
>>> transmission free from viruses, the sender will not be liable for
>>> damages caused by a transmitted virus.
>>> 
>> 
> 
> This message and any attachments are intended solely for the addressees and 
> may contain confidential information. Any unauthorized use or disclosure, 
> either whole or partial, is prohibited.
> E-mails are susceptible to alteration. Our company shall not be liable for 
> the message if altered, changed or falsified. If you are not the intended 
> recipient of this message, please delete it and notify the sender.
> Although all reasonable efforts have been made to keep this transmission free 
> from viruses, the sender will not be liable for damages caused by a 
> transmitted virus.
 



Re: Opinion on project infrastructure

2015-09-17 Thread Gurkan Erdogdu
Hello Arthur

This topic is more than application server selection. You can use the best 
application server in the world but if your architecture (including 
scalability, security, failover etc. ) is not designed well from the beginning 
of your project, you may be in trouble. It is also very important to understant 
what you mean by “respond in real-time?” Real time respond in 1 ms, 10 secs, 
150 ns ?

You have to consider:

- Web servers with HA in mind (for HTML, CSS, JS static delivery, example : 
Nginx, Apache)
- Using CDN (delivering your static contents, images etc. faster and also with 
no downtime)
- Security from start (XSS attacks, DNS attacks etc.)
- Clustered databases for scalable RW 
- Clustered application servers for failure, HA scenarios
- In memory /distributed caches to cache mostly used stuff
- Client side or server side rendering platforms (JSF or Angular JS with 
Bootstrap etc.)
- WebSocket frameworks (if you use web sockets but it is not globally accepted 
standard yet)
- Also, your architecture must allow you to scale your instances proportional 
to your application workload etc.

As you see, there are lots of consideration to implement such a big system 
irrespective of the application server you use.

Best.

Gurkan Erdogdu  
Founder, ManageCat
p. +1 (909) - 366 – 9337
a. 340 S Lemon Ave #7996 Walnut, CA 91789
w. http://managecat.com <http://managecat.com/>
e gerdo...@managecat.com <mailto:gerdo...@managecat.com>
 <http://twitter.com/gerdogdu>  <https://tr.linkedin.com/in/gerdogdu>

> On 16 Sep 2015, at 23:20, Arthur Portas <arthur.por...@itsector.pt> wrote:
> 
> Hi,
> 
> to deal with a scenario like this:
> "develop a system capable of scaling to support the load of dozens of
> countries , and algorithms able to respond in real -time"
> what would be your suggestions to draw such a system architecture with
> TomEE?
> 
> Love to hear our thoughts!
> 
> Cheers,
> 
> Arthur Portas




Re: a curiosity: is possible call a remote ejb on glassfsih from tomee and vice versa?

2015-09-17 Thread Gurkan Erdogdu
you can put WEB-INF/lib if only one application use or tomee/lib if more than 
one :)

you only put the Glassfish related jars so no conflict occurs

Best

Gurkan
> On 17 Sep 2015, at 09:23, mauro2java2011 <mauro2java2...@gmail.com> wrote:
> 
> But the glassfish client  jars i havr to put into  wrb-inf/lib of war or
> into tomer/lib ?
> 
> If i  put  the jars into tomee/lib can collide with the clasd of tomee ?
> Il 16/set/2015 19:17, "Gurkan Erdogdu-4 [via TomEE & OpenEJB]" <
> ml-node+s979440n4676267...@n4.nabble.com> ha scritto:
> 
>> Hello Mauro
>> 
>> AFAIK OpenEJB uses its own binary remote protocol, not CORBA or RMI/JRMP
>> etc. So, it may not possible to communicate from OpenEJB to Glassfish but
>> if you have Glassfish client jars to access glass fish remote EJBS, you can
>> use these clients to access them in TomEE.
>> 
>> Best
>> 
>> Gurkan Erdogdu
>> Founder, ManageCat
>> p. +1 (909) - 366 – 9337
>> a. 340 S Lemon Ave #7996 Walnut, CA 91789
>> w. http://managecat.com
>> e [hidden email] <http:///user/SendEmail.jtp?type=node=4676267=0>
>> <http://twitter.com/gerdogdu>  <https://tr.linkedin.com/in/gerdogdu>
>> 
>> On 16 Sep 2015, at 19:51, mauro2java2011 <[hidden email]
>> <http:///user/SendEmail.jtp?type=node=4676267=1>> wrote:
>> 
>> suppose that i have a ejb deployed on glassfsih remote.
>> It is possible call it from tomee on another machine?
>> 
>> and it is possible call a ejb deployed into tomee from a glassfsih?
>> 
>> Or the different corba /orb implementation not work ?
>> 
>> mauro
>> 
>> 
>> 
>> --
>> View this message in context:
>> http://tomee-openejb.979440.n4.nabble.com/a-curiosity-is-possible-call-a-remote-ejb-on-glassfsih-from-tomee-and-vice-versa-tp4676265.html
>> Sent from the TomEE Users mailing list archive at Nabble.com.
>> 
>> 
>> 
>> 
>> 
>> --
>> If you reply to this email, your message will be added to the discussion
>> below:
>> 
>> http://tomee-openejb.979440.n4.nabble.com/a-curiosity-is-possible-call-a-remote-ejb-on-glassfsih-from-tomee-and-vice-versa-tp4676265p4676267.html
>> To unsubscribe from a curiosity: is possible call a remote ejb on
>> glassfsih from tomee and vice versa?, click here
>> <http://tomee-openejb.979440.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code=4676265=bWF1cm8yamF2YTIwMTFAZ21haWwuY29tfDQ2NzYyNjV8LTExMTcxODc2MjU=>
>> .
>> NAML
>> <http://tomee-openejb.979440.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer=instant_html%21nabble%3Aemail.naml=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>> 
> 
> 
> 
> 
> --
> View this message in context: 
> http://tomee-openejb.979440.n4.nabble.com/a-curiosity-is-possible-call-a-remote-ejb-on-glassfsih-from-tomee-and-vice-versa-tp4676265p4676279.html
> Sent from the TomEE Users mailing list archive at Nabble.com.





Re: Two beans with the same name - I thought was supposed to give error?

2015-09-16 Thread Gurkan Erdogdu
Hello Colin

This is not related with CDI, you are using @Stateful annotation defined in EJB 
specification. EJB names are used to give a unique name to EJB beans, therefore 
you can inject them via @EJB(name of the bean). In OpenEJB, you can use the 
same name here but name will be used for EJB bean first deployed. If Movies2 
will be deployed first, only this bean is deployed otherwise Movies will be 
deployed and created JNDI name for them. According to EJB specification, The 
ejb-name element contains the name of an enterprise
bean. The name must be unique within the ejb-jar file.  Therefore, you have to 
give unique names to EJB beans.

So, if you want to use Alternative with CDI specification, you can use @Inject 
to inject EJB Beans and use @Alternatives to describe alternative CDI beans and 
also define alternatives in beans.xml.

Please have a look at this example : 
https://github.com/apache/tomee/tree/master/examples/cdi-alternative-and-stereotypes
 
<https://github.com/apache/tomee/tree/master/examples/cdi-alternative-and-stereotypes>
 

Hope that it helps!

Best
Gurkan Erdogdu
ManageCat, http://www.managecat.com <http://www.managecat.com/> 
Office : +1 (909) - 366 – 9337
340 S Lemon Ave #7996 Walnut, CA 91789

One of them is : 

> On 16 Sep 2015, at 07:54, cfnz <r...@hill-labs.co.nz> wrote:
> 
> Still trying to come to grips with beans and CDI, etc...
> 
> I was under the impression that if two beans had the same name, that the
> container would complain as it would not know which one to use... but it
> doesn't... is it supposed to?
> 
> Test case... take the eclipse link movies example, copy Movies.java to
> Movies2.java and add the following:
> 
> @Stateful(name = "Movies")
> public class Movies2 {
> ... etc
> }
> 
> I thought this would complain... When the test case asks for Movies, how
> does it know which movies it will get?? I have been looking into the
> @Alternative annotation, but the first thing I need to sort out is why the
> above works... (I have another query on how to select the @Alternative, but
> I shall do another post for that.)
> 
> Regards
> Colin
> 
> 
> 
> 
> --
> View this message in context: 
> http://tomee-openejb.979440.n4.nabble.com/Two-beans-with-the-same-name-I-thought-was-supposed-to-give-error-tp4676235.html
> Sent from the TomEE Users mailing list archive at Nabble.com.









Re: a curiosity: is possible call a remote ejb on glassfsih from tomee and vice versa?

2015-09-16 Thread Gurkan Erdogdu
Hello Mauro

AFAIK OpenEJB uses its own binary remote protocol, not CORBA or RMI/JRMP etc. 
So, it may not possible to communicate from OpenEJB to Glassfish but if you 
have Glassfish client jars to access glass fish remote EJBS, you can use these 
clients to access them in TomEE.

Best

Gurkan Erdogdu  
Founder, ManageCat 
p. +1 (909) - 366 – 9337
a. 340 S Lemon Ave #7996 Walnut, CA 91789
w. http://managecat.com <http://managecat.com/>
e gerdo...@managecat.com <mailto:gerdo...@managecat.com>
 <http://twitter.com/gerdogdu>  <https://tr.linkedin.com/in/gerdogdu>
> On 16 Sep 2015, at 19:51, mauro2java2011 <mauro2java2...@gmail.com> wrote:
> 
> suppose that i have a ejb deployed on glassfsih remote.
> It is possible call it from tomee on another machine?
> 
> and it is possible call a ejb deployed into tomee from a glassfsih?
> 
> Or the different corba /orb implementation not work ?
> 
> mauro
> 
> 
> 
> --
> View this message in context: 
> http://tomee-openejb.979440.n4.nabble.com/a-curiosity-is-possible-call-a-remote-ejb-on-glassfsih-from-tomee-and-vice-versa-tp4676265.html
> Sent from the TomEE Users mailing list archive at Nabble.com.





Re: [E-Book Version] Apache TomEE Cookbook

2013-08-22 Thread Gurkan Erdogdu
Hi Leo

Thanks for your support. Below link is not valid anymore. Use this link 
http://tinyurl.com/k74nmee 

Best

Gurkan


On 22 Ağu 2013, at 15:16, Leonardo K. Shikida shik...@gmail.com wrote:

 Hi Gurkan
 
 I'll give your pdf a try :-) unfortunately my company thinks your selling
 link is insecure and it's being blocked from here... :-( so I'll do this at
 home
 
 My suggestion for your next book is to cover TomEE+
 
 best regards and good job!
 
 Leo
 
 
 []
 
 Leo
 
 
 On Wed, Aug 21, 2013 at 12:09 PM, Gurkan Erdogdu 
 gurkanerdo...@yahoo.comwrote:
 
 Hello Yann
 
 You can buy PDF version of the book from http://payhip.com/b/bsva
 
 Best.
 
 Gurkan
 
 
 
 
 From: Yann Blazart yann.blaz...@bycode.fr
 To: users@tomee.apache.org; Gurkan Erdogdu gurkanerdo...@yahoo.com
 Cc: u...@openwebbeans.apache.org u...@openwebbeans.apache.org; 
 d...@openwebbeans.apache.org d...@openwebbeans.apache.org; 
 d...@tomee.apache.org d...@tomee.apache.org
 Sent: Wednesday, August 21, 2013 4:19 PM
 Subject: Re: Apache TomEE Cookbook
 
 
 Sorry, but it's the printed version ? Where can I buy the pdf version ?
 
 
 2013/8/21 Gurkan Erdogdu gurkanerdo...@yahoo.com
 
 Hi folks
 
 I have written a small cook book about Apache TomEE. My book Apache
 TomEE
 Cookbook published by Amazon Create Space. You can get e-book format of
 the book from http://tinyurl.com/k9rr56a
 
 Hard copy of the book will also be published in Amazon Strore in 5-7
 days.
 
 Please give your feedbacks to me directly for Version-2 of the book!
 
 Enjoy!
 


Re: [E-Book Version] Apache TomEE Cookbook

2013-08-21 Thread Gurkan Erdogdu
Hello Yann

You can buy PDF version of the book from http://payhip.com/b/bsva

Best.

Gurkan




 From: Yann Blazart yann.blaz...@bycode.fr
To: users@tomee.apache.org; Gurkan Erdogdu gurkanerdo...@yahoo.com 
Cc: u...@openwebbeans.apache.org u...@openwebbeans.apache.org; 
d...@openwebbeans.apache.org d...@openwebbeans.apache.org; 
d...@tomee.apache.org d...@tomee.apache.org 
Sent: Wednesday, August 21, 2013 4:19 PM
Subject: Re: Apache TomEE Cookbook
 

Sorry, but it's the printed version ? Where can I buy the pdf version ?


2013/8/21 Gurkan Erdogdu gurkanerdo...@yahoo.com

 Hi folks

 I have written a small cook book about Apache TomEE. My book Apache TomEE
 Cookbook published by Amazon Create Space. You can get e-book format of
 the book from http://tinyurl.com/k9rr56a

 Hard copy of the book will also be published in Amazon Strore in 5-7 days.

 Please give your feedbacks to me directly for Version-2 of the book!

 Enjoy!