Re: EAR deployment

jgallimore wrote > I know its been a while... I did just commit a patch for this issue: > https://issues.apache.org/jira/browse/TOMEE-2532 and I'd be curious if > this > helps with this issue at all. I'll run my own test when I get a sec, but > if > you're able to give it a go, that would be awesom

Re: EAR deployment

Actually, I could check this out in the nightly build -- assuming this change will go into the nightly build? If that is the case, I can check by the end of the week. Ross -- Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Users-f979441.html

Re: EAR deployment

@gmail.com> wrote: > >> Thanks, that's useful. >> >> Jon >> >> On Mon, Aug 13, 2018 at 3:15 PM, wrote: >> >>> Security policy is very simple right now: >>> >>> grant { >>> permission java.security.AllPermission;

Re: wtp ear deployment

https://gist.github.com/chongma/d558400763d354d2c2bbd311f4798028 On 12/12/2018 16:55, Jonathan Gallimore wrote: Can you paste your full deployment output into a gist or similar? I'm happy to have a go an example towards the end of the week. Jon On Wed, Dec 12, 2018 at 3:52 PM Matthew Broadhead

Re: wtp ear deployment

Can you paste your full deployment output into a gist or similar? I'm happy to have a go an example towards the end of the week. Jon On Wed, Dec 12, 2018 at 3:52 PM Matthew Broadhead wrote: > i fixed the first error. i had put > unzip:org.keycloak:keycloak-tomcat8-adapter:${keycloak.version}:z

Re: wtp ear deployment

i fixed the first error.  i had put unzip:org.keycloak:keycloak-tomcat8-adapter:${keycloak.version}:zip which should have been unzip:org.keycloak:keycloak-tomcat8-adapter-dist:${keycloak.version}:zip yes my project structure is the same as your outline now it seems there is a problem with

Re: wtp ear deployment

yes my application.xml looks the same. it is auto generated by maven On 12/12/2018 13:48, Luis Rodríguez Fernández wrote: Hello there, That .ear structure worked for me in the past. But I can not tell you at 100% if it was because everything was loaded in the same classloader or just "classload

Re: wtp ear deployment

Hello there, That .ear structure worked for me in the past. But I can not tell you at 100% if it was because everything was loaded in the same classloader or just "classloader-lottery". Regarding this tomee doc [1] I would say that yes. My ear/META-INF/application.xml looks like: my-app-ear

Re: wtp ear deployment

Is the structure? EAR | -- lib/common.jar | -- webapp1.war | -- webapp2.war The short answer is I'd have to check. If you have a super simple app I can put on a server and debug, I can definitely help. I'd expect the structure above to work, although I'd probably have to check specs and do some d

Re: wtp ear deployment

when deploying an EAR do the jar files get run in a common classloader? (i.e. shared between all the WARs but only loaded once) when deploying the full thing it stalls on the below error.  whereas it works fine if the wars are all packaged and deployed independently with their own libs 12-De

Re: wtp ear deployment

Let us know how you get on with the Maven plugin. If that doesn't work, resolving any issues there would be amazing. The WTP code is here: https://svn.apache.org/repos/asf/tomee/openejb-eclipse-plugin/trunk/plugins/org.apache.openejb.wtp.server/ - it is super old, but I'd love an excuse to revive i

Re: wtp ear deployment

i am trying to get the EAR running using tomee-maven-plugin first so if i see some success with that i will come back to you.  out of interest is the extension available to look at somewhere? On 12/12/2018 11:19, Jonathan Gallimore wrote: Are you trying to do it directly in Eclipse? We do have

Re: wtp ear deployment

Are you trying to do it directly in Eclipse? We do have an extension to WTP that does enable that, but it hasn't been updated for a while. I'd be happy to try and contribute that to Eclipse itself if that's what you're looking for. Jon On Wed, Dec 12, 2018 at 10:15 AM Matthew Broadhead wrote: >

wtp ear deployment

i created a maven sub module of type ear and added my jar and war files successfully using https://maven.apache.org/plugins/maven-ear-plugin/examples/skinny-wars.html and https://maven.apache.org/plugins/maven-ear-plugin/examples/eclipse-and-maven-integration.html. but i cannot seem to deploy

