Re: Suggestion: tick client JARs provisionning service
You're though with me, but I won't give up without trying harder :) Here's what I have in mind : providing a Java EE client JARs provisioning REST service for : 1. client apps which talk to the app server using JMS 2. client apps which talk to the app server using EJB 3. client apps which talk to the app server using JPA datatypes To avoid a service that would also such client apps to download all jar files if they need a feature subset, then one could steal some ideas to Eclipse plug-ins download. In Eclipse, you can select a few plug-ins, and ask to also get their dependencies and even better, you can make your fine-grained selection of what you'll actually download. Ideally, all Java EE app servers should provide such client Java EE jars provisionning service :for example, WebSphere Application Server could also downloading WebSphere MQ client Jars; etc. That's why in my initial post I was asking whether or not there's a Java EE standard for this need, either in existing Java EE specs or in next or future ones. If not, then would it make sense for TomEE to provide it, as a working reference implementation of a future enhancement of Java EE specs ? Does it sounds better now? thanks, Alex On Sun, Dec 9, 2012 at 8:34 AM, Romain Manni-Bucau rmannibu...@gmail.comwrote: Hmm, but the point is it depends so much on the needs that it will end up with the tull server to manage all cases, no? Le 9 déc. 2012 00:28, Alex The Rocker alex.m3...@gmail.com a écrit : Hello, Suppose you want to write a Java client application for your web app that relies on JNDI, JMS and send receives EJBs to and from the application server. Then, in your client application (which is not a web app, but rather a Java program with a class having a main() entry point method), you'll need to have in our classpath: - ActiveMQ JARs for using JMS in a way compatible with TomEE's ActiveMQ - TomEE actually uses web service protocols to make remote calls to EJB Session Beans. There still needs to be a client library that knows how to encode an EJB call into XML and extract the returned result as a Java Object. - the same idea would also apply to Java Programming Objects See jbossall-client.jar for something equivalent provided by JBoss : http://docs.jboss.org/jbossas/docs/Installation_And_Getting_Started_Guide/5/html/ch01.html#d0e525 Now, better than JBoss client libraries, we'd like to have a REST service on the app server allowing our client application to download the app server's client libraries specific to its JMS, EBJ, etc. implementation into some directory that would be added to the client application's CLASSPATH at runtime. Is it clearer ? Alex On Sat, Dec 8, 2012 at 6:22 PM, Jean-Louis MONTEIRO jeano...@gmail.com wrote: +1 Don't really understand the question. Could you elaborate a bit more? Le 8 déc. 2012 18:11, Romain Manni-Bucau rmannibu...@gmail.com a écrit : Not sure i got you. These jars are not always mandatory and depends on your needs. Le 8 déc. 2012 17:56, Alex The Rocker alex.m3...@gmail.com a écrit : Hello, A developer in our company asked me if there's any clean way to download tick client TomEE-specific JAR files. For example, for (not so recent) TomEE 1.5.1 snapshot, his application needs to use the following JAR files at runtime: activemq-core-5.6.0.jar javaee-api-6.0-4-tomcat.jar openejb-client-4.5.1-SNAPSHOT.jar openjpa-2.2.0.jar slf4j-api-1.6.6.jar Given that: a/ I have advised him not to include these JARs in his application, because his application must be compatible with newer TomEE releases, thus the question about a provisioning service for downloading those Java EE client-enabling JARs. b/ His application doesn't need these JARs at build-time : he only uses generic (ie, non vendor specific) APIs like JNDI or JMS c/ The last JAR file quoted above (slf4j-api.jar) is interesting because it's not directly a Java EE client implementation, but a dependency of some of the other JARs Question: 1. Is there a generic way to fulfill this requirement in a vendor independent way? if not, anything planned in Java EE 7 ? 2. Would it make sense to have such feature in TomEE to keeping Java EE tick clients up to date? If yes, then may I fill a JIRA for it? Thanks, Alex
Re: Suggestion: tick client JARs provisionning service
from security perspective, the provisioning service need to be in a webapp which can be configured to listen on another port than the one used for Internet access to application web apps on TomEE. It would also suck from security side if I had meant to include authentication in the provisioning, but I didn't mention it. For a proof a concept, I would need a way to find dependencies of Jars, I know how to do it with something like a Java bytecode reader, but it sounds like an overkill. Eclipse uses OSGi XML descriptors for dependencies, do we have something similar in TomEE binary distributions? Alex On Sun, Dec 9, 2012 at 5:05 PM, Romain Manni-Bucau rmannibu...@gmail.comwrote: Can you prototype it? With your description it sounds too risky for prod envrt but id like to be sure. Le 9 déc. 2012 16:55, Alex The Rocker alex.m3...@gmail.com a écrit : 1/ no, I don't want too much clients jars in my application : quite the opposite : I only want javaee-api.jar in my application, and the rest (the implementation jars compatible with the app server chosen by my customers) would be dynamically downloaded to this client (with a smart auto-update mechanism to avoid downloading at each start-up if there's no new version). 2/ no it's not maven related, because I'm looking for a run-time / production feature. Maven is good for development activities. Likewise I'm not looking for Opscode's Chef. I want the app server to deliver its own implementation jars to client apps, taking these jars from its own lib/ directories Maybe I'm asking too much, I don't realize.. Alex On Sun, Dec 9, 2012 at 4:41 PM, Romain Manni-Bucau rmannibu...@gmail.com wrote: Not sure if i still didnt get it but sounds like you either want too much client jars (== loosing users) or reinventing maven. Isnt it? Le 9 déc. 2012 16:38, Alex The Rocker alex.m3...@gmail.com a écrit : You're though with me, but I won't give up without trying harder :) Here's what I have in mind : providing a Java EE client JARs provisioning REST service for : 1. client apps which talk to the app server using JMS 2. client apps which talk to the app server using EJB 3. client apps which talk to the app server using JPA datatypes To avoid a service that would also such client apps to download all jar files if they need a feature subset, then one could steal some ideas to Eclipse plug-ins download. In Eclipse, you can select a few plug-ins, and ask to also get their dependencies and even better, you can make your fine-grained selection of what you'll actually download. Ideally, all Java EE app servers should provide such client Java EE jars provisionning service :for example, WebSphere Application Server could also downloading WebSphere MQ client Jars; etc. That's why in my initial post I was asking whether or not there's a Java EE standard for this need, either in existing Java EE specs or in next or future ones. If not, then would it make sense for TomEE to provide it, as a working reference implementation of a future enhancement of Java EE specs ? Does it sounds better now? thanks, Alex On Sun, Dec 9, 2012 at 8:34 AM, Romain Manni-Bucau rmannibu...@gmail.com wrote: Hmm, but the point is it depends so much on the needs that it will end up with the tull server to manage all cases, no? Le 9 déc. 2012 00:28, Alex The Rocker alex.m3...@gmail.com a écrit : Hello, Suppose you want to write a Java client application for your web app that relies on JNDI, JMS and send receives EJBs to and from the application server. Then, in your client application (which is not a web app, but rather a Java program with a class having a main() entry point method), you'll need to have in our classpath: - ActiveMQ JARs for using JMS in a way compatible with TomEE's ActiveMQ - TomEE actually uses web service protocols to make remote calls to EJB Session Beans. There still needs to be a client library that knows how to encode an EJB call into XML and extract the returned result as a Java Object. - the same idea would also apply to Java Programming Objects See jbossall-client.jar for something equivalent provided by JBoss : http://docs.jboss.org/jbossas/docs/Installation_And_Getting_Started_Guide/5/html/ch01.html#d0e525 Now, better than JBoss client libraries, we'd like to have a REST service on the app server allowing our client application to download the app server's client libraries specific to its JMS, EBJ, etc. implementation into some directory that would be added to the client application's CLASSPATH at runtime
Re: TomEE 1.5.1 release date?
Hello, Well said Harald ! In addition, I think TomEE will be taken even more seriously if it was written somewhere on its Internet site that for security alerts (CVE...) a new release would be provided in at most xx weeks. I know many potential users who wouldn't consider using TomEE if a Tomcat CVE is publicized and the only way to fix is to use a Snapshot, which may not be stable. The question is : TomEE is currently a super choice of developers, how can it be also a super choice for IT people, at least as much as Tomcat is ?. Fixed number of releases per year would be a good start (IT people won't care about Milestones, but I like this idea for developers, if Snapshot could be replaced by Nightly build - okay I confess : I like Eclipse way :) Alex On Sat, Dec 8, 2012 at 5:09 PM, Harald Wellmann hwellmann...@gmail.comwrote: To sum up my experience with TomEE: 1.0.0.beta was completely unusable, the 1.5.0 release has made a giant leap towards production quality but still has blocker bugs, which are getting fixed very quickly, and this list is extremely helpful. The problem with snapshots is that they disappear. If you work with Maven, you can't even release a product of your own with a snapshot dependency (and for a very good reason too). I've often cherrypicked fixes from unreleased versions of third-party dependencies, but that always involves the hassle of checking in a local copy, building a private release and deploying it to a local Nexus. At the current rate of bugs appearing and getting fixed in TomEE, it would be very helpful to have frequent releases. You may want to differentiate between milestone releases or stable builds and GA releases. It's ok to have only two or three GA releases per year as long as there are frequent (e.g. monthly) milestone releases, published to Maven Central, but without all the QA and ASF procedural overhead. IMHO, you cannot overestimate the negative effect of people taking a quick look at a project, running into problems, finding not enough documentation and then turning away and spreading bad news. So in addition to coming up with the next release, IMHO this project would greatly benefit from usable entry-level documentation and from sorting out the TomEE/OpenEJB confusion. Best regards, Harald
Suggestion: tick client JARs provisionning service
Hello, A developer in our company asked me if there's any clean way to download tick client TomEE-specific JAR files. For example, for (not so recent) TomEE 1.5.1 snapshot, his application needs to use the following JAR files at runtime: activemq-core-5.6.0.jar javaee-api-6.0-4-tomcat.jar openejb-client-4.5.1-SNAPSHOT.jar openjpa-2.2.0.jar slf4j-api-1.6.6.jar Given that: a/ I have advised him not to include these JARs in his application, because his application must be compatible with newer TomEE releases, thus the question about a provisioning service for downloading those Java EE client-enabling JARs. b/ His application doesn't need these JARs at build-time : he only uses generic (ie, non vendor specific) APIs like JNDI or JMS c/ The last JAR file quoted above (slf4j-api.jar) is interesting because it's not directly a Java EE client implementation, but a dependency of some of the other JARs Question: 1. Is there a generic way to fulfill this requirement in a vendor independent way? if not, anything planned in Java EE 7 ? 2. Would it make sense to have such feature in TomEE to keeping Java EE tick clients up to date? If yes, then may I fill a JIRA for it? Thanks, Alex
Re: Suggestion: tick client JARs provisionning service
Hello, Suppose you want to write a Java client application for your web app that relies on JNDI, JMS and send receives EJBs to and from the application server. Then, in your client application (which is not a web app, but rather a Java program with a class having a main() entry point method), you'll need to have in our classpath: - ActiveMQ JARs for using JMS in a way compatible with TomEE's ActiveMQ - TomEE actually uses web service protocols to make remote calls to EJB Session Beans. There still needs to be a client library that knows how to encode an EJB call into XML and extract the returned result as a Java Object. - the same idea would also apply to Java Programming Objects See jbossall-client.jar for something equivalent provided by JBoss : http://docs.jboss.org/jbossas/docs/Installation_And_Getting_Started_Guide/5/html/ch01.html#d0e525 Now, better than JBoss client libraries, we'd like to have a REST service on the app server allowing our client application to download the app server's client libraries specific to its JMS, EBJ, etc. implementation into some directory that would be added to the client application's CLASSPATH at runtime. Is it clearer ? Alex On Sat, Dec 8, 2012 at 6:22 PM, Jean-Louis MONTEIRO jeano...@gmail.comwrote: +1 Don't really understand the question. Could you elaborate a bit more? Le 8 déc. 2012 18:11, Romain Manni-Bucau rmannibu...@gmail.com a écrit : Not sure i got you. These jars are not always mandatory and depends on your needs. Le 8 déc. 2012 17:56, Alex The Rocker alex.m3...@gmail.com a écrit : Hello, A developer in our company asked me if there's any clean way to download tick client TomEE-specific JAR files. For example, for (not so recent) TomEE 1.5.1 snapshot, his application needs to use the following JAR files at runtime: activemq-core-5.6.0.jar javaee-api-6.0-4-tomcat.jar openejb-client-4.5.1-SNAPSHOT.jar openjpa-2.2.0.jar slf4j-api-1.6.6.jar Given that: a/ I have advised him not to include these JARs in his application, because his application must be compatible with newer TomEE releases, thus the question about a provisioning service for downloading those Java EE client-enabling JARs. b/ His application doesn't need these JARs at build-time : he only uses generic (ie, non vendor specific) APIs like JNDI or JMS c/ The last JAR file quoted above (slf4j-api.jar) is interesting because it's not directly a Java EE client implementation, but a dependency of some of the other JARs Question: 1. Is there a generic way to fulfill this requirement in a vendor independent way? if not, anything planned in Java EE 7 ? 2. Would it make sense to have such feature in TomEE to keeping Java EE tick clients up to date? If yes, then may I fill a JIRA for it? Thanks, Alex
Re: TomEE 1.5.1 release date?
Hello, Is TomEE 1.5.1 general availability still targeted and of current week or beginning of next week ? I'm worried, because I still see couple of JIRAs being closed : it doesn't look to me like a only most critical bugs can be fixed because we're in final convergence period... ... is there a way to have a firm target for 1.5.1 release? I still see people who download TomEE 1.5.0 on Windows and just throw it with a it doesn't works. I think only 1 out 1000 people actual bother to post to users list and finally get the information that they must use 1.5.1 SNAPSHOT : TomEE is loosing opportunities, I can't be clearer. Alex. On Sat, Dec 1, 2012 at 7:06 PM, Alex The Rocker alex.m3...@gmail.comwrote: @Stephano: well said ! I agree that more frequent release would make it clear that TomEE is alive, as it deserves to be seen ! Alex. On Sat, Dec 1, 2012 at 7:04 PM, stx_g st...@yahoo.it wrote: Hi David, IMHO a maintenance release should be delivered as soon as possible. A two months waiting period - or more - is too much as we are talking about bugs, not features. Moreover I think that, if there are frequent releases out, the hard work of the TomEE team could be appreciate much more. Regards. -- Stefano -- View this message in context: http://openejb.979440.n4.nabble.com/TomEE-1-5-1-release-date-tp4658991p4659037.html Sent from the OpenEJB User mailing list archive at Nabble.com.
Re: TomEE 1.5.1 release date?
@Stephano: well said ! I agree that more frequent release would make it clear that TomEE is alive, as it deserves to be seen ! Alex. On Sat, Dec 1, 2012 at 7:04 PM, stx_g st...@yahoo.it wrote: Hi David, IMHO a maintenance release should be delivered as soon as possible. A two months waiting period - or more - is too much as we are talking about bugs, not features. Moreover I think that, if there are frequent releases out, the hard work of the TomEE team could be appreciate much more. Regards. -- Stefano -- View this message in context: http://openejb.979440.n4.nabble.com/TomEE-1-5-1-release-date-tp4658991p4659037.html Sent from the OpenEJB User mailing list archive at Nabble.com.
Re: TomEE 1.5.1 release date?
David: To sum up your answer, earliest GA (General Availability) date for TomEE 1.5.1 is end of week 49, and more likely beginning of week 50 Best regards Alexandre On Fri, Nov 30, 2012 at 10:04 AM, David Blevins david.blev...@gmail.comwrote: On Nov 29, 2012, at 11:58 AM, Alex The Rocker alex.m3...@gmail.com wrote: People in my company are getting nervous with TomEE 1.5.1 official release date, because it's the target prerequisite of our soon-to-be released product. 1.5.0 is just not usable for production on Windows, due to the issues with registration as a service, and the bugs in Windows path processing. Is it possible to have a firm date for 1.5.1 official release? Next Tuesday is the tentative date for the OpenWebBeans release to start. We need this release for 1.5.1. It's 72 hours for voting per Apache rules, but typically we start the TomEE release as soon as the OpenWebBeans binaries are ready for voting -- for example, we ran the TomEE 1.5.0 vote in parallel with the OpenWebBeans 1.1.6 vote. This means the soonest we could expect released TomEE 1.5.1 is Friday. More likely early the week after. -David
TomEE 1.5.1 release date?
Hello, People in my company are getting nervous with TomEE 1.5.1 official release date, because it's the target prerequisite of our soon-to-be released product. 1.5.0 is just not usable for production on Windows, due to the issues with registration as a service, and the bugs in Windows path processing. Is it possible to have a firm date for 1.5.1 official release? Thanks, Alex.
Re: TomEE 1.5.1 Release Date
Hi, Any chance to have 1.5.1 officially release before end of next week?
Re: TomEE 1.5.1 Release Date
Hello, On our side we badly need an official 1.5.1 release because we have showstoppers on Windows with 1.5.0, and we cannot ask customers to use a Snapshot (=unofficial) version. What would be the target date for making 1.5.1 officially available ? Thanks, Alex. On Mon, Nov 12, 2012 at 11:19 AM, Harald Wellmann hwellmann...@gmail.comwrote: I would really love to see a TomEE 1.5.1 release as soon as possible. 1.5.0 has a number of blocker bugs for my use cases, but 1.5.1-SNAPSHOTs are fine. Best regards, Harald 2012/11/12 Romain Manni-Bucau rmannibu...@gmail.com: Hi, Why do you say it is not stable? Btw jlmoteiro started to work on the release so it should arrive. Le 12 nov. 2012 07:56, zeddius avalyu...@gmail.com a écrit : Hi guys, When TomEE 1.5.1 is going to be released? We are waiting for a number of bug fixes from TomEE 1.5.1 however the snapshots are not very stable. -- View this message in context: http://openejb.979440.n4.nabble.com/TomEE-1-5-1-Release-Date-tp4658516.html Sent from the OpenEJB User mailing list archive at Nabble.com.
Re: Need stable version scheme for TomEE and link to archived releases
Romain: Good to know that older version still exist, but this is only part of my points, which again are: - How about a well defined version scheme for TomEE ? - Can links to older versions archives be added to TomEE download page? Thanks, Alex On Sat, Oct 27, 2012 at 3:20 PM, Romain Manni-Bucau rmannibu...@gmail.comwrote: Quick side note: all versions are available on nexus, links are not (yet?) mentioned but exist. Le 27 oct. 2012 08:45, Alex The Rocker alex.m3...@gmail.com a écrit : Hello, TomEE is supposed to be Tomcat Enterprise Edition. One thing that Enterprises appreciate with software prerequisites is the ability to move from one version to another when they fell confident that 1/ it's compatible with the web apps they deploy 2/ it's available. Currently (as of 27th October) we have in TomEE download page only links to version 1.5.0. In theory, there will soon be version 1.5.1, and enterprises will consider the .1 as a bug fix release. I read that maybe the next available TomEE would be 1.6.0, meaning features changes. Why 1.0.0. isn't anymore accessible on TomEE download page? Will links to 1.5.0 be removed when 1.5.1 is available on the download page? Will links to 1.5.x be removed when 1.6.0 is available on the download page? What if an enterprise bought a product that is certified on 1.5.x ; x=0 ? Will there be no 1.5.2, 1.5.3 once 1.6.0 is available? what if Tomcat 7 security fixes are only avail on TomEE 1.6.x but not on TomEE 1.5.x? Let's compare with Apache Tomcat download page: there are links for the last 3 major releases (Tomcat 7, Tomcat 6 and Tomcat 5). When you follow the link on a given release, say Tomcat 7, you have access to latest point release of Tomcat 7 (Tomcat 7.0.32 as of this writing), but also to Archives, from where all point releases between 7.0.0 and 7.0.0.32 can be downloaded. All major application servers have clear version scheme and access to archives. We all want TomEE to be taken seriously (reference to Romain's link to a french article where TomEE was almost seen as a Toy-me ;), so would you agree to 1/ Standardize TomEE version scheme 2/ Restore access to TomEE 1.0.0 and provide a link to TomEE archived versions ? Thanks, Alex.
How to get TomEE+ version from command-line?
Hello, I have a simple question : how can TomEE+ version can be found using command-line? If we run tomEE install path/bin/version.sh/.bat then we only see Tomcat's version. also RELEASE-NOTES.txt file in the install root only mentions Tomcat. Am i missing something ? Thanks, Alex
Re: Need a more verbose message than java.lang.ArrayStoreException: sun.reflect.annotation.TypeNotPresentExceptionProxy
Hello, I found the culprit .jar in our web app using divide and conquer method (ie remove half of the .jar files, restart tomEE until I found the one that caused that blocking exception for deployment). I checked today's 1.5.1 snapshot (build #37), and I saw no difference in the mysteriousTypeNotPresentExceptionProxy exception. Would the improvement on this kind of issue be part of 1.5.1 or of a later version? I'm ready to test it as soon as it's available in a snapshot with my use case... Alex. On Wed, Oct 10, 2012 at 7:36 PM, Romain Manni-Bucau rmannibu...@gmail.comwrote: - no trace to activate - debug xbean AnnotationFinder method - i think the snapshot is not yet deployed *Romain Manni-Bucau* *Twitter: @rmannibucau https://twitter.com/rmannibucau* *Blog: **http://rmannibucau.wordpress.com/* http://rmannibucau.wordpress.com/ *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2012/10/10 Alex The Rocker alex.m3...@gmail.com Romain: I used 1.5.1 snapshot build #34, I which build number should we have a more verbose trace for this type of exceptions? More important : how can I debug the cause of this exception now? any log4j trace to activate (how ?) Thanks, Alex On Wed, Oct 10, 2012 at 5:12 PM, Romain Manni-Bucau rmannibu...@gmail.comwrote: Hi Alex, that's more a xbean issue btw i just pushed some changes to try to get it but from openejb/tomee that's not so easy *Romain Manni-Bucau* *Twitter: @rmannibucau https://twitter.com/rmannibucau* *Blog: **http://rmannibucau.wordpress.com/* http://rmannibucau.wordpress.com/ *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2012/10/10 Alex The Rocker alex.m3...@gmail.com Hello, Is there a way to get TomEE+ more verbose than when currently it throws TypeNotPresentExceptionProxy ? Looks like something is missing related to annotation processor, but hard to debug without a more verbose message. I'm using latest 1.5.1 snapshot. As a by-pass, is there a way to activate more traces (how?) Thanks, Alex PS: here's the stack for my latest case: SEVERE: Unable to deploy collapsed ear in war StandardEngine[Catalina].StandardHost[localhost].StandardContext[/WS] java.lang.ArrayStoreException: sun.reflect.annotation.TypeNotPresentExceptionProxy at sun.reflect.annotation.AnnotationParser.parseClassArray(AnnotationParser.java:673) at sun.reflect.annotation.AnnotationParser.parseArray(AnnotationParser.java:480) at sun.reflect.annotation.AnnotationParser.parseMemberValue(AnnotationParser.java:306) at sun.reflect.annotation.AnnotationParser.parseAnnotation(AnnotationParser.java:241) at sun.reflect.annotation.AnnotationParser.parseAnnotations2(AnnotationParser.java:88) at sun.reflect.annotation.AnnotationParser.parseAnnotations(AnnotationParser.java:70) at java.lang.Class.initAnnotationsIfNecessary(Class.java:3089) at java.lang.Class.getAnnotation(Class.java:3048) at java.lang.Class.isAnnotationPresent(Class.java:3061) at org.apache.xbean.finder.AnnotationFinder.findAnnotatedClasses(
Re: TomEE on Windows: how to register a native PATH for webapps
On a more general note, could we have for TomEE the equivalent documentation (and support of documented features) which Tomcat7 has for running as a Windows service: http://tomcat.apache.org/tomcat-7.0-doc/windows-service-howto.html#Installing_services Should I fill a JIRA for this ? Alex On Thu, Oct 11, 2012 at 6:31 PM, Alex The Rocker alex.m3...@gmail.comwrote: Hello, We need a to register TomEE+ on Windows with a native PATH for the web apps it will run (those web apps rely on JNI for some tricks, I know it sucks, but that's real life). Of course we don't want to use global environment variables. The tomcat7.exe / tomcat7w.exe had a way to specify PATH at the Tomcat Windows service level, looks like we're in regression with regard to this aspect with the various TomEE's .exe files. Should I open a JIRA for this, or did I miss something? PS: unfortunately, this inconvenience is seen as a show stopper for the application I've been lobbying to change its prereq form Tomcat to TomEE... hope there's a quick way to solve it... Thanks, Alex
TomEE on Windows: how to register a native PATH for webapps
Hello, We need a to register TomEE+ on Windows with a native PATH for the web apps it will run (those web apps rely on JNI for some tricks, I know it sucks, but that's real life). Of course we don't want to use global environment variables. The tomcat7.exe / tomcat7w.exe had a way to specify PATH at the Tomcat Windows service level, looks like we're in regression with regard to this aspect with the various TomEE's .exe files. Should I open a JIRA for this, or did I miss something? PS: unfortunately, this inconvenience is seen as a show stopper for the application I've been lobbying to change its prereq form Tomcat to TomEE... hope there's a quick way to solve it... Thanks, Alex
Need a more verbose message than java.lang.ArrayStoreException: sun.reflect.annotation.TypeNotPresentExceptionProxy
Hello, Is there a way to get TomEE+ more verbose than when currently it throws TypeNotPresentExceptionProxy ? Looks like something is missing related to annotation processor, but hard to debug without a more verbose message. I'm using latest 1.5.1 snapshot. As a by-pass, is there a way to activate more traces (how?) Thanks, Alex PS: here's the stack for my latest case: SEVERE: Unable to deploy collapsed ear in war StandardEngine[Catalina].StandardHost[localhost].StandardContext[/WS] java.lang.ArrayStoreException: sun.reflect.annotation.TypeNotPresentExceptionProxy at sun.reflect.annotation.AnnotationParser.parseClassArray(AnnotationParser.java:673) at sun.reflect.annotation.AnnotationParser.parseArray(AnnotationParser.java:480) at sun.reflect.annotation.AnnotationParser.parseMemberValue(AnnotationParser.java:306) at sun.reflect.annotation.AnnotationParser.parseAnnotation(AnnotationParser.java:241) at sun.reflect.annotation.AnnotationParser.parseAnnotations2(AnnotationParser.java:88) at sun.reflect.annotation.AnnotationParser.parseAnnotations(AnnotationParser.java:70) at java.lang.Class.initAnnotationsIfNecessary(Class.java:3089) at java.lang.Class.getAnnotation(Class.java:3048) at java.lang.Class.isAnnotationPresent(Class.java:3061) at org.apache.xbean.finder.AnnotationFinder.findAnnotatedClasses(
Re: Need a more verbose message than java.lang.ArrayStoreException: sun.reflect.annotation.TypeNotPresentExceptionProxy
Romain: I used 1.5.1 snapshot build #34, I which build number should we have a more verbose trace for this type of exceptions? More important : how can I debug the cause of this exception now? any log4j trace to activate (how ?) Thanks, Alex On Wed, Oct 10, 2012 at 5:12 PM, Romain Manni-Bucau rmannibu...@gmail.comwrote: Hi Alex, that's more a xbean issue btw i just pushed some changes to try to get it but from openejb/tomee that's not so easy *Romain Manni-Bucau* *Twitter: @rmannibucau https://twitter.com/rmannibucau* *Blog: **http://rmannibucau.wordpress.com/* http://rmannibucau.wordpress.com/ *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2012/10/10 Alex The Rocker alex.m3...@gmail.com Hello, Is there a way to get TomEE+ more verbose than when currently it throws TypeNotPresentExceptionProxy ? Looks like something is missing related to annotation processor, but hard to debug without a more verbose message. I'm using latest 1.5.1 snapshot. As a by-pass, is there a way to activate more traces (how?) Thanks, Alex PS: here's the stack for my latest case: SEVERE: Unable to deploy collapsed ear in war StandardEngine[Catalina].StandardHost[localhost].StandardContext[/WS] java.lang.ArrayStoreException: sun.reflect.annotation.TypeNotPresentExceptionProxy at sun.reflect.annotation.AnnotationParser.parseClassArray(AnnotationParser.java:673) at sun.reflect.annotation.AnnotationParser.parseArray(AnnotationParser.java:480) at sun.reflect.annotation.AnnotationParser.parseMemberValue(AnnotationParser.java:306) at sun.reflect.annotation.AnnotationParser.parseAnnotation(AnnotationParser.java:241) at sun.reflect.annotation.AnnotationParser.parseAnnotations2(AnnotationParser.java:88) at sun.reflect.annotation.AnnotationParser.parseAnnotations(AnnotationParser.java:70) at java.lang.Class.initAnnotationsIfNecessary(Class.java:3089) at java.lang.Class.getAnnotation(Class.java:3048) at java.lang.Class.isAnnotationPresent(Class.java:3061) at org.apache.xbean.finder.AnnotationFinder.findAnnotatedClasses(
Re: v1.5.0 Security concern
Romain: I think TomEE should be secure by default, so commenting the default users sound good to me. For developers vs production use cases, I think it would be great to have a configurator command to swtich from developer vs. production configuration profiles. (IBM WebSphere has this feature, in Profile Management Tool) Alex. On Sat, Oct 6, 2012 at 4:15 PM, Romain Manni-Bucau rmannibu...@gmail.comwrote: Hi, i think the question is open and i scare a debate without end on this topic. Why i didn't comment it: because the moment where you need it the most often is during the development so no issue having it. In production i hope it is adapted (and maybe tomcat-users.xml is not used at all) so i thought it was not an issue. That's said if *everybody *thinks it should be as Tomcat commented i see no big issue doing it *Romain Manni-Bucau* *Twitter: @rmannibucau https://twitter.com/rmannibucau* *Blog: **http://rmannibucau.wordpress.com/* http://rmannibucau.wordpress.com/ *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2012/10/6 exabrial exabrial+open...@gmail.com In apache-tomee-webprofile-1.5.0/conf/tomcat-users.xml, the following users are defined: role rolename=tomee-admin/ user password=tomee roles=tomee-admin,manager-gui username=tomee/ Wouldn't it be better to have those commented out by default? -- View this message in context: http://openejb.979440.n4.nabble.com/v1-5-0-Security-concern-tp4657814.html Sent from the OpenEJB User mailing list archive at Nabble.com.
Re: v1.5.0 Security concern
Security isn't an option. JIRA improvement item created, see: https://issues.apache.org/jira/browse/TOMEE-450 On Sat, Oct 6, 2012 at 5:32 PM, Romain Manni-Bucau rmannibu...@gmail.comwrote: i thought starting a thread on it after next release but up to you, jira works too *Romain Manni-Bucau* *Twitter: @rmannibucau https://twitter.com/rmannibucau* *Blog: **http://rmannibucau.wordpress.com/* http://rmannibucau.wordpress.com/ *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2012/10/6 Alex The Rocker alex.m3...@gmail.com Want me to fill a JIRA for it ? Alex On Sat, Oct 6, 2012 at 5:23 PM, Romain Manni-Bucau rmannibu...@gmail.com wrote: hmm kind of profile can make sense probably something to think about for v 1.6 *Romain Manni-Bucau* *Twitter: @rmannibucau https://twitter.com/rmannibucau* *Blog: **http://rmannibucau.wordpress.com/* http://rmannibucau.wordpress.com/ *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2012/10/6 Alex The Rocker alex.m3...@gmail.com Romain: I think TomEE should be secure by default, so commenting the default users sound good to me. For developers vs production use cases, I think it would be great to have a configurator command to swtich from developer vs. production configuration profiles. (IBM WebSphere has this feature, in Profile Management Tool) Alex. On Sat, Oct 6, 2012 at 4:15 PM, Romain Manni-Bucau rmannibu...@gmail.com wrote: Hi, i think the question is open and i scare a debate without end on this topic. Why i didn't comment it: because the moment where you need it the most often is during the development so no issue having it. In production i hope it is adapted (and maybe tomcat-users.xml is not used at all) so i thought it was not an issue. That's said if *everybody *thinks it should be as Tomcat commented i see no big issue doing it *Romain Manni-Bucau* *Twitter: @rmannibucau https://twitter.com/rmannibucau* *Blog: **http://rmannibucau.wordpress.com/* http://rmannibucau.wordpress.com/ *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2012/10/6 exabrial exabrial+open...@gmail.com In apache-tomee-webprofile-1.5.0/conf/tomcat-users.xml, the following users are defined: role rolename=tomee-admin/ user password=tomee roles=tomee-admin,manager-gui username=tomee/ Wouldn't it be better to have those commented out by default? -- View this message in context: http://openejb.979440.n4.nabble.com/v1-5-0-Security-concern-tp4657814.html Sent from the OpenEJB User mailing list archive at Nabble.com.
Re: v1.5.0 Security concern
okay I do that On Sat, Oct 6, 2012 at 9:29 PM, Romain Manni-Bucau rmannibu...@gmail.comwrote: added some more info + my opinion maybe the thread should be pushed to dev@ now, no? *Romain Manni-Bucau* *Twitter: @rmannibucau https://twitter.com/rmannibucau* *Blog: **http://rmannibucau.wordpress.com/* http://rmannibucau.wordpress.com/ *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2012/10/6 Alex The Rocker alex.m3...@gmail.com Security isn't an option. JIRA improvement item created, see: https://issues.apache.org/jira/browse/TOMEE-450 On Sat, Oct 6, 2012 at 5:32 PM, Romain Manni-Bucau rmannibu...@gmail.com wrote: i thought starting a thread on it after next release but up to you, jira works too *Romain Manni-Bucau* *Twitter: @rmannibucau https://twitter.com/rmannibucau* *Blog: **http://rmannibucau.wordpress.com/* http://rmannibucau.wordpress.com/ *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2012/10/6 Alex The Rocker alex.m3...@gmail.com Want me to fill a JIRA for it ? Alex On Sat, Oct 6, 2012 at 5:23 PM, Romain Manni-Bucau rmannibu...@gmail.com wrote: hmm kind of profile can make sense probably something to think about for v 1.6 *Romain Manni-Bucau* *Twitter: @rmannibucau https://twitter.com/rmannibucau* *Blog: **http://rmannibucau.wordpress.com/* http://rmannibucau.wordpress.com/ *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2012/10/6 Alex The Rocker alex.m3...@gmail.com Romain: I think TomEE should be secure by default, so commenting the default users sound good to me. For developers vs production use cases, I think it would be great to have a configurator command to swtich from developer vs. production configuration profiles. (IBM WebSphere has this feature, in Profile Management Tool) Alex. On Sat, Oct 6, 2012 at 4:15 PM, Romain Manni-Bucau rmannibu...@gmail.com wrote: Hi, i think the question is open and i scare a debate without end on this topic. Why i didn't comment it: because the moment where you need it the most often is during the development so no issue having it. In production i hope it is adapted (and maybe tomcat-users.xml is not used at all) so i thought it was not an issue. That's said if *everybody *thinks it should be as Tomcat commented i see no big issue doing it *Romain Manni-Bucau* *Twitter: @rmannibucau https://twitter.com/rmannibucau* *Blog: **http://rmannibucau.wordpress.com/* http://rmannibucau.wordpress.com/ *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2012/10/6 exabrial exabrial+open...@gmail.com In apache-tomee-webprofile-1.5.0/conf/tomcat-users.xml, the following users are defined: role rolename=tomee-admin/ user password=tomee roles=tomee-admin,manager-gui username=tomee/ Wouldn't it be better to have those commented out by default? -- View this message in context: http://openejb.979440.n4.nabble.com/v1-5-0-Security-concern-tp4657814.html Sent from the OpenEJB User mailing list archive at Nabble.com.
Re: Next TomEE release date?
Hello, What happen with TomEE/TomEE+ 1.5.0 ? I thought it was to be available this week (remember most people who visit TomEE internet site don't use this mailing list to find snapshots). Here's what currently available at :http://tomee.apache.org/downloads.html : Apache TomEE 1.0.0 April 30th, 2012I got some feedbacks from software compagnies I work with that lack of visibility of even the RC / beta 1.5.0 giving this site the image of a dead project. April 30th is like years ago in computing time. TomEE deserves better visibility, in my opinion. May I suggest that until 1.5.0 is out, a link to the latest 1.5.0 snapshot be added to http://tomee.apache.org/downloads.html page, as well as some indications that, in order to get visibility for next major and minor releases, people should subscribe to users and/or dev mailing lists (and from time to time, a link to 1.5.1 / 1.6.0 snapshot would be updated on this page)? The world must be aware that TomEE is alive! Thanks Alex On Tue, Oct 2, 2012 at 7:57 AM, Neale Rudd ne...@metawerx.net wrote: Hi David, Plus and JAX already showing in http://www.apache.org/dist/**openejb/http://www.apache.org/dist/openejb/, and WP just appeared too :) Great work! Best Regards, Neale - Original Message - From: David Blevins david.blev...@gmail.com To: users@openejb.apache.org Sent: Tuesday, October 02, 2012 3:46 PM Subject: Re: Next TomEE release date? The 1.5.0 binaries published. It takes several hours from them to reach Maven Central and the Apache Mirrors. The announcement should go out Tuesday or Wednesday, but keep your eyes out here in the meantime: - http://www.apache.org/dist/**openejb/http://www.apache.org/dist/openejb/ Already a couple bugs found and fixed, a 1.5.1 should be short on the heels. Maybe even next week. -David On Oct 1, 2012, at 3:16 PM, andyay wrote: So, any news about the next TomEE (TomEE+ for me) release date ? Would it be based on the 1.5.1 version or later ? Thanks. -- View this message in context: http://openejb.979440.n4.** nabble.com/Next-TomEE-release-**date-tp4657315p4657738.htmlhttp://openejb.979440.n4.nabble.com/Next-TomEE-release-date-tp4657315p4657738.html Sent from the OpenEJB User mailing list archive at Nabble.com.
Re: failed to register TomEE 1.5.0 latest snapshot on 64-bit Windows 7
Andy: Thank you very much, the Windows executable files at the link you provided works for me, so I have a by-pass. Nevertheless, don't you think I should fill a JIRA to track resolution of this issue on the officially released TomEE/TomEE+ packages? (I realized that this was broken in 1.0.0 as well). Alex. On Tue, Oct 2, 2012 at 5:12 PM, AndyG andy.gumbre...@orprovision.comwrote: Looks like the distribution is trashing the exe files - They are fine in the source: https://svn.apache.org/repos/asf/openejb/trunk/openejb/tomee/apache-tomee/src/main/resources Try downloading directly and overwrite the local exe's -- View this message in context: http://openejb.979440.n4.nabble.com/failed-to-register-TomEE-1-5-0-latest-snapshot-on-64-bit-Windows-7-tp4657751p4657754.html Sent from the OpenEJB User mailing list archive at Nabble.com.
Re: Next TomEE release date?
Isn't the actual path this one: https://repository.apache.org/content/repositories/orgapacheopenejb-036/org/apache/openejb/apache-tomee/1.5.0/ ? what's different between TomEE at your path and https://repository.apache.org/content/repositories/snapshots/org/apache/openejb/apache-tomee/1.5.1-SNAPSHOT/? On Tue, Sep 25, 2012 at 12:59 AM, David Blevins david.blev...@gmail.comwrote: Just put up a preview build of the 1.5.0 https://repository.apache.org/content/repositories/orgapacheopenejb-036 These aren't the official binaries of course, but the final binaries should be fairly close to these. -David On Sep 24, 2012, at 11:21 AM, Alex The Rocker wrote: Hello, I am again confused : I thought next TomEE release would be call 1.5.0, but I saw that there's a 1.5.1 snapshot dated today here: https://repository.apache.org/content/repositories/snapshots/org/apache/openejb/apache-tomee/1.5.1-SNAPSHOT/ I don't want to qualify our app with an higher version than upcomping GA, but I can't find a 1.5.0 snapshot. Am I mistaking? Alex On Sun, Sep 23, 2012 at 9:16 PM, Romain Manni-Bucau rmannibu...@gmail.comwrote: Oops sorry, it means Apache OpenWebBeans *Romain Manni-Bucau* *Twitter: @rmannibucau* *Blog: http://rmannibucau.wordpress.com* *LinkedIn: http://www.linkedin.com/pub/romain-manni-bucau/43/544/956* 2012/9/23 Alex The Rocker alex.m3...@gmail.com Okay, and hey sorry again for being n00b, but what does OWB means? On Sun, Sep 23, 2012 at 7:45 PM, Romain Manni-Bucau rmannibu...@gmail.comwrote: Hi Alex, we are waiting the OWB release (should be under vote pretty quickly, just one or two classes to fix before running the vote) *Romain Manni-Bucau* *Twitter: @rmannibucau* *Blog: http://rmannibucau.wordpress.com* *LinkedIn: http://www.linkedin.com/pub/romain-manni-bucau/43/544/956* 2012/9/23 Alex The Rocker alex.m3...@gmail.com Hello, Just wondering if a release candidate of next TomEE release is planned soon ? On Sun, Sep 16, 2012 at 5:12 PM, Alex The Rocker alex.m3...@gmail.com wrote: David: Thank you very much for your clear answer, it's alright : I understand that you're doing best effort to get 1.1.0 done for JavaOne, I guess that even if it's not ready at this time it could be available early october. I'm going to take the risk and bet on it for our project (time to have guts) Alex On Sun, Sep 16, 2012 at 3:43 AM, David Blevins david.blev...@gmail.com wrote: We're hacking on the release now, it'll be a scramble to get it done by the end of the month but should be doable. No Apache project can actually guarantee a date due to voting -- it takes a minimum of 3 days per Apache bylaws and can't be closed till certain conditions are met -- such as getting enough votes. As it's a volunteer organization and difficult to get people's time, we typically get last minute feedback that requires new binaries and a new vote and another 3 days. So the best I can say is we're trying very hard to get it out before JavaOne / end of the month. As that sounds very scary, as a point of reference, we were in this same position last year and made the before JavaOne date. We got our *first* ever 100% TCK pass on September 23rd (cutting it very close) and were able to get a release out and announcement ready by JavaOne. If we're able to get a vote started by mid week, we should be able to make it by end of the month no problem. -David On Sep 15, 2012, at 1:28 PM, Alex The Rocker wrote: Anyone here knowing TomEE/TomEE+ 1.1.0 targeted date for general availability ? On Fri, Sep 14, 2012 at 9:39 PM, Alex The Rocker alex.m3...@gmail.com wrote: Okay, I don't mind if the next release is called 1.1.0 instead of 1.0.1. However, do care to know whether or not it's still scheduled for this month before JavaOne: the application for which I'm lobbying a change from Tomcat to TomEE+ is currently in final phase for prerequisites define. They want to add REST façade, and I saw in TomEE 1.0.1 release notes (here: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12312320version=12321242 ) that there was a fix on the JAX-WS + JAX-RS cohexistence in a same web app. If TomEE 1.1.0 come too late (ie after September), then they'll reject TomEE+ and choose instead to stay with Tomcat and use Jersey for JAX-RS, which would make a TomEE+ win-back hard (I saw some threads about Jersey annoyances when deploying such apps to TomEE+) Baseline : what's the target date for 1.1.0 GA (General Availability) ? Alex On Fri, Sep 14, 2012 at 9:31 PM, Romain Manni-Bucau rmannibu...@gmail.com wrote: Yeah, i think 1.0.1 will never be released Npt = not from a phone ;) Le 14 sept
Re: Next TomEE release date?
Hello, Just wondering if a release candidate of next TomEE release is planned soon ? On Sun, Sep 16, 2012 at 5:12 PM, Alex The Rocker alex.m3...@gmail.comwrote: David: Thank you very much for your clear answer, it's alright : I understand that you're doing best effort to get 1.1.0 done for JavaOne, I guess that even if it's not ready at this time it could be available early october. I'm going to take the risk and bet on it for our project (time to have guts) Alex On Sun, Sep 16, 2012 at 3:43 AM, David Blevins david.blev...@gmail.comwrote: We're hacking on the release now, it'll be a scramble to get it done by the end of the month but should be doable. No Apache project can actually guarantee a date due to voting -- it takes a minimum of 3 days per Apache bylaws and can't be closed till certain conditions are met -- such as getting enough votes. As it's a volunteer organization and difficult to get people's time, we typically get last minute feedback that requires new binaries and a new vote and another 3 days. So the best I can say is we're trying very hard to get it out before JavaOne / end of the month. As that sounds very scary, as a point of reference, we were in this same position last year and made the before JavaOne date. We got our *first* ever 100% TCK pass on September 23rd (cutting it very close) and were able to get a release out and announcement ready by JavaOne. If we're able to get a vote started by mid week, we should be able to make it by end of the month no problem. -David On Sep 15, 2012, at 1:28 PM, Alex The Rocker wrote: Anyone here knowing TomEE/TomEE+ 1.1.0 targeted date for general availability ? On Fri, Sep 14, 2012 at 9:39 PM, Alex The Rocker alex.m3...@gmail.com wrote: Okay, I don't mind if the next release is called 1.1.0 instead of 1.0.1. However, do care to know whether or not it's still scheduled for this month before JavaOne: the application for which I'm lobbying a change from Tomcat to TomEE+ is currently in final phase for prerequisites define. They want to add REST façade, and I saw in TomEE 1.0.1 release notes (here: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12312320version=12321242 ) that there was a fix on the JAX-WS + JAX-RS cohexistence in a same web app. If TomEE 1.1.0 come too late (ie after September), then they'll reject TomEE+ and choose instead to stay with Tomcat and use Jersey for JAX-RS, which would make a TomEE+ win-back hard (I saw some threads about Jersey annoyances when deploying such apps to TomEE+) Baseline : what's the target date for 1.1.0 GA (General Availability) ? Alex On Fri, Sep 14, 2012 at 9:31 PM, Romain Manni-Bucau rmannibu...@gmail.com wrote: Yeah, i think 1.0.1 will never be released Npt = not from a phone ;) Le 14 sept. 2012 21:24, Alex The Rocker alex.m3...@gmail.com a écrit : Call me n00b if you want, but I don't catch it: do you mean that next release due for JavaOne (end of this month) is 1.1.0 ? If otherwise it's still 1.0.1, then why couldn't there be a refresh of 1.0.1 snapshot? (and btw, what do you mean by npt? I utfm but wtf, no hit ;) Alex On Fri, Sep 14, 2012 at 9:05 PM, Romain Manni-Bucau rmannibu...@gmail.comwrote: Hi, The snapshot is the 1.1.0 (npt 1.0.1). The rc will probably be skipped (we had CI issues this week and lost some days on it :(). btw we need the snapshot for the end of the month. We currently wait an openwebbeans new version then we should be able to release Le 14 sept. 2012 20:58, Alex The Rocker alex.m3...@gmail.com a écrit : Hello, I saw in dev list that a 1.0.1 release candidate should be available this week, is that still the plan? I had a look to your (useful) link with snapshots builds. Unfortunately, for 1.0.1 there is not recent snapshot here: https://repository.apache.org/content/repositories/snapshots/org/apache/openejb/apache-tomee/1.0.1-SNAPSHOT/ The most recent one is dated 7th of June. In 1.0.1 snapshots repository, there are more recent build, but since 1.0.1 is planned before JavaOne (this month I understand), I think it's safer to target 1.0.1 a prerequisite for an application to be moved from Tomcat to TomEE+. Would you please update 1.0.1 snapshot (unless a RC is actually for current wekk) ? Thanks, Alex On Sat, Sep 8, 2012 at 10:01 AM, Romain Manni-Bucau rmannibu...@gmail.comwrote: I hope a rc next week. I wrote a post to get the snapshot: http://rmannibucau.wordpress.com/2012/05/23/getting-tomee-snapshot/ Le 8 sept. 2012 09:44, Alex The Rocker alex.m3...@gmail.com a écrit : Thanks guys, Based on David's answer and given that JavaOne begins end of september, I guess we can hope for a generally available 1.0.1 at this time, right? However, I see no 1.0.1-alpha or 1.0.1
Which JSON notations are supported by TomEE+ ?
Hello, I have a requirement to build a web application with JSON web services and which must be portable accross Apache TomEE+ next GA release = 1.5 ?, IBM WebSphere 8.5 and ORACLE WebLogic 12c. I'd like to use pure Java EE 6 APIs to make portability simple. I am currently confused by JAX-RS 1.1 : appart from Java EE 6’s javax.ws.rs.core.MediaType.APPLICATION_JSON constant, I don't find much about JSON in JAX-RS specifications. Is there a way to control which JSON notation is generated by JAX-RS web services in TomEE+ ? Note : uou will find in this link : http://jersey.java.net/nonav/documentation/latest/json.html#d4e949 a description of the Various JSON Notation (at least from a Jersey point of view) For example, is NATURAL notation supported by JSON implementation in TomEE+ ? If the generated JSON depends on which application server my application is deployed, then it'd make impossible writing with single source code, I'm afraid... isn't it ? Thanks, Alex.
Re: Can webapps/tomee directory be deleted for a production environment?
Romain: It would be great to move TomEE's transport out of the tomee management UI web app, as you suggest. Should I create a JIRA to track this feature request ? Alex PS: I'm definitely paranoid and want to remove management web app from production environment exposed to Internet (and maybe use secured JMX for remote management with strict iptable rules..) On Sun, Sep 16, 2012 at 10:59 PM, Romain Manni-Bucau rmannibu...@gmail.comwrote: i dont think (or it is not known today) i personnally would like to keep it a gui + transport webapp. wonder if we shouldnt move transport part BTW. We could do it programmatically and totally skip the webapp (something to think about after next release). *Romain Manni-Bucau* *Twitter: @rmannibucau* *Blog: http://rmannibucau.wordpress.com* 2012/9/16 Alex The Rocker alex.m3...@gmail.com David: Thank you very much for your answer. Is the ability to remove webapps/tomee directory a durable one? Won't there be future mandatory features requiring this web app? Alex On Sun, Sep 16, 2012 at 7:29 PM, David Blevins david.blev...@gmail.com wrote: On Sep 16, 2012, at 8:16 AM, Alex The Rocker wrote: Hello, Can the webapps/tomee directory be deleted for deploying a web app to production TomEE/TomEE+ server and exposed to Internet? Indeed, when delivering our app with Tomcat, we delete all default web apps as part of a list of Tomcat hardening task list. Is there any TomEE/TomE++ vital content in webapps/tomee directory ? The only loss of functionality would be the ability to remotely execute EJBs over HTTP. However this can easily be added to a different webapp like so: servlet servlet-nameServerServlet/servlet-name servlet-classorg.apache.openejb.server.httpd.ServerServlet/servlet-class /servlet servlet-mapping servlet-nameServerServlet/servlet-name url-pattern/myejbs/*/url-pattern /servlet-mapping Then you can create an `InitialContext` that points to that webapp like so: Properties p = new Properties(); p.put(java.naming.factory.initial, org.apache.openejb.client.RemoteInitialContextFactory); p.put(java.naming.provider.url, http://127.0.0.1:8080/mywebapp/myejbs;); // user and pass optional p.put(java.naming.security.principal, myuser); p.put(java.naming.security.credentials, mypass); InitialContext ctx = new InitialContext(p); MyBean myBean = (MyBean) ctx.lookup(MyBeanRemote); -David
Re: Which JSON notations are supported by TomEE+ ?
Thks for quick answer. However, what's TomEE+ default JSON mapping ? Which components does it embbeds to support javax.ws.rs.core.MediaType.APPLICATION_JSON constant ? Alex On Thu, Sep 20, 2012 at 10:19 PM, Romain Manni-Bucau rmannibu...@gmail.comwrote: Hi i think json is not yet standardized but you can use jaxb to do so through jaxrs providers. it means youll need to bring some classes in your code but it will be portable *Romain Manni-Bucau* *Twitter: @rmannibucau* *Blog: http://rmannibucau.wordpress.com* *LinkedIn: http://www.linkedin.com/pub/romain-manni-bucau/43/544/956* 2012/9/20 Alex The Rocker alex.m3...@gmail.com Hello, I have a requirement to build a web application with JSON web services and which must be portable accross Apache TomEE+ next GA release = 1.5 ?, IBM WebSphere 8.5 and ORACLE WebLogic 12c. I'd like to use pure Java EE 6 APIs to make portability simple. I am currently confused by JAX-RS 1.1 : appart from Java EE 6’s javax.ws.rs.core.MediaType.APPLICATION_JSON constant, I don't find much about JSON in JAX-RS specifications. Is there a way to control which JSON notation is generated by JAX-RS web services in TomEE+ ? Note : uou will find in this link : http://jersey.java.net/nonav/documentation/latest/json.html#d4e949 a description of the Various JSON Notation (at least from a Jersey point of view) For example, is NATURAL notation supported by JSON implementation in TomEE+ ? If the generated JSON depends on which application server my application is deployed, then it'd make impossible writing with single source code, I'm afraid... isn't it ? Thanks, Alex.
Re: Next TomEE release date?
David: Thank you very much for your clear answer, it's alright : I understand that you're doing best effort to get 1.1.0 done for JavaOne, I guess that even if it's not ready at this time it could be available early october. I'm going to take the risk and bet on it for our project (time to have guts) Alex On Sun, Sep 16, 2012 at 3:43 AM, David Blevins david.blev...@gmail.comwrote: We're hacking on the release now, it'll be a scramble to get it done by the end of the month but should be doable. No Apache project can actually guarantee a date due to voting -- it takes a minimum of 3 days per Apache bylaws and can't be closed till certain conditions are met -- such as getting enough votes. As it's a volunteer organization and difficult to get people's time, we typically get last minute feedback that requires new binaries and a new vote and another 3 days. So the best I can say is we're trying very hard to get it out before JavaOne / end of the month. As that sounds very scary, as a point of reference, we were in this same position last year and made the before JavaOne date. We got our *first* ever 100% TCK pass on September 23rd (cutting it very close) and were able to get a release out and announcement ready by JavaOne. If we're able to get a vote started by mid week, we should be able to make it by end of the month no problem. -David On Sep 15, 2012, at 1:28 PM, Alex The Rocker wrote: Anyone here knowing TomEE/TomEE+ 1.1.0 targeted date for general availability ? On Fri, Sep 14, 2012 at 9:39 PM, Alex The Rocker alex.m3...@gmail.com wrote: Okay, I don't mind if the next release is called 1.1.0 instead of 1.0.1. However, do care to know whether or not it's still scheduled for this month before JavaOne: the application for which I'm lobbying a change from Tomcat to TomEE+ is currently in final phase for prerequisites define. They want to add REST façade, and I saw in TomEE 1.0.1 release notes (here: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12312320version=12321242 ) that there was a fix on the JAX-WS + JAX-RS cohexistence in a same web app. If TomEE 1.1.0 come too late (ie after September), then they'll reject TomEE+ and choose instead to stay with Tomcat and use Jersey for JAX-RS, which would make a TomEE+ win-back hard (I saw some threads about Jersey annoyances when deploying such apps to TomEE+) Baseline : what's the target date for 1.1.0 GA (General Availability) ? Alex On Fri, Sep 14, 2012 at 9:31 PM, Romain Manni-Bucau rmannibu...@gmail.com wrote: Yeah, i think 1.0.1 will never be released Npt = not from a phone ;) Le 14 sept. 2012 21:24, Alex The Rocker alex.m3...@gmail.com a écrit : Call me n00b if you want, but I don't catch it: do you mean that next release due for JavaOne (end of this month) is 1.1.0 ? If otherwise it's still 1.0.1, then why couldn't there be a refresh of 1.0.1 snapshot? (and btw, what do you mean by npt? I utfm but wtf, no hit ;) Alex On Fri, Sep 14, 2012 at 9:05 PM, Romain Manni-Bucau rmannibu...@gmail.comwrote: Hi, The snapshot is the 1.1.0 (npt 1.0.1). The rc will probably be skipped (we had CI issues this week and lost some days on it :(). btw we need the snapshot for the end of the month. We currently wait an openwebbeans new version then we should be able to release Le 14 sept. 2012 20:58, Alex The Rocker alex.m3...@gmail.com a écrit : Hello, I saw in dev list that a 1.0.1 release candidate should be available this week, is that still the plan? I had a look to your (useful) link with snapshots builds. Unfortunately, for 1.0.1 there is not recent snapshot here: https://repository.apache.org/content/repositories/snapshots/org/apache/openejb/apache-tomee/1.0.1-SNAPSHOT/ The most recent one is dated 7th of June. In 1.0.1 snapshots repository, there are more recent build, but since 1.0.1 is planned before JavaOne (this month I understand), I think it's safer to target 1.0.1 a prerequisite for an application to be moved from Tomcat to TomEE+. Would you please update 1.0.1 snapshot (unless a RC is actually for current wekk) ? Thanks, Alex On Sat, Sep 8, 2012 at 10:01 AM, Romain Manni-Bucau rmannibu...@gmail.comwrote: I hope a rc next week. I wrote a post to get the snapshot: http://rmannibucau.wordpress.com/2012/05/23/getting-tomee-snapshot/ Le 8 sept. 2012 09:44, Alex The Rocker alex.m3...@gmail.com a écrit : Thanks guys, Based on David's answer and given that JavaOne begins end of september, I guess we can hope for a generally available 1.0.1 at this time, right? However, I see no 1.0.1-alpha or 1.0.1-beta on the official TomEE download page. May I suggest that -even if not everything is ironed for 1.0.1- you guys post on TomEE download page links to alpha/beta
Can webapps/tomee directory be deleted for a production environment?
Hello, Can the webapps/tomee directory be deleted for deploying a web app to production TomEE/TomEE+ server and exposed to Internet? Indeed, when delivering our app with Tomcat, we delete all default web apps as part of a list of Tomcat hardening task list. Is there any TomEE/TomE++ vital content in webapps/tomee directory ? If the answer is yes, then it means that we cannot just remove webapps/tomee, so then is there a way to make this web app inaccessible to all network adapters in order to prevent its use by attackers? Alex.
Re: Can webapps/tomee directory be deleted for a production environment?
David: Thank you very much for your answer. Is the ability to remove webapps/tomee directory a durable one? Won't there be future mandatory features requiring this web app? Alex On Sun, Sep 16, 2012 at 7:29 PM, David Blevins david.blev...@gmail.comwrote: On Sep 16, 2012, at 8:16 AM, Alex The Rocker wrote: Hello, Can the webapps/tomee directory be deleted for deploying a web app to production TomEE/TomEE+ server and exposed to Internet? Indeed, when delivering our app with Tomcat, we delete all default web apps as part of a list of Tomcat hardening task list. Is there any TomEE/TomE++ vital content in webapps/tomee directory ? The only loss of functionality would be the ability to remotely execute EJBs over HTTP. However this can easily be added to a different webapp like so: servlet servlet-nameServerServlet/servlet-name servlet-classorg.apache.openejb.server.httpd.ServerServlet/servlet-class /servlet servlet-mapping servlet-nameServerServlet/servlet-name url-pattern/myejbs/*/url-pattern /servlet-mapping Then you can create an `InitialContext` that points to that webapp like so: Properties p = new Properties(); p.put(java.naming.factory.initial, org.apache.openejb.client.RemoteInitialContextFactory); p.put(java.naming.provider.url, http://127.0.0.1:8080/mywebapp/myejbs;); // user and pass optional p.put(java.naming.security.principal, myuser); p.put(java.naming.security.credentials, mypass); InitialContext ctx = new InitialContext(p); MyBean myBean = (MyBean) ctx.lookup(MyBeanRemote); -David
Re: Next TomEE release date?
Anyone here knowing TomEE/TomEE+ 1.1.0 targeted date for general availability ? On Fri, Sep 14, 2012 at 9:39 PM, Alex The Rocker alex.m3...@gmail.comwrote: Okay, I don't mind if the next release is called 1.1.0 instead of 1.0.1. However, do care to know whether or not it's still scheduled for this month before JavaOne: the application for which I'm lobbying a change from Tomcat to TomEE+ is currently in final phase for prerequisites define. They want to add REST façade, and I saw in TomEE 1.0.1 release notes (here: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12312320version=12321242) that there was a fix on the JAX-WS + JAX-RS cohexistence in a same web app. If TomEE 1.1.0 come too late (ie after September), then they'll reject TomEE+ and choose instead to stay with Tomcat and use Jersey for JAX-RS, which would make a TomEE+ win-back hard (I saw some threads about Jersey annoyances when deploying such apps to TomEE+) Baseline : what's the target date for 1.1.0 GA (General Availability) ? Alex On Fri, Sep 14, 2012 at 9:31 PM, Romain Manni-Bucau rmannibu...@gmail.com wrote: Yeah, i think 1.0.1 will never be released Npt = not from a phone ;) Le 14 sept. 2012 21:24, Alex The Rocker alex.m3...@gmail.com a écrit : Call me n00b if you want, but I don't catch it: do you mean that next release due for JavaOne (end of this month) is 1.1.0 ? If otherwise it's still 1.0.1, then why couldn't there be a refresh of 1.0.1 snapshot? (and btw, what do you mean by npt? I utfm but wtf, no hit ;) Alex On Fri, Sep 14, 2012 at 9:05 PM, Romain Manni-Bucau rmannibu...@gmail.comwrote: Hi, The snapshot is the 1.1.0 (npt 1.0.1). The rc will probably be skipped (we had CI issues this week and lost some days on it :(). btw we need the snapshot for the end of the month. We currently wait an openwebbeans new version then we should be able to release Le 14 sept. 2012 20:58, Alex The Rocker alex.m3...@gmail.com a écrit : Hello, I saw in dev list that a 1.0.1 release candidate should be available this week, is that still the plan? I had a look to your (useful) link with snapshots builds. Unfortunately, for 1.0.1 there is not recent snapshot here: https://repository.apache.org/content/repositories/snapshots/org/apache/openejb/apache-tomee/1.0.1-SNAPSHOT/ The most recent one is dated 7th of June. In 1.0.1 snapshots repository, there are more recent build, but since 1.0.1 is planned before JavaOne (this month I understand), I think it's safer to target 1.0.1 a prerequisite for an application to be moved from Tomcat to TomEE+. Would you please update 1.0.1 snapshot (unless a RC is actually for current wekk) ? Thanks, Alex On Sat, Sep 8, 2012 at 10:01 AM, Romain Manni-Bucau rmannibu...@gmail.comwrote: I hope a rc next week. I wrote a post to get the snapshot: http://rmannibucau.wordpress.com/2012/05/23/getting-tomee-snapshot/ Le 8 sept. 2012 09:44, Alex The Rocker alex.m3...@gmail.com a écrit : Thanks guys, Based on David's answer and given that JavaOne begins end of september, I guess we can hope for a generally available 1.0.1 at this time, right? However, I see no 1.0.1-alpha or 1.0.1-beta on the official TomEE download page. May I suggest that -even if not everything is ironed for 1.0.1- you guys post on TomEE download page links to alpha/beta/release candidate (whatever makes sense) builds of current stable TomEE and TomEE+, for the rest of us who aren't quite at ease with poking into source code repositories? (I'm don't even know from where to start, I had a look to support/github... and got lost) I love Eclipse download site, where nightly builds can be downloaded at any time, do we have something like this coming for TomEE/TomEE+ ? TomEE's great, I bet it will have more audience if such improvements (including a roadmap) could be provided on its home page. Alex On Sat, Sep 8, 2012 at 9:07 AM, Romain Manni-Bucau rmannibu...@gmail.com wrote: We should do it when owb will use asm instead of javassist IMO (I have some minor fixes to push next week too but should be quick) I know David is hacking on it, i can help if needed. We just should take care of iwb release time Le 8 sept. 2012 01:52, David Blevins david.blev...@gmail.com a écrit : I think it's pretty critical to get a release out before JavaOne, which is just weeks away. Might be tricky, but I think we can do it. -David
Re: Next TomEE release date?
Hello, I saw in dev list that a 1.0.1 release candidate should be available this week, is that still the plan? I had a look to your (useful) link with snapshots builds. Unfortunately, for 1.0.1 there is not recent snapshot here: https://repository.apache.org/content/repositories/snapshots/org/apache/openejb/apache-tomee/1.0.1-SNAPSHOT/ The most recent one is dated 7th of June. In 1.0.1 snapshots repository, there are more recent build, but since 1.0.1 is planned before JavaOne (this month I understand), I think it's safer to target 1.0.1 a prerequisite for an application to be moved from Tomcat to TomEE+. Would you please update 1.0.1 snapshot (unless a RC is actually for current wekk) ? Thanks, Alex On Sat, Sep 8, 2012 at 10:01 AM, Romain Manni-Bucau rmannibu...@gmail.comwrote: I hope a rc next week. I wrote a post to get the snapshot: http://rmannibucau.wordpress.com/2012/05/23/getting-tomee-snapshot/ Le 8 sept. 2012 09:44, Alex The Rocker alex.m3...@gmail.com a écrit : Thanks guys, Based on David's answer and given that JavaOne begins end of september, I guess we can hope for a generally available 1.0.1 at this time, right? However, I see no 1.0.1-alpha or 1.0.1-beta on the official TomEE download page. May I suggest that -even if not everything is ironed for 1.0.1- you guys post on TomEE download page links to alpha/beta/release candidate (whatever makes sense) builds of current stable TomEE and TomEE+, for the rest of us who aren't quite at ease with poking into source code repositories? (I'm don't even know from where to start, I had a look to support/github... and got lost) I love Eclipse download site, where nightly builds can be downloaded at any time, do we have something like this coming for TomEE/TomEE+ ? TomEE's great, I bet it will have more audience if such improvements (including a roadmap) could be provided on its home page. Alex On Sat, Sep 8, 2012 at 9:07 AM, Romain Manni-Bucau rmannibu...@gmail.com wrote: We should do it when owb will use asm instead of javassist IMO (I have some minor fixes to push next week too but should be quick) I know David is hacking on it, i can help if needed. We just should take care of iwb release time Le 8 sept. 2012 01:52, David Blevins david.blev...@gmail.com a écrit : I think it's pretty critical to get a release out before JavaOne, which is just weeks away. Might be tricky, but I think we can do it. -David On Sep 7, 2012, at 4:01 PM, Jeremyau wrote: I'm really interested about this question as well since there is a couple of issues that have been fixed. (Hibernate, Grails...) Has someone an idea about that? -- View this message in context: http://openejb.979440.n4.nabble.com/Next-TomEE-release-date-tp4657315p4657331.html Sent from the OpenEJB User mailing list archive at Nabble.com.
Re: Next TomEE release date?
Call me n00b if you want, but I don't catch it: do you mean that next release due for JavaOne (end of this month) is 1.1.0 ? If otherwise it's still 1.0.1, then why couldn't there be a refresh of 1.0.1 snapshot? (and btw, what do you mean by npt? I utfm but wtf, no hit ;) Alex On Fri, Sep 14, 2012 at 9:05 PM, Romain Manni-Bucau rmannibu...@gmail.comwrote: Hi, The snapshot is the 1.1.0 (npt 1.0.1). The rc will probably be skipped (we had CI issues this week and lost some days on it :(). btw we need the snapshot for the end of the month. We currently wait an openwebbeans new version then we should be able to release Le 14 sept. 2012 20:58, Alex The Rocker alex.m3...@gmail.com a écrit : Hello, I saw in dev list that a 1.0.1 release candidate should be available this week, is that still the plan? I had a look to your (useful) link with snapshots builds. Unfortunately, for 1.0.1 there is not recent snapshot here: https://repository.apache.org/content/repositories/snapshots/org/apache/openejb/apache-tomee/1.0.1-SNAPSHOT/ The most recent one is dated 7th of June. In 1.0.1 snapshots repository, there are more recent build, but since 1.0.1 is planned before JavaOne (this month I understand), I think it's safer to target 1.0.1 a prerequisite for an application to be moved from Tomcat to TomEE+. Would you please update 1.0.1 snapshot (unless a RC is actually for current wekk) ? Thanks, Alex On Sat, Sep 8, 2012 at 10:01 AM, Romain Manni-Bucau rmannibu...@gmail.comwrote: I hope a rc next week. I wrote a post to get the snapshot: http://rmannibucau.wordpress.com/2012/05/23/getting-tomee-snapshot/ Le 8 sept. 2012 09:44, Alex The Rocker alex.m3...@gmail.com a écrit : Thanks guys, Based on David's answer and given that JavaOne begins end of september, I guess we can hope for a generally available 1.0.1 at this time, right? However, I see no 1.0.1-alpha or 1.0.1-beta on the official TomEE download page. May I suggest that -even if not everything is ironed for 1.0.1- you guys post on TomEE download page links to alpha/beta/release candidate (whatever makes sense) builds of current stable TomEE and TomEE+, for the rest of us who aren't quite at ease with poking into source code repositories? (I'm don't even know from where to start, I had a look to support/github... and got lost) I love Eclipse download site, where nightly builds can be downloaded at any time, do we have something like this coming for TomEE/TomEE+ ? TomEE's great, I bet it will have more audience if such improvements (including a roadmap) could be provided on its home page. Alex On Sat, Sep 8, 2012 at 9:07 AM, Romain Manni-Bucau rmannibu...@gmail.com wrote: We should do it when owb will use asm instead of javassist IMO (I have some minor fixes to push next week too but should be quick) I know David is hacking on it, i can help if needed. We just should take care of iwb release time Le 8 sept. 2012 01:52, David Blevins david.blev...@gmail.com a écrit : I think it's pretty critical to get a release out before JavaOne, which is just weeks away. Might be tricky, but I think we can do it. -David On Sep 7, 2012, at 4:01 PM, Jeremyau wrote: I'm really interested about this question as well since there is a couple of issues that have been fixed. (Hibernate, Grails...) Has someone an idea about that? -- View this message in context: http://openejb.979440.n4.nabble.com/Next-TomEE-release-date-tp4657315p4657331.html Sent from the OpenEJB User mailing list archive at Nabble.com.
Re: Next TomEE release date?
Okay, I don't mind if the next release is called 1.1.0 instead of 1.0.1. However, do care to know whether or not it's still scheduled for this month before JavaOne: the application for which I'm lobbying a change from Tomcat to TomEE+ is currently in final phase for prerequisites define. They want to add REST façade, and I saw in TomEE 1.0.1 release notes (here: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12312320version=12321242) that there was a fix on the JAX-WS + JAX-RS cohexistence in a same web app. If TomEE 1.1.0 come too late (ie after September), then they'll reject TomEE+ and choose instead to stay with Tomcat and use Jersey for JAX-RS, which would make a TomEE+ win-back hard (I saw some threads about Jersey annoyances when deploying such apps to TomEE+) Baseline : what's the target date for 1.1.0 GA (General Availability) ? Alex On Fri, Sep 14, 2012 at 9:31 PM, Romain Manni-Bucau rmannibu...@gmail.comwrote: Yeah, i think 1.0.1 will never be released Npt = not from a phone ;) Le 14 sept. 2012 21:24, Alex The Rocker alex.m3...@gmail.com a écrit : Call me n00b if you want, but I don't catch it: do you mean that next release due for JavaOne (end of this month) is 1.1.0 ? If otherwise it's still 1.0.1, then why couldn't there be a refresh of 1.0.1 snapshot? (and btw, what do you mean by npt? I utfm but wtf, no hit ;) Alex On Fri, Sep 14, 2012 at 9:05 PM, Romain Manni-Bucau rmannibu...@gmail.comwrote: Hi, The snapshot is the 1.1.0 (npt 1.0.1). The rc will probably be skipped (we had CI issues this week and lost some days on it :(). btw we need the snapshot for the end of the month. We currently wait an openwebbeans new version then we should be able to release Le 14 sept. 2012 20:58, Alex The Rocker alex.m3...@gmail.com a écrit : Hello, I saw in dev list that a 1.0.1 release candidate should be available this week, is that still the plan? I had a look to your (useful) link with snapshots builds. Unfortunately, for 1.0.1 there is not recent snapshot here: https://repository.apache.org/content/repositories/snapshots/org/apache/openejb/apache-tomee/1.0.1-SNAPSHOT/ The most recent one is dated 7th of June. In 1.0.1 snapshots repository, there are more recent build, but since 1.0.1 is planned before JavaOne (this month I understand), I think it's safer to target 1.0.1 a prerequisite for an application to be moved from Tomcat to TomEE+. Would you please update 1.0.1 snapshot (unless a RC is actually for current wekk) ? Thanks, Alex On Sat, Sep 8, 2012 at 10:01 AM, Romain Manni-Bucau rmannibu...@gmail.comwrote: I hope a rc next week. I wrote a post to get the snapshot: http://rmannibucau.wordpress.com/2012/05/23/getting-tomee-snapshot/ Le 8 sept. 2012 09:44, Alex The Rocker alex.m3...@gmail.com a écrit : Thanks guys, Based on David's answer and given that JavaOne begins end of september, I guess we can hope for a generally available 1.0.1 at this time, right? However, I see no 1.0.1-alpha or 1.0.1-beta on the official TomEE download page. May I suggest that -even if not everything is ironed for 1.0.1- you guys post on TomEE download page links to alpha/beta/release candidate (whatever makes sense) builds of current stable TomEE and TomEE+, for the rest of us who aren't quite at ease with poking into source code repositories? (I'm don't even know from where to start, I had a look to support/github... and got lost) I love Eclipse download site, where nightly builds can be downloaded at any time, do we have something like this coming for TomEE/TomEE+ ? TomEE's great, I bet it will have more audience if such improvements (including a roadmap) could be provided on its home page. Alex On Sat, Sep 8, 2012 at 9:07 AM, Romain Manni-Bucau rmannibu...@gmail.com wrote: We should do it when owb will use asm instead of javassist IMO (I have some minor fixes to push next week too but should be quick) I know David is hacking on it, i can help if needed. We just should take care of iwb release time Le 8 sept. 2012 01:52, David Blevins david.blev...@gmail.com a écrit : I think it's pretty critical to get a release out before JavaOne, which is just weeks away. Might be tricky, but I think we can do it. -David On Sep 7, 2012, at 4:01 PM, Jeremyau wrote: I'm really interested about this question as well since there is a couple of issues that have
Re: Any risk of using tomcat7.exe instead of TomEE.amd64.exe ?
Hello, Your (kind) answers seem to focus on UNIX starter, but again what' the risk of starting TomEE+ on Windows using tomcat7.exe / tomcat7w.exe for service registration ? To clarify my need: I try to make people believe in TomEE+ can be an easy replacement for Tomcat (and after, lobby for EE feature to be used). For this, I'm trying to replace Tomcat by TomEE in an app without even modifying this installer's app (but I can create a media for this app with TomEE expanded in same dir as Tomcat used to be). Devil is in details, I don't know if TomEE's registration as a Windows service can work strictly like Tomcat's, any clue appreciated ! On Tue, Sep 11, 2012 at 10:04 PM, Romain Manni-Bucau rmannibu...@gmail.comwrote: not really we hack for endorsed dir for java 7 too (in catalina.sh) *Romain Manni-Bucau* *Twitter: @rmannibucau* *Blog: http://rmannibucau.wordpress.com* 2012/9/11 David Blevins david.blev...@gmail.com On Sep 9, 2012, at 1:07 PM, Alex The Rocker wrote: Hello, I am testing the drop-in replacement of Tomcat by TomEE+ for a server application running on 64-bit Windows For the moment, I want minimal changes in this application's installer. This application's installer registers the application server as a service. I noticed that tomcat7.exe is missing from Windows (ZIP) distribution of TomEE+ 1.0.1, there's TomEE.amd64.exe and a service.bat stuff. I am wondering if I would run into a wall by just copying Tomcat 7.0.27's tomcat7.exe into bin/ directory and let the application installer register the service as if TomEE+ were Tomcat. Any opinion? What's different between TomEE.amd64.exe tomcat7.exe, appart form the exe's name? Andy Gumbrecht (Cc'ed) made it IIRC. I know in terms of the ./catalina.sh, the only change we make is adding the -javaagent flag which is only required if using OpenJPA as your JPA provider and you want runtime JPA enhancement (as opposed to doing it at build time). I suspect that's the main difference, but probably Andy can say for certain. -David
Re: Any risk of using tomcat7.exe instead of TomEE.amd64.exe ?
Thanks, since there's currently no JPA in the application, so I guess 1) not mandatory at this time. About : 2) the JDK 7 used by this app (which actually installs it from its media) has no endorsed/ directory, if that's what you mean. In that case, can I just copy tomcat7.exe / tomcat7w.exe from a Tomcat 7 distribution at same version as TomEE+ 1.0.0, and repackage TomEE+ 1.0.0 in this application and let its installer register TomEE+ as a Windows service just like if it were Tomcat ? (sorry if those questions are trivial, I have one slot for this experience - a nightly build in which i'm allowed to make the experiment, I'd rather be successful, or TomEE+ adoption there will be slower, people are always kind of scared by changes...) Alex On Tue, Sep 11, 2012 at 10:24 PM, Romain Manni-Bucau rmannibu...@gmail.comwrote: two previous mentionned hacks are true under windows too the main differences are the following ones: 1) need of javaagent for not enhanced JPA entity with OpenJPA (not recommanded BTW) 2) endorsed dir should be empty for java 7 (done automatically in startup scripts switching of folder but doing it manually is fine too if you want to keep endorsed dir) *Romain Manni-Bucau* *Twitter: @rmannibucau* *Blog: http://rmannibucau.wordpress.com* 2012/9/11 Alex The Rocker alex.m3...@gmail.com Hello, Your (kind) answers seem to focus on UNIX starter, but again what' the risk of starting TomEE+ on Windows using tomcat7.exe / tomcat7w.exe for service registration ? To clarify my need: I try to make people believe in TomEE+ can be an easy replacement for Tomcat (and after, lobby for EE feature to be used). For this, I'm trying to replace Tomcat by TomEE in an app without even modifying this installer's app (but I can create a media for this app with TomEE expanded in same dir as Tomcat used to be). Devil is in details, I don't know if TomEE's registration as a Windows service can work strictly like Tomcat's, any clue appreciated ! On Tue, Sep 11, 2012 at 10:04 PM, Romain Manni-Bucau rmannibu...@gmail.comwrote: not really we hack for endorsed dir for java 7 too (in catalina.sh) *Romain Manni-Bucau* *Twitter: @rmannibucau* *Blog: http://rmannibucau.wordpress.com* 2012/9/11 David Blevins david.blev...@gmail.com On Sep 9, 2012, at 1:07 PM, Alex The Rocker wrote: Hello, I am testing the drop-in replacement of Tomcat by TomEE+ for a server application running on 64-bit Windows For the moment, I want minimal changes in this application's installer. This application's installer registers the application server as a service. I noticed that tomcat7.exe is missing from Windows (ZIP) distribution of TomEE+ 1.0.1, there's TomEE.amd64.exe and a service.bat stuff. I am wondering if I would run into a wall by just copying Tomcat 7.0.27's tomcat7.exe into bin/ directory and let the application installer register the service as if TomEE+ were Tomcat. Any opinion? What's different between TomEE.amd64.exe tomcat7.exe, appart form the exe's name? Andy Gumbrecht (Cc'ed) made it IIRC. I know in terms of the ./catalina.sh, the only change we make is adding the -javaagent flag which is only required if using OpenJPA as your JPA provider and you want runtime JPA enhancement (as opposed to doing it at build time). I suspect that's the main difference, but probably Andy can say for certain. -David
Re: Any risk of using tomcat7.exe instead of TomEE.amd64.exe ?
Thanks, all I need now is a TomEE 1.0.1 RC (because of the problem with space around the load-on-startup value in this app's web.xml), I read it's supposed to come this week. Impatiently, Alex On Tue, Sep 11, 2012 at 10:52 PM, Romain Manni-Bucau rmannibu...@gmail.comwrote: sounds rather good ;) *Romain Manni-Bucau* *Twitter: @rmannibucau* *Blog: http://rmannibucau.wordpress.com* 2012/9/11 Alex The Rocker alex.m3...@gmail.com Thanks, since there's currently no JPA in the application, so I guess 1) not mandatory at this time. About : 2) the JDK 7 used by this app (which actually installs it from its media) has no endorsed/ directory, if that's what you mean. In that case, can I just copy tomcat7.exe / tomcat7w.exe from a Tomcat 7 distribution at same version as TomEE+ 1.0.0, and repackage TomEE+ 1.0.0 in this application and let its installer register TomEE+ as a Windows service just like if it were Tomcat ? (sorry if those questions are trivial, I have one slot for this experience - a nightly build in which i'm allowed to make the experiment, I'd rather be successful, or TomEE+ adoption there will be slower, people are always kind of scared by changes...) Alex On Tue, Sep 11, 2012 at 10:24 PM, Romain Manni-Bucau rmannibu...@gmail.comwrote: two previous mentionned hacks are true under windows too the main differences are the following ones: 1) need of javaagent for not enhanced JPA entity with OpenJPA (not recommanded BTW) 2) endorsed dir should be empty for java 7 (done automatically in startup scripts switching of folder but doing it manually is fine too if you want to keep endorsed dir) *Romain Manni-Bucau* *Twitter: @rmannibucau* *Blog: http://rmannibucau.wordpress.com* 2012/9/11 Alex The Rocker alex.m3...@gmail.com Hello, Your (kind) answers seem to focus on UNIX starter, but again what' the risk of starting TomEE+ on Windows using tomcat7.exe / tomcat7w.exe for service registration ? To clarify my need: I try to make people believe in TomEE+ can be an easy replacement for Tomcat (and after, lobby for EE feature to be used). For this, I'm trying to replace Tomcat by TomEE in an app without even modifying this installer's app (but I can create a media for this app with TomEE expanded in same dir as Tomcat used to be). Devil is in details, I don't know if TomEE's registration as a Windows service can work strictly like Tomcat's, any clue appreciated ! On Tue, Sep 11, 2012 at 10:04 PM, Romain Manni-Bucau rmannibu...@gmail.comwrote: not really we hack for endorsed dir for java 7 too (in catalina.sh) *Romain Manni-Bucau* *Twitter: @rmannibucau* *Blog: http://rmannibucau.wordpress.com* 2012/9/11 David Blevins david.blev...@gmail.com On Sep 9, 2012, at 1:07 PM, Alex The Rocker wrote: Hello, I am testing the drop-in replacement of Tomcat by TomEE+ for a server application running on 64-bit Windows For the moment, I want minimal changes in this application's installer. This application's installer registers the application server as a service. I noticed that tomcat7.exe is missing from Windows (ZIP) distribution of TomEE+ 1.0.1, there's TomEE.amd64.exe and a service.bat stuff. I am wondering if I would run into a wall by just copying Tomcat 7.0.27's tomcat7.exe into bin/ directory and let the application installer register the service as if TomEE+ were Tomcat. Any opinion? What's different between TomEE.amd64.exe tomcat7.exe, appart form the exe's name? Andy Gumbrecht (Cc'ed) made it IIRC. I know in terms of the ./catalina.sh, the only change we make is adding the -javaagent flag which is only required if using OpenJPA as your JPA provider and you want runtime JPA enhancement (as opposed to doing it at build time). I suspect that's the main difference, but probably Andy can say for certain. -David
Re: How to relax TomEE+ validation of web.xml (white space in load-on-startup value) ?
Romain: How do you skip the validation? Any pointer to instruction will be helpful :) As for the JIRA, on this topic, done: https://issues.apache.org/jira/browse/TOMEE-410 I hope it's precise enough (it's my first JIRA!) Alex On Sun, Sep 9, 2012 at 1:52 PM, Romain Manni-Bucau rmannibu...@gmail.comwrote: Currently you can skip the validation only i think. But please open a jira we can easily fix it in our validator Le 8 sept. 2012 22:30, Alex The Rocker alex.m3...@gmail.com a écrit : Hello, I have been lobbying people with an optimistic TomEE+ accept OOTB any web app which can be deployed on Tomcat 7. Unfortunately, somebody made me feel ridiculous. The case is very simple: a web app with this line: load-on-startup 1 /load-on-startup (notice the space character before and after the '1' value). Of course it would be obvious to fix the web app, but my problem is that it just works with this syntax with Tomcat 7.0.27, and not with TomEE+ 1.0.0, so the compatibility is broken here. Anyway, Is there some kind of setting in TomEE+ which I could set to make it actually compatible with Tomcat from web.xml validation standpoint ? Thanks, Alex
Re: How to relax TomEE+ validation of web.xml (white space in load-on-startup value) ?
wow, you TomEE guys are so fast: the issue has been fixed about 10 minutes after I posted the JIRA :) However, in the closure text, I see no target release : does it means it's too late for this fix to be part of TomEE(+) 1.0.1 ? Alex On Sun, Sep 9, 2012 at 3:43 PM, Alex The Rocker alex.m3...@gmail.comwrote: Romain: How do you skip the validation? Any pointer to instruction will be helpful :) As for the JIRA, on this topic, done: https://issues.apache.org/jira/browse/TOMEE-410 I hope it's precise enough (it's my first JIRA!) Alex On Sun, Sep 9, 2012 at 1:52 PM, Romain Manni-Bucau rmannibu...@gmail.comwrote: Currently you can skip the validation only i think. But please open a jira we can easily fix it in our validator Le 8 sept. 2012 22:30, Alex The Rocker alex.m3...@gmail.com a écrit : Hello, I have been lobbying people with an optimistic TomEE+ accept OOTB any web app which can be deployed on Tomcat 7. Unfortunately, somebody made me feel ridiculous. The case is very simple: a web app with this line: load-on-startup 1 /load-on-startup (notice the space character before and after the '1' value). Of course it would be obvious to fix the web app, but my problem is that it just works with this syntax with Tomcat 7.0.27, and not with TomEE+ 1.0.0, so the compatibility is broken here. Anyway, Is there some kind of setting in TomEE+ which I could set to make it actually compatible with Tomcat from web.xml validation standpoint ? Thanks, Alex
Any risk of using tomcat7.exe instead of TomEE.amd64.exe ?
Hello, I am testing the drop-in replacement of Tomcat by TomEE+ for a server application running on 64-bit Windows For the moment, I want minimal changes in this application's installer. This application's installer registers the application server as a service. I noticed that tomcat7.exe is missing from Windows (ZIP) distribution of TomEE+ 1.0.1, there's TomEE.amd64.exe and a service.bat stuff. I am wondering if I would run into a wall by just copying Tomcat 7.0.27's tomcat7.exe into bin/ directory and let the application installer register the service as if TomEE+ were Tomcat. Any opinion? What's different between TomEE.amd64.exe tomcat7.exe, appart form the exe's name? Alex
Re: Next TomEE release date?
Thanks guys, Based on David's answer and given that JavaOne begins end of september, I guess we can hope for a generally available 1.0.1 at this time, right? However, I see no 1.0.1-alpha or 1.0.1-beta on the official TomEE download page. May I suggest that -even if not everything is ironed for 1.0.1- you guys post on TomEE download page links to alpha/beta/release candidate (whatever makes sense) builds of current stable TomEE and TomEE+, for the rest of us who aren't quite at ease with poking into source code repositories? (I'm don't even know from where to start, I had a look to support/github... and got lost) I love Eclipse download site, where nightly builds can be downloaded at any time, do we have something like this coming for TomEE/TomEE+ ? TomEE's great, I bet it will have more audience if such improvements (including a roadmap) could be provided on its home page. Alex On Sat, Sep 8, 2012 at 9:07 AM, Romain Manni-Bucau rmannibu...@gmail.comwrote: We should do it when owb will use asm instead of javassist IMO (I have some minor fixes to push next week too but should be quick) I know David is hacking on it, i can help if needed. We just should take care of iwb release time Le 8 sept. 2012 01:52, David Blevins david.blev...@gmail.com a écrit : I think it's pretty critical to get a release out before JavaOne, which is just weeks away. Might be tricky, but I think we can do it. -David On Sep 7, 2012, at 4:01 PM, Jeremyau wrote: I'm really interested about this question as well since there is a couple of issues that have been fixed. (Hibernate, Grails...) Has someone an idea about that? -- View this message in context: http://openejb.979440.n4.nabble.com/Next-TomEE-release-date-tp4657315p4657331.html Sent from the OpenEJB User mailing list archive at Nabble.com.
Next TomEE release date?
Hello, Apache Tomcat just release version 7.0.30. How far are we from a new release of Apache TomEE / TomEE+ ? Are you considering to post a release schedule, a la Firefox ? Thanks, Alex
Frequency of Tomcat version updates in TomEE ?
Hello, We are considering Apache TomEE+, but we are concerned by the lack of clear update policy of Tomcat version in TomEE TomEE+. Today (16th of July 2012): - Apache TomEE(+) 1.0 is available with embedded Apache Tomcat 7.0.27 - Apache Tomcat 7.0.29 is available since 8th of July. Although there is no know security vulnerabilities in Tomcat 7.0.27, it would be nice to have a clear statement on Apache TomEE/TomEE+ update policy with regard to the components it embeds (and not only Apache Tomcat) ; so that users could decide whether or not they want to bed on this new J2EE application server (yeah, we know it's J2EE with web profile). A commitment to update TomEE TomEE+ when an Apache Tomcat fix of security vulnerabilities within very short time (2 weeks) would clearly be nice, if possible. Regards, Alex
Re: Frequency of Tomcat version updates in TomEE ?
Well, the Download tab (http://openejb.apache.org/downloads.html) show a list of fixes for TomEE / TomEE+ 1.0 which show that Tomcat version is 2.0.27 (we understand that were was a typo and 7.0.27). Where is it mentionned that Tomcat 7.0.29 is part of 1.0, if it is ? Alex On Mon, Jul 16, 2012 at 9:51 PM, Romain Manni-Bucau rmannibu...@gmail.comwrote: Hi, we have no official position regarding it from what i know but here two points: 1) if you look last update of tomcat or security update (i think of cxf) it took 2 days for the snapshot (we are already on tomcat 7.0.29) 2) regarding releases we are working on the 1.1.0 and then we'll refactor our trunk to ease releases so it should be more frequent 3) a lot of companies use TomEE and are concerned by security updates (including committer companies) so updates will be done - Romain 2012/7/16 Alex The Rocker alex.m3...@gmail.com Hello, We are considering Apache TomEE+, but we are concerned by the lack of clear update policy of Tomcat version in TomEE TomEE+. Today (16th of July 2012): - Apache TomEE(+) 1.0 is available with embedded Apache Tomcat 7.0.27 - Apache Tomcat 7.0.29 is available since 8th of July. Although there is no know security vulnerabilities in Tomcat 7.0.27, it would be nice to have a clear statement on Apache TomEE/TomEE+ update policy with regard to the components it embeds (and not only Apache Tomcat) ; so that users could decide whether or not they want to bed on this new J2EE application server (yeah, we know it's J2EE with web profile). A commitment to update TomEE TomEE+ when an Apache Tomcat fix of security vulnerabilities within very short time (2 weeks) would clearly be nice, if possible. Regards, Alex
