[GitHub] [geronimo-xbean] rmannibucau merged pull request #24: [XBEAN-333]upgrade to ASM 9.2 so that xbean can work with JDK18-EA

rmannibucau merged pull request #24: URL: https://github.com/apache/geronimo-xbean/pull/24 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-uns

[jira] [Commented] (GERONIMO-6813) [mvn-plugin/Knights] Will not work with jakarta Namespace

We can do the same as for most ASF project and just have a shade of the extension with jakarta classifier since extensions are just maven dependencies at the end . > [mvn-plugin/Knights] Will not work with jakarta Na

[jira] [Created] (GERONIMO-6813) [mvn-plugin/Knights] Will not work with jakarta Namespace

Benjamin Marwell created GERONIMO-6813: -- Summary: [mvn-plugin/Knights] Will not work with jakarta Namespace Key: GERONIMO-6813 URL: https://issues.apache.org/jira/browse/GERONIMO-6813 Project

[jira] [Updated] (GERONIMO-6757) Changes to make geronimo-jwt-auth work with Aries CDI

> Changes to make geronimo-jwt-auth work with Aries CDI > - > > Key: GERONIMO-6757 > URL: https://issues.apache.org/jira/browse/GERONIMO-6757 > Project: Geronimo > Issue Type

[jira] [Created] (GERONIMO-6789) Simple JCache extension does not work well with cdi (cdi helper not found)

Romain Manni-Bucau created GERONIMO-6789: Summary: Simple JCache extension does not work well with cdi (cdi helper not found) Key: GERONIMO-6789 URL: https://issues.apache.org/jira/browse/GERONIMO-6789

[jira] [Resolved] (GERONIMO-6789) Simple JCache extension does not work well with cdi (cdi helper not found)

