So, I haven't settled on any particular EE container. I like the fact I
can manage the different Glassfish aspects via a web interface and that
it is so "reference" and just works. I disagree with the not working
statement as the nature of this thread is: it didn't work out of the box
with TomEE for me. I know Tomcat has a web interface, too, but it' s
very basic. Obviously I have been spoiled by point'n'click M$ software,
but I am also running a Linux workstation with a Windows 7 VM just for
the .NET stuff. So you see my clear preference right there. And
command-line is second nature to me.
Anyway, this is for a different discussion, I think.
Thanks guys for helping me with this. It probably won't be the last time
I'm posting to this user group as I clearly intend on getting more
involved with Java and TomEE.
Kay
On 12/13/2012 03:25 PM, Howard W. Smith, Jr. wrote:
I recommend 1.5.1 and I prefer it over Glassfish? Why, because I don't make
sticking with it...to make it work.
TomEE and CDI-managed-beans and the not-so-real Apache Derby database on my
slow/old Windows Server 2003 32bit 4GB RAM is performing just as good as
Glassfish 3.1.2.2. I'm just learning 'how' to use TomEE, correctly and
efficiently.
Please make that sale.. TomEE/CDI... defintely not .NET. :)
Glassfish/WELD for CDI? i was not able to make it work at all, too hard,
too complicated... someone else told me recently, they heard all my
buzz/chatter in many different forums, they had/have Glassfish/WELD for CDI
and it's working good in production forthem, but they tried
TomEE/CDI-managed-beans, and that person said... it 'feels' faster than
Glassfish/WELD.
I like the tomEE committers big time! go with tomEE. :)
On Thu, Dec 13, 2012 at 4:15 PM, Romain Manni-Bucau
<[email protected]>wrote:
you'll not get issue with your management, the 1.5.1 release passed,
we just wait Jean-Louis to push binaries on repo1 :)
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2012/12/13 Kay Wrobel <[email protected]>:
It does when you check the "Enable Context and Dependency Injection"
check
box.
Kay Wrobel
MIS Associate
*Hawk Electronics, Inc.*
800-THE-HAWK
800-843-4295
[email protected]
On 12/13/2012 03:08 PM, Romain Manni-Bucau wrote:
Question from a none netbeans user: when creating a new JavaEE 6
project netbeans doesn't create a beans.xml?
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2012/12/13 Howard W. Smith, Jr. <[email protected]>:
I struggled getting mine to work as well, but I was advised to either
add
beans.xml to WEB-INF or META-INF folder.
I learned that in NetBeans, for META-INF, you create a new folder in
the
same folder that contain all your java code. Netbeans does not like
META-INF/beans.xml, you get squiggly lines etc when trying to code, so
the
full path of mine is as follows:
C:\Users\Public\NetBeansProjects\mcms_tomee\web\WEB-INF\beans.xml
Empty beans.xml would be like the following:
<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://java.sun.com/xml/ns/javaee";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
http://java.sun.com/xml/ns/javaee/beans_1_0.xsd";>
</beans>
On Thu, Dec 13, 2012 at 3:56 PM, Kay Wrobel <[email protected]>
wrote:
Now CDI is item number one in the feature list of TomEE Web Profile
and
has been since version 1.0 if I remember correctly. I just can't get
it
to
work...
--
------------------------------
The information in this e-mail is confidential and is intended solely for
the addressee(s). Access to this email by anyone else is unauthorized. If
you are not an intended recipient, you may not print, save or otherwise
store the e-mail or any of the contents thereof in electronic or physical
form, nor copy, use or disseminate the information contained in the
email.
If you are not an intended recipient, please notify the sender of this
email immediately.
--
------------------------------
The information in this e-mail is confidential and is intended solely for
the addressee(s). Access to this email by anyone else is unauthorized. If
you are not an intended recipient, you may not print, save or otherwise
store the e-mail or any of the contents thereof in electronic or physical
form, nor copy, use or disseminate the information contained in the email.
If you are not an intended recipient, please notify the sender of this
email immediately.
