Depends what you do and the knowledge and heterogeneous state of your apps.
If they are inconsistent or very different in term of stack spring is good
but if in each app you do the same spring boot will need more knowledge to
work correctly - so it means you will get more copy paste in the apps so
I think so too.
It should be good to have a real solution to run as jar, with
"application.properties" out of the box.
I made it myself, with my own extension of tome-embedded (I load a properties
and put it in System.properties to override some config files for datasources
and so on).
I rea
What do you miss? Properties can be set on the config IIRC.
That said for big companies not using container deployment makes all the
responsabilities - security, fixes, upgrades... - on dev teams..which is
never a guarantee of a good maintenance cause of project constraints from
my experience. So
MyFaces 2.2.8, but the root of the problem was that OmniFaces 2.x requires
CDI 1.1...
2016-01-04 12:21 GMT-02:00 Howard W. Smith, Jr. :
> Interesting. I did not have any issues. I always deploy OmniFaces JAR
> in/with my WAR file. Felipe, are you using MyFaces 2.2.x or 2.1.x?
> On Jan 4, 2016 7:2
config IIRC ? What do you mean ?
From my point of view, most often production team are unable to manage
correctly the application servers... They want to work less...
Here, with Weblogic for now, this is hell.
One jar + one properties is the top for this type of guys, and this will free
us lo
Le 5 janv. 2016 14:09, "Yann BLAZART"
a écrit :
>
> config IIRC ? What do you mean ?
>
> From my point of view, most often production team are unable to manage
correctly the application servers... They want to work less...
>
So dev should enable it but saw several companies working fine and fast
Hmmm,
so earlier you said,
I had problems with OmniFaces 2.x + TomEE 1.7.2
and
On Tue, Jan 5, 2016 at 5:47 AM, Felipe Jaekel wrote:
> MyFaces 2.2.8, but the root of the problem was that OmniFaces 2.x requires
> CDI 1.1...
>
Would probably need to know more about your stack to determine why
I used Spring for several years, but JEE has matured to such a level that
it really doesn't make sense any more from my perspective. Unless you have
a ton of legacy Spring code with a bunch of Spring only developers perhaps
(this is not good in a general sense). The thing I'd say to your boss and
p
the default that came with tomee1.7.2
--
View this message in context:
http://tomee-openejb.979440.n4.nabble.com/what-omnifaces-version-use-with-tomee-1-7-tp4677331p4677359.html
Sent from the TomEE Users mailing list archive at Nabble.com.
Platform is Debian linux/jessie, tomcat 8.0.30
I deleted the existing tomee.war from tomcat8 installation
(tomee-plus-webapp-7.0.0-20150518.041035.war)
Waited for tomee directory to be removed and then copied
tomee-plus-7.0.0-m1.war file as tomee.war.
Browsed to http://localhost/tomee and the pag
Hi
Should check the list but IIRC we removed the gui.
Did you use it for anything else than checking the server is up?
Le 5 janv. 2016 18:20, "adrianh" a écrit :
> Platform is Debian linux/jessie, tomcat 8.0.30
>
> I deleted the existing tomee.war from tomcat8 installation
> (tomee-plus-webapp-
Think a project created with mvn ans pushed on github would save the time
spent on this list "wondering if" guys ;).
Le 5 janv. 2016 18:04, "mauro2java2011" a écrit :
> the default that came with tomee1.7.2
>
>
>
> --
> View this message in context:
> http://tomee-openejb.979440.n4.nabble.com/wha
FYI
https://github.com/omnifaces/omnifaces/issues/193
Le 5 janv. 2016 18:54, "Romain Manni-Bucau" a
écrit :
> Think a project created with mvn ans pushed on github would save the time
> spent on this list "wondering if" guys ;).
> Le 5 janv. 2016 18:04, "mauro2java2011" a
> écrit :
>
>> the def
13 matches
Mail list logo