[ https://issues.apache.org/jira/browse/GERONIMO-6789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau resolved GERONIMO-6789. -- Resolution: Fixed > Simple JCache extension does not work well with

[jira] [Resolved] (GERONIMO-6761) Enable Geronimo Simple JCache to work with OSGi

[ https://issues.apache.org/jira/browse/GERONIMO-6761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau resolved GERONIMO-6761. -- Resolution: Fixed > Enable Geronimo Simple JCache to work with O

[jira] [Created] (GERONIMO-6761) Enable Geronimo Simple JCache to work with OSGi

Romain Manni-Bucau created GERONIMO-6761: Summary: Enable Geronimo Simple JCache to work with OSGi Key: GERONIMO-6761 URL: https://issues.apache.org/jira/browse/GERONIMO-6761 Project: Geronimo

[jira] [Created] (GERONIMO-6757) Changes to make geronimo-jwt-auth work with Aries CDI

Raymond Augé created GERONIMO-6757: -- Summary: Changes to make geronimo-jwt-auth work with Aries CDI Key: GERONIMO-6757 URL: https://issues.apache.org/jira/browse/GERONIMO-6757 Project: Geronimo

[jira] [Resolved] (GERONIMO-6745) javax.json.bind.JsonbConfig#accumulate does not work

[ https://issues.apache.org/jira/browse/GERONIMO-6745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau resolved GERONIMO-6745. -- Resolution: Fixed > javax.json.bind.JsonbConfig#accumulate does not w

[jira] [Created] (GERONIMO-6745) javax.json.bind.JsonbConfig#accumulate does not work

Romain Manni-Bucau created GERONIMO-6745: Summary: javax.json.bind.JsonbConfig#accumulate does not work Key: GERONIMO-6745 URL: https://issues.apache.org/jira/browse/GERONIMO-6745 Project

[jira] [Resolved] (GERONIMO-6702) geronimo.opentracing.filter.skippedTracing.urls does not work

oes not work > - > > Key: GERONIMO-6702 > URL: https://issues.apache.org/jira/browse/GERONIMO-6702 > Project: Geronimo > Issue Type: Bug > Security Leve

[jira] [Created] (GERONIMO-6702) geronimo.opentracing.filter.skippedTracing.urls does not work

Romain Manni-Bucau created GERONIMO-6702: Summary: geronimo.opentracing.filter.skippedTracing.urls does not work Key: GERONIMO-6702 URL: https://issues.apache.org/jira/browse/GERONIMO-6702

[jira] [Commented] (GERONIMO-6661) OpenAPIMojo doesn't work with @Path annotation on interface

that when you don't use mp-openapi-api (always looks weird to write it) you easily end up with not having enough info to generate the openapi.json and defaulting to dummy values is likely as bad bu t happy to find a better way if you have an idea ;). > OpenAPIMojo doesn't work with @P

[jira] [Commented] (GERONIMO-6661) OpenAPIMojo doesn't work with @Path annotation on interface

property '$ref' Schema error at paths['/sayHello/{a}'].get.responses['200'] should match exactly one schema in oneOf {noformat} > OpenAPIMojo doesn't work with @Path annotation on interface > ---

[jira] [Resolved] (GERONIMO-6661) OpenAPIMojo doesn't work with @Path annotation on interface

: OpenAPI_1.0.2 Pushed a first version, it is not 100% generic so feedback is welcomed, i will release johnzon tomorrow (vote) and then this one (depending on the result of johnzon's vote result) > OpenAPIMojo doesn't work with @Path annotation

[jira] [Commented] (GERONIMO-6661) OpenAPIMojo doesn't work with @Path annotation on interface

will work on it to be able to release it tomorrow > OpenAPIMojo doesn't work with @Path annotation on interface > --- > > Key: GERONIMO-6661 > URL: https://issues.apache.org/j

[jira] [Commented] (GERONIMO-6661) OpenAPIMojo doesn't work with @Path annotation on interface

d to continue around the christmas holidays... > OpenAPIMojo doesn't work with @Path annotation on interface > --- > > Key: GERONIMO-6661 > URL: https://issues.apache.org/j

[jira] [Commented] (GERONIMO-6661) OpenAPIMojo doesn't work with @Path annotation on interface

t an impl has an interface as contract but current reflection impl ignores @path i think if not on the parsed class. Do you want to try to submit a patch or girhub pull request for that? Sounds feasible (just requires a test somehow to prevent regressions) > OpenAPIMojo doesn't wor

[jira] [Commented] (GERONIMO-6661) OpenAPIMojo doesn't work with @Path annotation on interface

for the quick response. There is a second class in the sample that uses the same interface: [https://github.com/apache/cxf/blob/master/distribution/src/main/release/samples/jax_rs/spring_boot/src/main/java/sample/rs/service/hello2/HelloServiceImpl2.java] So just providing the interface will not

[jira] [Commented] (GERONIMO-6661) OpenAPIMojo doesn't work with @Path annotation on interface

s is kind of expected since you should list the interface rather than the impl, no? There is no discovery yet in the mojo and it expects the model to be provided as such. > OpenAPIMojo doesn't work with @Path annotation

[jira] [Created] (GERONIMO-6661) OpenAPIMojo doesn't work with @Path annotation on interface

Dennis Kieselhorst created GERONIMO-6661: Summary: OpenAPIMojo doesn't work with @Path annotation on interface Key: GERONIMO-6661 URL: https://issues.apache.org/jira/browse/GERONIMO

Re: Should primitive types work in config?

Hmm right, pretty sure I had an issue with primitives at some point but can be specific to a version or project. Let handle it anyway here and thanks for the memory refresh ;). Romain Manni-Bucau @rmannibucau | Blog | Old B

Re: Should primitive types work in config?

You can inject to primitive fields in DS config (that's how I found this problem). John On Sun, Jul 30, 2017 at 6:10 AM Romain Manni-Bucau wrote: > Interesting, why was it rejected in DeltaSpike config then? Do you recall? > > Now on config itself if cdi does +1 to support it. We should probabl

Re: Should primitive types work in config?

Interesting, why was it rejected in DeltaSpike config then? Do you recall? Now on config itself if cdi does +1 to support it. We should probably align on the spec defaults, ie null would resolve to 0 for an int for instance. Romain Manni-Bucau @rmannibucau | Bl

Re: Should primitive types work in config?

http://docs.jboss.org/cdi/spec/2.0/cdi-spec.html#primitive_types_and_null_values "For the purposes of typesafe resolution and dependency injection, primitive types and their corresponding wrapper types in the package java.lang are considered identical and assignable. If necessary, the container

Re: Should primitive types work in config?

Hmm, cdi does? was pretty sure injections had Object constraint. Do I get it wrong? Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github | LinkedIn <

Re: Should primitive types work in config?

CDI supports primitives. So I'm not quite sure what's the point? LieGrue, strub > Am 30.07.2017 um 09:26 schrieb Romain Manni-Bucau : > > > Alternative would be to make cdi support primitive, agree there is no blocker > at all to do it but then for libs i think we need to limit to the most >

Re: Should primitive types work in config?

@John: it is not a technical issue, it is a model issue: public class MyConfig { @Inject @ConfigProperty(name = "...") int port; } will work in standalone, spring, ... but if you have a cdi extension bridging the lib it will just fail - that is why proxy model is more portable for

Re: Should primitive types work in config?

t;> Oh I see. Now I get what you mean. >> Yes, we should just register the same converters for their primitive >> counterparts as well. >> >> LieGrue, >> strub >> >> > Am 29.07.2017 um 13:12 schrieb John D. Ament : >> > >> > Hey guys &

Re: Should primitive types work in config?

gt; > Hey guys > > > > I raised a spec level issue on MP Config because primitives don't work > quite right in Geronimo Config and when I looked at the spec, it didn't say > they should. > > > > Basically, primitives aren't used in the TCK, and the foll

Re: Should primitive types work in config?

e converters for their primitive > counterparts as well. > > LieGrue, > strub > > > Am 29.07.2017 um 13:12 schrieb John D. Ament : > > > > Hey guys > > > > I raised a spec level issue on MP Config because primitives don't work > quite right in Geron

Re: Should primitive types work in config?

Oh I see. Now I get what you mean. Yes, we should just register the same converters for their primitive counterparts as well. LieGrue, strub > Am 29.07.2017 um 13:12 schrieb John D. Ament : > > Hey guys > > I raised a spec level issue on MP Config because primitives don't

Should primitive types work in config?

Hey guys I raised a spec level issue on MP Config because primitives don't work quite right in Geronimo Config and when I looked at the spec, it didn't say they should. Basically, primitives aren't used in the TCK, and the follow behaviors are noticed: int port = config.get

Re: Yoko work

(Sorry, my reply was “stuck” in the draft folder) Many thanks! It’s great to see external products giving back to their OSS siblings. Hope to see more great work! Regards, Alan > On Feb 28, 2017, at 3:25 PM, David Jencks wrote: > > I’ve merged the commits from Joe Chacko, Neil

Yoko work

I’ve merged the commits from Joe Chacko, Neil Richards and myself into yoko master and closed the related jira issues. I think there may have been some further development at IBM after I left, I will try to see if we can get that added in, perhaps with more help from Joe/Neil. thanks david jen

Quick debugging of JSP's doesn't work

perimenting with the "modificationTestInterval" setting in the Catalina web.xml file as the help text indicates this value is related to the "development" setting in the same file. Is there someone here, who has successfully made this work? Thanks, -- View this message in c

[jira] [Commented] (GERONIMO-6423) Programmatically registering JASPIC auth module doesn't work correctly

here. This is still a rather serious impediment for using JASPIC on Geronimo. > Programmatically registering JASPIC auth module doesn't work correctly > -- > > Key: GERONIMO-6423 >

[jira] [Updated] (GERONIMO-6043) module init order doesn't always work due to gbean dependencies

n't always work due to gbean dependencies > --- > > Key: GERONIMO-6043 > URL: https://issues.apache.org/jira/browse/GERONIMO-6043 > Project: Geronimo > Issue Type:

[jira] [Updated] (GERONIMO-5046) Remove need for system property true to get car-maven-plugin to work

tem property true > to get car-maven-plugin to work > - > > Key: GERONIMO-5046 > URL: https://issues.apache.org/jira/browse/GERONIMO-5046 >

[jira] [Updated] (GERONIMO-6247) Put the stax and jaxb api bundles in endorsed and figure out what the karaf-activator idea is so they can work.

api bundles in endorsed and figure out what the > karaf-activator idea is so they can work. > --- > > Key: GERONIMO-6247 > URL: https://issues.apac

[jira] [Resolved] (GERONIMO-6466) Remote address filter feature doesn't work when add it into

ote address filter feature doesn't work when add it into > - > > Key: GERONIMO-6466 > URL: https://issues.apache.org/jira/browse/GERONIMO-6466 > Project: Geronim

[jira] [Commented] (GERONIMO-6466) Remote address filter feature doesn't work when add it into

h at r1481687, thanks xiezhi for this patch! > Remote address filter feature doesn't work when add it into > - > > Key: GERONIMO-6466 > URL: https://issue

[jira] [Updated] (GERONIMO-6466) Remote address filter feature doesn't work when add it into

. > Remote address filter feature doesn't work when add it into > - > > Key: GERONIMO-6466 > URL: https://issues.apache.org/jira/browse/GERONIMO-6466 >

[jira] [Created] (GERONIMO-6466) Remote address filter feature doesn't work when add it into

xiezhi created GERONIMO-6466: Summary: Remote address filter feature doesn't work when add it into Key: GERONIMO-6466 URL: https://issues.apache.org/jira/browse/GERONIMO-6466 Project: Ger

[jira] [Resolved] (GERONIMODEVTOOLS-809) In-use port detection does not work sometimes

port checking seems to be working as expected. > In-use port detection does not work sometimes > - > > Key: GERONIMODEVTOOLS-809 > URL: > https://issues.apache.org/jira/browse/GE

[jira] [Commented] (GERONIMODEVTOOLS-809) In-use port detection does not work sometimes

tted improvements in revision 1461837. Besides checking 0.0.0.0 (as done before), GEP will also now lookup and check the address of the server as configured in Eclipse (getServer().getHost()). > In-use port detection does not work so

[jira] [Created] (GERONIMODEVTOOLS-809) In-use port detection does not work sometimes

Jarek Gawor created GERONIMODEVTOOLS-809: Summary: In-use port detection does not work sometimes Key: GERONIMODEVTOOLS-809 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-809

[jira] [Resolved] (GERONIMO-6389) Obscuring Passwords Feature couldn't work

branch at rev.1459106 and trunk at rev.1459107 Thanks, Xie Zhi ! > Obscuring Passwords Feature couldn't work > - > > Key: GERONIMO-6389 > URL: https://issues.apache.org/jira/

[jira] [Assigned] (GERONIMO-6389) Obscuring Passwords Feature couldn't work

[ https://issues.apache.org/jira/browse/GERONIMO-6389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan reassigned GERONIMO-6389: -- Assignee: Ivan (was: xiezhi) > Obscuring Passwords Feature couldn

[jira] [Commented] (GERONIMO-6428) @DataSourceDefinition doesn't work correctly

more information? Or didn't I write the issue correctly? If the latter is true, just let me know what's missing and I'll gladly provide more info. > @DataSourceDefinition doesn't work correctly > > >

[jira] [Commented] (GERONIMO-6428) @DataSourceDefinition doesn't work correctly

the Geronimo team can react on this ;) > @DataSourceDefinition doesn't work correctly > > > Key: GERONIMO-6428 > URL: https://issues.apache.org/jira/browse/GERONIMO-6428 >

[jira] [Comment Edited] (GERONIMO-6428) @DataSourceDefinition doesn't work correctly

obal/MyApp/myDS org.h2.jdbcx.JdbcDataSource jdbc:h2:mem:test sa sa URLjdbc:h2:mem:test true TRANSACTION_READ_COMMITTED 2 10 5 0 {code} > @DataSourceDefinition doesn't wo

[jira] [Commented] (GERONIMO-6428) @DataSourceDefinition doesn't work correctly

2 10 5 0 {code} > @DataSourceDefinition doesn't work correctly > > > Key: GERONIMO-6428 > URL: https://issues.apache.org/jira/browse/GERONIMO-6428 >

[jira] [Commented] (GERONIMO-6428) @DataSourceDefinition doesn't work correctly

his is logged later as a warning, but the warning doesn't contain the full cause. > @DataSourceDefinition doesn't work correctly > > > Key: GERONIMO-6428 > URL: ht

[jira] [Created] (GERONIMO-6428) @DataSourceDefinition doesn't work correctly

Henk de Boer created GERONIMO-6428: -- Summary: @DataSourceDefinition doesn't work correctly Key: GERONIMO-6428 URL: https://issues.apache.org/jira/browse/GERONIMO-6428 Project: Ger

[jira] [Created] (GERONIMO-6423) Programmatically registering JASPIC auth module doesn't work correctly

Arjan Tijms created GERONIMO-6423: - Summary: Programmatically registering JASPIC auth module doesn't work correctly Key: GERONIMO-6423 URL: https://issues.apache.org/jira/browse/GERONIMO-6423 Pr

[jira] [Updated] (GERONIMO-5046) Remove need for system property true to get car-maven-plugin to work

tem property true > to get car-maven-plugin to work > - > > Key: GERONIMO-5046 > URL: https://issues.apache.org/jira/browse/GERONIMO-5046 >

[jira] [Updated] (GERONIMO-6043) module init order doesn't always work due to gbean dependencies

n't always work due to gbean dependencies > --- > > Key: GERONIMO-6043 > URL: https://issues.apache.org/jira/browse/GERONIMO-6043 > Project: Geronimo > Issue Type:

[jira] [Updated] (GERONIMO-6247) Put the stax and jaxb api bundles in endorsed and figure out what the karaf-activator idea is so they can work.

api bundles in endorsed and figure out what the > karaf-activator idea is so they can work. > --- > > Key: GERONIMO-6247 > URL: https://issues.apac

[jira] [Resolved] (GERONIMO-6388) geronimo debug does not work

[ https://issues.apache.org/jira/browse/GERONIMO-6388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-6388. --- Resolution: Fixed Fix Version/s: 3.0.1 > geronimo debug does not w

[jira] [Updated] (GERONIMO-6389) Obscuring Passwords Feature couldn't work

> Obscuring Passwords Feature couldn't work > - > > Key: GERONIMO-6389 > URL: https://issues.apache.org/jira/browse/GERONIMO-6389 > Project: Geronimo > Issue Type: Bug > Security

[jira] [Commented] (GERONIMO-6389) Obscuring Passwords Feature couldn't work

nimo-6310. And jira 6310 fixed on geronimo 3.0-beta. > Obscuring Passwords Feature couldn't work > - > > Key: GERONIMO-6389 > URL: https://issues.apache.org/jira/browse/GERONIMO-6389 >

[jira] [Assigned] (GERONIMO-6389) Obscuring Passwords Feature couldn't work

[ https://issues.apache.org/jira/browse/GERONIMO-6389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiezhi reassigned GERONIMO-6389: Assignee: xiezhi > Obscuring Passwords Feature couldn

[jira] [Created] (GERONIMO-6389) Obscuring Passwords Feature couldn't work

xiezhi created GERONIMO-6389: Summary: Obscuring Passwords Feature couldn't work Key: GERONIMO-6389 URL: https://issues.apache.org/jira/browse/GERONIMO-6389 Project: Geronimo Issue Type

[jira] [Commented] (GERONIMO-6388) geronimo debug does not work

fixed the debug command by 1) ensuring that the transformer.jar is on the classpath (I first tried passing -J-javaagent but that did not work for some reason) and 2) ensuring that karaf.startLocalConsole=false in debug mode. I also simplified the start command on Windows which was passing all the

[jira] [Updated] (GERONIMO-6388) geronimo debug does not work

debug" saying that -javaagent argument is unrecognized. > geronimo debug does not work > > > Key: GERONIMO-6388 > URL: https://issues.apache.org/jira/browse/GERONIMO-6388 > Project: Geronimo >

[jira] [Created] (GERONIMO-6388) geronimo debug does not work

Jarek Gawor created GERONIMO-6388: - Summary: geronimo debug does not work Key: GERONIMO-6388 URL: https://issues.apache.org/jira/browse/GERONIMO-6388 Project: Geronimo Issue Type: Bug

[jira] [Created] (GERONIMO-6387) @EJB doesn't work in an EJB annotated with @Entity

Anthony Insolia created GERONIMO-6387: - Summary: @EJB doesn't work in an EJB annotated with @Entity Key: GERONIMO-6387 URL: https://issues.apache.org/jira/browse/GERONIMO-6387 Project: Ger

Re: OSGi Composite Bundle didn't work on Geronimo v3.0

Geronimo does not support compsite bundles, maybe you could try to use eba, which is another kind of programming model in OSGi runtime. 2012/8/24 정재부 > Dear, Apache team. > > I’m JB, osgi developer in korea. > > Once I wanted to make a composite bundle project with Geronimo, everything >

OSGi Composite Bundle didn't work on Geronimo v3.0

Dear, Apache team. I’m JB, osgi developer in korea. Once I wanted to make a composite bundle project with Geronimo, everything was OK but I got one problem. When I made New Project > OSGi composite bundle project and then I deployed it on Geronimo V3.0,( I already configured GEP and OSGi develop

[jira] [Updated] (GERONIMO-5737) setJavaEnv.bat does not work under TCC/LE command shell for Windows

Version/s: 2.1.9 3.0.1 2.2.2 Assignee: Shawn Jiang > setJavaEnv.bat does not work under TCC/LE command shell for Windows > --- > > Key: G

[jira] [Resolved] (GERONIMO-5737) setJavaEnv.bat does not work under TCC/LE command shell for Windows

. > setJavaEnv.bat does not work under TCC/LE command shell for Windows > --- > > Key: GERONIMO-5737 > URL: https://issues.apache.org/jira/browse/GERONIMO-5737 > Project: Geronimo >

[jira] [Updated] (GERONIMO-6218) Directory Listings function doesn't work well for web application

[ https://issues.apache.org/jira/browse/GERONIMO-6218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn Jiang updated GERONIMO-6218: -- Patch Info: Patch Available > Directory Listings function doesn't work well

[jira] [Commented] (GERONIMODEVTOOLS-797) Latest beta version does not work with Eclipse Juno because of invalid openejb-jar-2.2.xsd file

ssue has been resolved in GERONIMODEVTOOLS-799, thank you for your patch. > Latest beta version does not work with Eclipse Juno because of invalid > openejb-jar-2.

[jira] [Resolved] (GERONIMODEVTOOLS-797) Latest beta version does not work with Eclipse Juno because of invalid openejb-jar-2.2.xsd file

oes not work with Eclipse Juno because of invalid > openejb-jar-2.2.xsd file > --- > > Key: GERONIMODEVTOOLS-797 > URL: > https://issues.apache.org/jira/br

[jira] [Commented] (GERONIMODEVTOOLS-797) Latest beta version does not work with Eclipse Juno because of invalid openejb-jar-2.2.xsd file

as mentioned above > Latest beta version does not work with Eclipse Juno because of invalid > openejb-jar-2.2.xsd file > --- > > Key: GERONIMODEVTOOLS-797 > U

[jira] [Commented] (GERONIMODEVTOOLS-797) Latest beta version does not work with Eclipse Juno because of invalid openejb-jar-2.2.xsd file

ttps://issues.apache.org/jira/secure/attachment/12485673/Geronimo-6050.patch > Latest beta version does not work with Eclipse Juno because of invalid > openejb-jar-2.

[jira] [Updated] (GERONIMODEVTOOLS-797) Latest beta version does not work with Eclipse Juno because of invalid openejb-jar-2.2.xsd file

[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Johannes Weberhofer updated GERONIMODEVTOOLS-797: - Summary: Latest beta version does not work with Eclipse

[jira] [Updated] (GERONIMODEVTOOLS-797) Latest beta version does not work with Eclipse Juno because of invalid openejb-jaar-2.2.xsd file

est beta version does not work with Eclipse Juno because of invalid > openejb-jaar-2.2.xsd file > > > Key: GERONIMODEVTOOLS-797 > URL: > https://issues.a

[jira] [Created] (GERONIMODEVTOOLS-797) Latest beta version does not work with Eclipse Juno because of invalid openejb-jaar-2.2.xsd file

Johannes Weberhofer created GERONIMODEVTOOLS-797: Summary: Latest beta version does not work with Eclipse Juno because of invalid openejb-jaar-2.2.xsd file Key: GERONIMODEVTOOLS-797 URL: https

[jira] [Created] (GERONIMO-6354) web.xml in geronimo server does not work

Saphen Qiu created GERONIMO-6354: Summary: web.xml in geronimo server does not work Key: GERONIMO-6354 URL: https://issues.apache.org/jira/browse/GERONIMO-6354 Project: Geronimo Issue Type

[jira] [Resolved] (GERONIMO-4972) Nested child configurations from ears don't work well with osgi

one bundle. > Nested child configurations from ears don't work well with osgi > --- > > Key: GERONIMO-4972 > URL: https://issues.apache.org/jira/browse/GERONIMO-4972 > P

[jira] [Resolved] (GERONIMO-5480) Web security does not work on Equinox

[ https://issues.apache.org/jira/browse/GERONIMO-5480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks resolved GERONIMO-5480. Resolution: Fixed Jarek's fix seems to work. > Web security

[jira] [Updated] (GERONIMO-6251) Fix geronimo-maven-plugin to work with more karaf-based server

: (was: 3.0) 4.0 > Fix geronimo-maven-plugin to work with more karaf-based server > -- > > Key: GERONIMO-6251 > URL: https://issues.apache.org/jira/brows

[jira] [Resolved] (GERONIMO-5280) geronimo-jaspi jaspic provider won't work well under osgi

> geronimo-jaspi jaspic provider won't work well under osgi > - > > Key: GERONIMO-5280 > URL: https://issues.apache.org/jira/browse/GERONIMO-5280 > Project: Geronimo >

[jira] [Commented] (GERONIMO-6218) Directory Listings function doesn't work well for web application

this issue is fixed in the latest 2.1.x and 2.2.x build? If it is still there, please consider raise it to Tomcat community for a resolution. thank you! > Directory Listings function doesn't work well for web

[jira] [Commented] (GERONIMO-6218) Directory Listings function doesn't work well for web application

s in advance! > Directory Listings function doesn't work well for web application > --- > > Key: GERONIMO-6218 > URL: https://issues.apache.org/jira/browse/GERONIMO-62

[jira] [Assigned] (GERONIMO-6218) Directory Listings function doesn't work well for web application

[ https://issues.apache.org/jira/browse/GERONIMO-6218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tina Li reassigned GERONIMO-6218: - Assignee: Tina Li > Directory Listings function doesn't work well for web app

[jira] [Resolved] (GERONIMO-6233) --offline option does not work when server is started

is fixed by Jarek, thanks! > --offline option does not work when server is started > - > > Key: GERONIMO-6233 > URL: https://issues.apache.org/jira/browse/GERONIMO-6233 >

[jira] [Commented] (GERONIMO-6043) module init order doesn't always work due to gbean dependencies

need to re-evaluate the issue of this jira reported, any new comment? > module init order doesn't always work due to gbean dependencies > --- > > Key: GERONIMO-6043 >

[jira] [Commented] (GERONIMO-6233) --offline option does not work when server is started

sion 1331869 that make offline option work for me. Please verify my fix. The key is to ensure that rmi-naming dependency does not actually start with offline deployer. > --offline option does not work when server is

[jira] [Closed] (GERONIMO-6254) Shared library does not work in the deployment process

[ https://issues.apache.org/jira/browse/GERONIMO-6254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan closed GERONIMO-6254. -- > Shared library does not work in the deployment proc

[jira] [Resolved] (GERONIMO-6254) Shared library does not work in the deployment process

[ https://issues.apache.org/jira/browse/GERONIMO-6254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan resolved GERONIMO-6254. Resolution: Fixed > Shared library does not work in the deployment proc

[jira] [Commented] (GERONIMO-6233) --offline option does not work when server is started

One question here, can we not change g-m-p bahavior on failIfNotStarted? so that keep consistent as before. > --offline option does not work when server is started > - > > Key: GERONIMO-6233 >

[jira] [Commented] (GERONIMO-6254) Shared library does not work in the deployment process

jira? > Shared library does not work in the deployment process > -- > > Key: GERONIMO-6254 > URL: https://issues.apache.org/jira/browse/GERONIMO-6254 > Project: Geronimo >

[jira] [Resolved] (GERONIMO-5051) Taglib discovery does not work

[ https://issues.apache.org/jira/browse/GERONIMO-5051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia resolved GERONIMO-5051. --- Resolution: Fixed > Taglib discovery does not w

[jira] [Reopened] (GERONIMO-6233) --offline option does not work when server is started

[ https://issues.apache.org/jira/browse/GERONIMO-6233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saphen Qiu reopened GERONIMO-6233: -- > --offline option does not work when server is star

[jira] [Updated] (GERONIMODEVTOOLS-788) The hot deploy of jsp and other static resource files do not work even under the development mode

les do not work even under > the development mode > - > > Key: GERONIMODEVTOOLS-788 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-788

[jira] [Commented] (GERONIMODEVTOOLS-788) The hot deploy of jsp and other static resource files do not work even under the development mode

sion 1295380 and 1295382 > The hot deploy of jsp and other static resource files do not work even under > the development mode > - > > Key: G

  1   2   3   4   5   6   7   8   9   10   >