Re: EAR deployment

John, Thanks for the update -- I appreciate you looking into this. Ross From: "Jonathan Gallimore" To: users@tomee.apache.org, Date: 08/20/2018 05:53 AM Subject: Re: EAR deployment So I can explain a bit about what's going on here - everything goes ok wi

Re: EAR deployment

>> grant { >> permission java.security.AllPermission; >> }; >> >> Thanks! >> Ross >> >> >> >> From: "Jonathan Gallimore" >> To: users@tomee.apache.org, >> Date: 08/10/2018 12:54 PM >> Subject:Re

Re: EAR deployment

users@tomee.apache.org, > Date: 08/10/2018 12:54 PM > Subject:Re: EAR deployment > > > > It didn't, sorry. I still want to work on it and should have time next > week. Are you able to share your security manager policy to help me debug > it through? > >

Re: EAR deployment

Security policy is very simple right now: grant { permission java.security.AllPermission; }; Thanks! Ross From: "Jonathan Gallimore" To: users@tomee.apache.org, Date: 08/10/2018 12:54 PM Subject: Re: EAR deployment It didn't, sorry. I still want to

Re: EAR deployment

It didn't, sorry. I still want to work on it and should have time next week. Are you able to share your security manager policy to help me debug it through? Jon On Fri, 10 Aug 2018, 15:23 ross.cohen, wrote: > Any chance this got fixed in 7.0.5? My hopes aren't too high, and I > already > have

Re: EAR deployment

Any chance this got fixed in 7.0.5? My hopes aren't too high, and I already have an ugly work-around, but still ... Ross -- Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Users-f979441.html

Re: EAR deployment

ws how long it will be before I can make the time to do these > > things. > > > > But this raises a question: am I really the last person still deploying > > EARs?! Really??? > > > > Thanks for your prompt help -- you guys are amazing! > > Ross >

Re: EAR deployment

zing! > Ross > > > > > > From: "Romain Manni-Bucau" > To: users@tomee.apache.org, > Date: 06/28/2018 04:03 PM > Subject:Re: EAR deployment > > > > I see > > Then it is just a bug and we miss a wrapping to be SM compliant in th

Re: EAR deployment

uys are amazing! Ross From: "Romain Manni-Bucau" To: users@tomee.apache.org, Date: 06/28/2018 04:03 PM Subject: Re: EAR deployment I see Then it is just a bug and we miss a wrapping to be SM compliant in that part of the code. Do you want to submit a PR to fix it? L

Re: EAR deployment

t : > > > So: > > > > 1. With the security manager disabled, the ear deploys fine, ejb's > > instantitiate, initialize, etc -- no errors at all! > > > > 2. I connected to the running jvm with jmx, and poked around for a > while, > > but could not find

Re: EAR deployment

" -Xmx2048m Thanks, Ross From: "Romain Manni-Bucau" To: users@tomee.apache.org, Date: 06/28/2018 11:20 AM Subject:Re: EAR deployment I think you can check it in the JVM info in system properties (VM Summary) Romain Manni-Bucau @rmannibucau < https://milton-we

Re: EAR deployment

; From: "Romain Manni-Bucau" > To: users@tomee.apache.org, > Date: 06/27/2018 04:54 PM > Subject:Re: EAR deployment > > > > Hi > > can you confirm it works without the security manager enabled? > > Also can you check connecting on the

Re: EAR deployment

nt as to where this info is? Thanks, Ross From: "Romain Manni-Bucau" To: users@tomee.apache.org, Date: 06/27/2018 04:54 PM Subject: Re: EAR deployment Hi can you confirm it works without the security manager enabled? Also can you check connecting on the JVM throu

Re: EAR deployment

. 27 juin 2018 à 19:12, a écrit : > I'm running 7.0.4. I have been deploying to webapps ( dir="apps" /> remains commented). > > Ross > > > > From: "Jonathan Gallimore" > To: users@tomee.apache.org, > Date: 06/27/2018 12:22 PM > S

Re: EAR deployment

I'm running 7.0.4. I have been deploying to webapps ( remains commented). Ross From: "Jonathan Gallimore" To: users@tomee.apache.org, Date: 06/27/2018 12:22 PM Subject: Re: EAR deployment Hi What version of TomEE are you running? Are you deploying your E

