added a message to not use start/stop when called for now. Will at least
limit the ambiguity.
Romain Manni-Bucau
@rmannibucau https://twitter.com/rmannibucau | Blog
http://rmannibucau.wordpress.com | Github https://github.com/rmannibucau |
LinkedIn https://www.linkedin.com/in/rmannibucau |
Yeah, I would agree with removing them. They have no obvious value, are
confusing and need to be maintained.
On Sun, Aug 30, 2015 at 9:41 AM Gurkan Erdogdu
gurkanerdo...@yahoo.com.invalid wrote:
It may not break anything because the fix is handled in exception case and
the problem is very
Hi Gurkan,
It would probably be better to fix the issue instead of working it around
in the Assembler. Here few question to try to nail it down:
- we are several to have tested tomee under windows lately and we didnt get
it so what is different with your setup (home/base? custom classpath?
Hi Romain
tomee.sh is a great because it starts standalone OpenEJB server, not TomEE.
Therefore, I think that we have to fix the exception problem :) Otherwise, may
not put these scripts to bin/ folder. Some customers play with TomEE and when
gets exception like this, they think that it is
It may not break anything because the fix is handled in exception case and the
problem is very clear, but I am not sure :)
Otherwise, as you said we can redirect these scripts to catalina.sh or
completely remove the scripts.
Best
Gurkan
On Sunday, August 30, 2015 5:39 PM, Romain
Hi Romain
I downloaded the apache-tomee-1.7.2-plus.tar.gz and I run it in Mac OSX
Yosemite 10.10.4 with JDK 1.7.0_72-b14. There is no custom configuration.
Reproduce of the issue:
1- Download fresh TomEE Plus 1.7.2 from
http://tomee.apache.org/downloads.html2- Untar it to any folder3- cd bin/
2015-08-30 17:40 GMT+02:00 Gurkan Erdogdu gurkanerdo...@yahoo.com:
It may not break anything because the fix is handled in exception case and
the problem is very clear, but I am not sure :)
it does since all apps will no more be properly handled by tomcat so all
features coming from tomcat
2015-08-30 18:05 GMT+02:00 Gurkan Erdogdu gurkanerdo...@yahoo.com.invalid:
I debug the standalone openejb and tomee, somehow openejb-core is filtered
in default openejb server but not filtered in tomee.
When I add openejb.deployments.classpath = false to the system.properties
file, then
Oh I see!
tomee.sh start/stop commands are not intended to be used with tomee ATM,
they are inherited from openejb embedded but dont start/stop tomee like a
tomcat, we should redirect them to catalina.sh I think. This sounds like a
better fix ;).
./catalina.sh run or start shouldnt have any
I debug the standalone openejb and tomee, somehow openejb-core is filtered in
default openejb server but not filtered in tomee.
When I add openejb.deployments.classpath = false to the system.properties file,
then openejb-core is filtered and the problem disappears.
But as you said, there are
2015-08-30 16:32 GMT+02:00 Gurkan Erdogdu gurkanerdo...@yahoo.com.invalid:
Hi Romain
tomee.sh is a great because it starts standalone OpenEJB server, not
TomEE. Therefore, I think that we have to fix the exception problem :)
Otherwise, may not put these scripts to bin/ folder. Some customers
11 matches
Mail list logo