Re: EAR deployment

Hi What version of TomEE are you running? Are you deploying your EAR from webapps, or from apps with added in tomee.xml? Regards Jon On Wed, Jun 27, 2018 at 5:15 PM, wrote: > I seem unable to deploy EARs.I have set the catalina.policy to: > grant { > permission java.security.All

EAR deployment

I seem unable to deploy EARs.I have set the catalina.policy to: grant { permission java.security.AllPermission; }; I have set the work directory to "work" (and at deploy see the exploded EAR there). Also I have set deployOnStartup to false, autoDeploy to true, and unpackWARs to tru

Re: DeployEJB for EAR Deployment

In conf/. It is a plain list of apps. Le 13 août 2016 12:37, "romi ton" a écrit : > Thanks. > > Where TomEE save this file? And how TomEE understands that it will have app > to deploy at startup? Is TomEE writes to any configuration file the > location path of this app? > > Thanks. > Ron. > > On

Re: DeployEJB for EAR Deployment

Thanks. Where TomEE save this file? And how TomEE understands that it will have app to deploy at startup? Is TomEE writes to any configuration file the location path of this app? Thanks. Ron. On Sat, Aug 13, 2016 at 8:07 AM, Romain Manni-Bucau wrote: > Hi > > openejb.deployer.save-deployments=

Re: DeployEJB for EAR Deployment

Hi openejb.deployer.save-deployments=true in conf/system.properties Le 13 août 2016 00:44, "romi ton" a écrit : > Hi all > > When we use DeployEJB to deploy some ear to TomEE, after restart this > deployment is not valid anymore. How to persist this deployment even in > server restarts? > > Bes

DeployEJB for EAR Deployment

Hi all When we use DeployEJB to deploy some ear to TomEE, after restart this deployment is not valid anymore. How to persist this deployment even in server restarts? Best Ron.

Re: ear deployment doesn't work for tomee 1.5.2 but works for 1.5.1

will be the solution for every tomee release, right? > > > > -- > View this message in context: > http://openejb.979440.n4.nabble.com/ear-deployment-doesn-t-work-for-tomee-1-5-2-but-works-for-1-5-1-tp4662612p4662620.html > Sent from the OpenEJB User mailing list archive at Nabble.com. >

Re: ear deployment doesn't work for tomee 1.5.2 but works for 1.5.1

So add to conf\tomee.xml and copy my ear to apps\ will be the solution for every tomee release, right? -- View this message in context: http://openejb.979440.n4.nabble.com/ear-deployment-doesn-t-work-for-tomee-1-5-2-but-works-for-1-5-1-tp4662612p4662620.html Sent from the OpenEJB User mailing

Re: ear deployment doesn't work for tomee 1.5.2 but works for 1.5.1

Hi, Basically use the same tomee.xml (user conf) and all should be fine. We removed the deployments directive because we valid it now (before we were swallowing errors) Le 2 mai 2013 05:26, "nj00yy_1" <784396...@qq.com> a écrit : > What I want is an ear deployment solution wh

Re: ear deployment doesn't work for tomee 1.5.2 but works for 1.5.1

What I want is an ear deployment solution which works for every Tomee release, such as: tomee1.0.0, tomee1.5.2, and any future release. Thanks. -- View this message in context: http://openejb.979440.n4.nabble.com/ear-deployment-doesn-t-work-for-tomee-1-5-2-but-works-for-1-5-1

Re: ear deployment doesn't work for tomee 1.5.2 but works for 1.5.1

ear on top of tomee 1.5.2? -- View this message in context: http://openejb.979440.n4.nabble.com/ear-deployment-doesn-t-work-for-tomee-1-5-2-but-works-for-1-5-1-tp4662612p4662614.html Sent from the OpenEJB User mailing list archive at Nabble.com.

ear deployment doesn't work for tomee 1.5.2 but works for 1.5.1

.979440.n4.nabble.com/ear-deployment-doesn-t-work-for-tomee-1-5-2-but-works-for-1-5-1-tp4662612.html Sent from the OpenEJB User mailing list archive at Nabble.com.