[jira] [Resolved] (GERONIMO-6784) ClassCastException in javax.enterprise.util.AnnotationLiteral#hashCode
[ https://issues.apache.org/jira/browse/GERONIMO-6784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved GERONIMO-6784. - Resolution: Fixed Thank you Arne, applied and release is under vote! > ClassCastException in javax.enterprise.util.AnnotationLiteral#hashCode > -- > > Key: GERONIMO-6784 > URL: https://issues.apache.org/jira/browse/GERONIMO-6784 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: specs >Reporter: Arne Limburg >Assignee: Mark Struberg >Priority: Major > > In jcdi-spec in javax.enterprise.util.AnnotationLiteral#hashCode the type is > checked for boolean[] and then casted to long[] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GERONIMO-6784) ClassCastException in javax.enterprise.util.AnnotationLiteral#hashCode
[ https://issues.apache.org/jira/browse/GERONIMO-6784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg reassigned GERONIMO-6784: --- Assignee: Mark Struberg > ClassCastException in javax.enterprise.util.AnnotationLiteral#hashCode > -- > > Key: GERONIMO-6784 > URL: https://issues.apache.org/jira/browse/GERONIMO-6784 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: specs >Reporter: Arne Limburg >Assignee: Mark Struberg >Priority: Major > > In jcdi-spec in javax.enterprise.util.AnnotationLiteral#hashCode the type is > checked for boolean[] and then casted to long[] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GERONIMO-6726) Create jakarta.* spec APIs
[ https://issues.apache.org/jira/browse/GERONIMO-6726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16837650#comment-16837650 ] Mark Struberg commented on GERONIMO-6726: - Hi [~downdrown]! It is pretty much 100% fix that the javax.* namespace will not be touched and JakartaEE will have to move. I guess you've seen my blog post, right? There will be tools to support downstream users. I guess that NetBeans, Eclipse and Idea will have this on board. I expect a timeframe of about 9 months before you'll see the first full servers and eco system being migrated. I think migrating a user project will be updating dependencies + an hour of work. Given all deps are available for jakarta.* then it should be pretty much straight forward. > Create jakarta.* spec APIs > -- > > Key: GERONIMO-6726 > URL: https://issues.apache.org/jira/browse/GERONIMO-6726 > Project: Geronimo > Issue Type: Task > Security Level: public(Regular issues) > Components: specs >Reporter: Mark Struberg >Priority: Major > > Oracle does not allow to evolve the former JavaEE specs under the javax.* > package name as they claim to own the full 'Java' trademark. > While this may or may not be true it might be wise to not pursue a legal > battle. > Thus we will move all the specs to use the jakarta.* package names. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GERONIMO-6726) Create jakarta.* spec APIs
Mark Struberg created GERONIMO-6726: --- Summary: Create jakarta.* spec APIs Key: GERONIMO-6726 URL: https://issues.apache.org/jira/browse/GERONIMO-6726 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Components: specs Reporter: Mark Struberg Oracle does not allow to evolve the former JavaEE specs under the javax.* package name as they claim to own the full 'Java' trademark. While this may or may not be true it might be wise to not pursue a legal battle. Thus we will move all the specs to use the jakarta.* package names. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GERONIMO-6712) JsonValue Class initialisation might create a deadlock
[
https://issues.apache.org/jira/browse/GERONIMO-6712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16786526#comment-16786526
]
Mark Struberg commented on GERONIMO-6712:
-
VOTE passed, fix got released in our 1.2 version:
repo1.maven.org/maven2/org/apache/geronimo/specs/geronimo-json_1.1_spec/1.2/
> JsonValue Class initialisation might create a deadlock
> --
>
> Key: GERONIMO-6712
> URL: https://issues.apache.org/jira/browse/GERONIMO-6712
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: specs
>Reporter: Mark Struberg
>Assignee: Mark Struberg
>Priority: Major
>
> Our {{JsonValue}} class contains the following two static fields:
> {souce}
> JsonObject EMPTY_JSON_OBJECT = Json.createObjectBuilder().build();
> JsonArray EMPTY_JSON_ARRAY = Json.createArrayBuilder().build();
> {souce}
> It basically starts up a whole Json Provider just for initialising the
> JsonValue class.
> This might lead to a deadlock in the JVM during the classloading if it gets
> triggered in highly concurrent situtations.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (GERONIMO-6712) JsonValue Class initialisation might create a deadlock
[
https://issues.apache.org/jira/browse/GERONIMO-6712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16786526#comment-16786526
]
Mark Struberg edited comment on GERONIMO-6712 at 3/7/19 8:45 AM:
-
VOTE passed, fix got released in our 1.2 version:
https://repo1.maven.org/maven2/org/apache/geronimo/specs/geronimo-json_1.1_spec/1.2/
was (Author: struberg):
VOTE passed, fix got released in our 1.2 version:
repo1.maven.org/maven2/org/apache/geronimo/specs/geronimo-json_1.1_spec/1.2/
> JsonValue Class initialisation might create a deadlock
> --
>
> Key: GERONIMO-6712
> URL: https://issues.apache.org/jira/browse/GERONIMO-6712
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: specs
>Reporter: Mark Struberg
>Assignee: Mark Struberg
>Priority: Major
>
> Our {{JsonValue}} class contains the following two static fields:
> {souce}
> JsonObject EMPTY_JSON_OBJECT = Json.createObjectBuilder().build();
> JsonArray EMPTY_JSON_ARRAY = Json.createArrayBuilder().build();
> {souce}
> It basically starts up a whole Json Provider just for initialising the
> JsonValue class.
> This might lead to a deadlock in the JVM during the classloading if it gets
> triggered in highly concurrent situtations.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GERONIMO-6712) JsonValue Class initialisation might create a deadlock
[
https://issues.apache.org/jira/browse/GERONIMO-6712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg resolved GERONIMO-6712.
-
Resolution: Fixed
will get shipped with geronimo-json_1.1_spec-api-1.2.jar
> JsonValue Class initialisation might create a deadlock
> --
>
> Key: GERONIMO-6712
> URL: https://issues.apache.org/jira/browse/GERONIMO-6712
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: specs
>Reporter: Mark Struberg
>Assignee: Mark Struberg
>Priority: Major
>
> Our {{JsonValue}} class contains the following two static fields:
> {souce}
> JsonObject EMPTY_JSON_OBJECT = Json.createObjectBuilder().build();
> JsonArray EMPTY_JSON_ARRAY = Json.createArrayBuilder().build();
> {souce}
> It basically starts up a whole Json Provider just for initialising the
> JsonValue class.
> This might lead to a deadlock in the JVM during the classloading if it gets
> triggered in highly concurrent situtations.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GERONIMO-6712) JsonValue Class initialisation might create a deadlock
Mark Struberg created GERONIMO-6712:
---
Summary: JsonValue Class initialisation might create a deadlock
Key: GERONIMO-6712
URL: https://issues.apache.org/jira/browse/GERONIMO-6712
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Components: specs
Reporter: Mark Struberg
Assignee: Mark Struberg
Our {{JsonValue}} class contains the following two static fields:
{souce}
JsonObject EMPTY_JSON_OBJECT = Json.createObjectBuilder().build();
JsonArray EMPTY_JSON_ARRAY = Json.createArrayBuilder().build();
{souce}
It basically starts up a whole Json Provider just for initialising the
JsonValue class.
This might lead to a deadlock in the JVM during the classloading if it gets
triggered in highly concurrent situtations.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GERONIMO-6606) Apply Portable Java Contracts to all specs
[ https://issues.apache.org/jira/browse/GERONIMO-6606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16499974#comment-16499974 ] Mark Struberg commented on GERONIMO-6606: - Hi Raymond! Thanks for the patch! I've applied it now. All, shall we release all those specs now? That might be quite a few releases. > Apply Portable Java Contracts to all specs > -- > > Key: GERONIMO-6606 > URL: https://issues.apache.org/jira/browse/GERONIMO-6606 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: specs >Reporter: Raymond Augé >Priority: Major > > I'd like all the specs to provide portable java contracts [1]. > To that end I will send a PR which adds these. > > [1] https://www.osgi.org/portable-java-contract-definitions/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GERONIMO-6607) [geronimo-config] variable replacement use cases
Mark Struberg created GERONIMO-6607: --- Summary: [geronimo-config] variable replacement use cases Key: GERONIMO-6607 URL: https://issues.apache.org/jira/browse/GERONIMO-6607 Project: Geronimo Issue Type: New Feature Security Level: public (Regular issues) Components: Config Reporter: Mark Struberg Attachments: PlaceholdersTest.java While getting the geronimo-config/trunk and branches/ConfigJSR in sync, I've switched the PlaceholdersTest from using the internal Placeholders class to the official API. While doing so I figured that we should not yet add this functionality at all. But first we should discuss this through with mp and ConfigJSR. The reason is that variable replacement is already added in ConfigJSR but does not yet contain all the cases Romain has on it's wishlist. Plus we also need to ensure that we do not loose too much performance. A few of the replacement rules are quite a bit 'meta'. Before we implement those I really need the use cases first. I'll attach the pimped PlaceholdersTest -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GERONIMO-6595) add support for Implicit Converters
[ https://issues.apache.org/jira/browse/GERONIMO-6595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved GERONIMO-6595. - Resolution: Fixed > add support for Implicit Converters > --- > > Key: GERONIMO-6595 > URL: https://issues.apache.org/jira/browse/GERONIMO-6595 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: Config >Affects Versions: Config_1.0 >Reporter: Mark Struberg >Assignee: Mark Struberg > Fix For: Config_1.1 > > > mp-config-1.2 requires to support implicit converters. > E.g. a ct(String) or a static valueOf(String) or valueOf(CharSequence) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (GERONIMO-6595) add support for Implicit Converters
Mark Struberg created GERONIMO-6595: --- Summary: add support for Implicit Converters Key: GERONIMO-6595 URL: https://issues.apache.org/jira/browse/GERONIMO-6595 Project: Geronimo Issue Type: New Feature Security Level: public (Regular issues) Components: Config Affects Versions: Config_1.0 Reporter: Mark Struberg Assignee: Mark Struberg Fix For: Config_1.1 mp-config-1.2 requires to support implicit converters. E.g. a ct(String) or a static valueOf(String) or valueOf(CharSequence) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (GERONIMO-6593) [config] Create a branch for JSR-382
Mark Struberg created GERONIMO-6593: --- Summary: [config] Create a branch for JSR-382 Key: GERONIMO-6593 URL: https://issues.apache.org/jira/browse/GERONIMO-6593 Project: Geronimo Issue Type: New Feature Security Level: public (Regular issues) Components: Config Affects Versions: Config_2.0 Reporter: Mark Struberg Assignee: Mark Struberg With the start of JSR-382 (Configuration API for Java, v1.0) we can also provide a branch of our config module. The code is currently really the same like with MicroProfile-Config. Just with javax.config as package name. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (GERONIMO-6577) [config] injection of @ConfigProperty Provider is broken
[
https://issues.apache.org/jira/browse/GERONIMO-6577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg updated GERONIMO-6577:
Description:
{code}
@Inject
@ConfigProperty(name="bla")
private Provider dynamicValue;
{code}
is broken; blows up with Missing converter for 'bla' from Field Injection
Point, field name : ...
was:
{source}
@Inject
@ConfigProperty(name="bla")
private Provider dynamicValue;
{source}
is broken; blows up with Missing converter for 'bla' from Field Injection
Point, field name : ...
> [config] injection of @ConfigProperty Provider is broken
> ---
>
> Key: GERONIMO-6577
> URL: https://issues.apache.org/jira/browse/GERONIMO-6577
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Config
>Reporter: Mark Struberg
>Assignee: Mark Struberg
>
> {code}
> @Inject
> @ConfigProperty(name="bla")
> private Provider dynamicValue;
> {code}
> is broken; blows up with Missing converter for 'bla' from Field Injection
> Point, field name : ...
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (GERONIMO-6577) [config] injection of @ConfigProperty Provider is broken
[
https://issues.apache.org/jira/browse/GERONIMO-6577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16117344#comment-16117344
]
Mark Struberg commented on GERONIMO-6577:
-
The problems got introduced with r1800744
> [config] injection of @ConfigProperty Provider is broken
> ---
>
> Key: GERONIMO-6577
> URL: https://issues.apache.org/jira/browse/GERONIMO-6577
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Config
>Reporter: Mark Struberg
>Assignee: Mark Struberg
>
> {source}
> @Inject
> @ConfigProperty(name="bla")
> private Provider dynamicValue;
> {source}
> is broken; blows up with Missing converter for 'bla' from Field Injection
> Point, field name : ...
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (GERONIMO-6577) [config] injection of @ConfigProperty Provider is broken
Mark Struberg created GERONIMO-6577:
---
Summary: [config] injection of @ConfigProperty Provider is
broken
Key: GERONIMO-6577
URL: https://issues.apache.org/jira/browse/GERONIMO-6577
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Components: Config
Reporter: Mark Struberg
Assignee: Mark Struberg
{source}
@Inject
@ConfigProperty(name="bla")
private Provider dynamicValue;
{source}
is broken; blows up with Missing converter for 'bla' from Field Injection
Point, field name : ...
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (GERONIMO-6572) Create geronimo-jpa_2.2_spec
[ https://issues.apache.org/jira/browse/GERONIMO-6572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated GERONIMO-6572: Description: The MR for JPA also brought a few minor code changes in the API. Most notably the Query#getResultStream() and RepeatableAnnotations. The preliminary change log can be found here: https://jcp.org/aboutJava/communityprocess/maintenance/jsr338/ChangeLog-JPA-2.2-MR.txt was: The MR for JPA also brought a few minor code changes in the API. Most notably the Query#getResultStream() and RepeatableAnnotations. > Create geronimo-jpa_2.2_spec > > > Key: GERONIMO-6572 > URL: https://issues.apache.org/jira/browse/GERONIMO-6572 > Project: Geronimo > Issue Type: Task > Security Level: public(Regular issues) > Components: specs >Reporter: Mark Struberg >Assignee: Mark Struberg > > The MR for JPA also brought a few minor code changes in the API. > Most notably the Query#getResultStream() and RepeatableAnnotations. > The preliminary change log can be found here: > https://jcp.org/aboutJava/communityprocess/maintenance/jsr338/ChangeLog-JPA-2.2-MR.txt -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (GERONIMO-6572) Create geronimo-jpa_2.2_spec
Mark Struberg created GERONIMO-6572: --- Summary: Create geronimo-jpa_2.2_spec Key: GERONIMO-6572 URL: https://issues.apache.org/jira/browse/GERONIMO-6572 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Components: specs Reporter: Mark Struberg Assignee: Mark Struberg The MR for JPA also brought a few minor code changes in the API. Most notably the Query#getResultStream() and RepeatableAnnotations. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (GERONIMO-6568) Create geronimo-annotation_1.3_spec
[ https://issues.apache.org/jira/browse/GERONIMO-6568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved GERONIMO-6568. - Resolution: Fixed > Create geronimo-annotation_1.3_spec > --- > > Key: GERONIMO-6568 > URL: https://issues.apache.org/jira/browse/GERONIMO-6568 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: specs >Reporter: Mark Struberg >Assignee: Mark Struberg > > common-annotations-1.3 is a MR of JSR-250 and did just change 1 piece: > It allows @Priority to also be added to Parameters. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (GERONIMO-6568) Create geronimo-annotation_1.3_spec
[ https://issues.apache.org/jira/browse/GERONIMO-6568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated GERONIMO-6568: Issue Type: New Feature (was: Bug) > Create geronimo-annotation_1.3_spec > --- > > Key: GERONIMO-6568 > URL: https://issues.apache.org/jira/browse/GERONIMO-6568 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: specs >Reporter: Mark Struberg >Assignee: Mark Struberg > > common-annotations-1.3 is a MR of JSR-250 and did just change 1 piece: > It allows @Priority to also be added to Parameters. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (GERONIMO-6568) Create geronimo-annotation_1.3_spec
Mark Struberg created GERONIMO-6568: --- Summary: Create geronimo-annotation_1.3_spec Key: GERONIMO-6568 URL: https://issues.apache.org/jira/browse/GERONIMO-6568 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: specs Reporter: Mark Struberg Assignee: Mark Struberg common-annotations-1.3 is a MR of JSR-250 and did just change 1 piece: It allows @Priority to also be added to Parameters. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GERONIMO-6553) CDI 2.0 Spec JAR Updates
[ https://issues.apache.org/jira/browse/GERONIMO-6553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16028499#comment-16028499 ] Mark Struberg commented on GERONIMO-6553: - Wohuu, with Johns latest contributions we are now down to zero functional diffs! There are a few slight diffs which are basically caused by doPrivileged blocks we do have. > CDI 2.0 Spec JAR Updates > > > Key: GERONIMO-6553 > URL: https://issues.apache.org/jira/browse/GERONIMO-6553 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: specs >Reporter: John D. Ament >Assignee: Mark Struberg > Attachments: GERONIMO_6553_Adding_Request_Context_Control.patch, > GERONIMO_6553_Adding_SE_support.patch, GERONIMO-6553.patch > > > Enhancements to the CDI 2.0 spec jar to include: > - async observers. > - prioritized elements > - configuration builders > - native literals > - Java 8 compatibility with bundles -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GERONIMO-6553) CDI 2.0 Spec JAR Updates
[ https://issues.apache.org/jira/browse/GERONIMO-6553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16028493#comment-16028493 ] Mark Struberg commented on GERONIMO-6553: - Cool, thanks will apply now > CDI 2.0 Spec JAR Updates > > > Key: GERONIMO-6553 > URL: https://issues.apache.org/jira/browse/GERONIMO-6553 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: specs >Reporter: John D. Ament >Assignee: Mark Struberg > Attachments: GERONIMO_6553_Adding_Request_Context_Control.patch, > GERONIMO_6553_Adding_SE_support.patch, GERONIMO-6553.patch > > > Enhancements to the CDI 2.0 spec jar to include: > - async observers. > - prioritized elements > - configuration builders > - native literals > - Java 8 compatibility with bundles -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GERONIMO-6553) CDI 2.0 Spec JAR Updates
[ https://issues.apache.org/jira/browse/GERONIMO-6553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16028444#comment-16028444 ] Mark Struberg commented on GERONIMO-6553: - Cool John, many thanks for the patch! We now just miss ActivateRequestContext and RequestContextController according to the signature comparison with the official jar! CLSS public abstract interface !annotation javax.enterprise.context.control.ActivateRequestContext anno 0 java.lang.annotation.Documented() anno 0 java.lang.annotation.Retention(java.lang.annotation.RetentionPolicy value=RUNTIME) anno 0 java.lang.annotation.Target(java.lang.annotation.ElementType[] value=[METHOD, TYPE]) anno 0 javax.interceptor.InterceptorBinding() intf java.lang.annotation.Annotation CLSS public abstract interface javax.enterprise.context.control.RequestContextController meth public abstract boolean activate() meth public abstract void deactivate() > CDI 2.0 Spec JAR Updates > > > Key: GERONIMO-6553 > URL: https://issues.apache.org/jira/browse/GERONIMO-6553 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: specs >Reporter: John D. Ament >Assignee: Mark Struberg > Attachments: GERONIMO_6553_Adding_SE_support.patch, > GERONIMO-6553.patch > > > Enhancements to the CDI 2.0 spec jar to include: > - async observers. > - prioritized elements > - configuration builders > - native literals > - Java 8 compatibility with bundles -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Reopened] (GERONIMO-6553) CDI 2.0 Spec JAR Updates
[ https://issues.apache.org/jira/browse/GERONIMO-6553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg reopened GERONIMO-6553: - Heh true, we should reopen this ticket formally ;) Thanks for the patch, John! Will apply it now. > CDI 2.0 Spec JAR Updates > > > Key: GERONIMO-6553 > URL: https://issues.apache.org/jira/browse/GERONIMO-6553 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: specs >Reporter: John D. Ament >Assignee: Mark Struberg > Attachments: GERONIMO_6553_Adding_SE_support.patch, > GERONIMO-6553.patch > > > Enhancements to the CDI 2.0 spec jar to include: > - async observers. > - prioritized elements > - configuration builders > - native literals > - Java 8 compatibility with bundles -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (GERONIMO-6566) Implement MicroProfile Config
[ https://issues.apache.org/jira/browse/GERONIMO-6566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated GERONIMO-6566: Component/s: (was: common) Config > Implement MicroProfile Config > - > > Key: GERONIMO-6566 > URL: https://issues.apache.org/jira/browse/GERONIMO-6566 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: Config >Reporter: Mark Struberg >Assignee: Mark Struberg > > A long time ago we've discussed to start a EE configuration project for > Application configuration. This now got made close to become the basis for a > standard in the MicroProfile movement. > The Config approach is based on Gerhards and my work in OWB and DeltaSpike, > but sadly got made a standard outside of the ASF. > But at least the implementation should live on over here. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (GERONIMO-6566) Implement MicroProfile Config
[ https://issues.apache.org/jira/browse/GERONIMO-6566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved GERONIMO-6566. - Resolution: Fixed > Implement MicroProfile Config > - > > Key: GERONIMO-6566 > URL: https://issues.apache.org/jira/browse/GERONIMO-6566 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: common >Reporter: Mark Struberg >Assignee: Mark Struberg > > A long time ago we've discussed to start a EE configuration project for > Application configuration. This now got made close to become the basis for a > standard in the MicroProfile movement. > The Config approach is based on Gerhards and my work in OWB and DeltaSpike, > but sadly got made a standard outside of the ASF. > But at least the implementation should live on over here. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (GERONIMO-6567) Expose configuration system details via JMX
Mark Struberg created GERONIMO-6567: --- Summary: Expose configuration system details via JMX Key: GERONIMO-6567 URL: https://issues.apache.org/jira/browse/GERONIMO-6567 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: Config Reporter: Mark Struberg Assignee: Mark Struberg This is basically the same functionality as we are currently implementing in DeltaSpike Config as well https://issues.apache.org/jira/browse/DELTASPIKE-1245 Each application should be able to expose details about it's configuration via a MBean (JMX). The following info should be made available 1.) The list of all picked up ConfigSources + their ordinals. Of course already sorted 2.) All configured values. - their key - their 'native' value (without variables, etc) - the ConfigSource from which the value effectively got picked up Map of all the ConfigSources containing the key + the values which got resolved on each level. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (GERONIMO-6566) Implement MicroProfile Config
Mark Struberg created GERONIMO-6566: --- Summary: Implement MicroProfile Config Key: GERONIMO-6566 URL: https://issues.apache.org/jira/browse/GERONIMO-6566 Project: Geronimo Issue Type: New Feature Security Level: public (Regular issues) Components: common Reporter: Mark Struberg Assignee: Mark Struberg A long time ago we've discussed to start a EE configuration project for Application configuration. This now got made close to become the basis for a standard in the MicroProfile movement. The Config approach is based on Gerhards and my work in OWB and DeltaSpike, but sadly got made a standard outside of the ASF. But at least the implementation should live on over here. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GERONIMO-6564) Move the JSONB api from Johnzon to Geronimo
[ https://issues.apache.org/jira/browse/GERONIMO-6564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15978738#comment-15978738 ] Mark Struberg commented on GERONIMO-6564: - patch applied, thanks Christian! > Move the JSONB api from Johnzon to Geronimo > --- > > Key: GERONIMO-6564 > URL: https://issues.apache.org/jira/browse/GERONIMO-6564 > Project: Geronimo > Issue Type: Task > Security Level: public(Regular issues) > Components: specs >Reporter: Mark Struberg >Assignee: Mark Struberg > Attachments: GERONIMO-6564-1.patch > > > The JSONB api (JSR-367) got finished in Apache Johnzon and is ready to get > moved to geronimo and get released. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (GERONIMO-6564) Move the JSONB api from Johnzon to Geronimo
[ https://issues.apache.org/jira/browse/GERONIMO-6564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved GERONIMO-6564. - Resolution: Fixed > Move the JSONB api from Johnzon to Geronimo > --- > > Key: GERONIMO-6564 > URL: https://issues.apache.org/jira/browse/GERONIMO-6564 > Project: Geronimo > Issue Type: Task > Security Level: public(Regular issues) > Components: specs >Reporter: Mark Struberg >Assignee: Mark Struberg > > The JSONB api (JSR-367) got finished in Apache Johnzon and is ready to get > moved to geronimo and get released. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (GERONIMO-6564) Move the JSONB api from Johnzon to Geronimo
Mark Struberg created GERONIMO-6564: --- Summary: Move the JSONB api from Johnzon to Geronimo Key: GERONIMO-6564 URL: https://issues.apache.org/jira/browse/GERONIMO-6564 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Components: specs Reporter: Mark Struberg Assignee: Mark Struberg The JSONB api (JSR-367) got finished in Apache Johnzon and is ready to get moved to geronimo and get released. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GERONIMO-6558) API for JSR-374 JSON-P 1.1
[ https://issues.apache.org/jira/browse/GERONIMO-6558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15691297#comment-15691297 ] Mark Struberg commented on GERONIMO-6558: - patch applied, txs Reinhard! > API for JSR-374 JSON-P 1.1 > -- > > Key: GERONIMO-6558 > URL: https://issues.apache.org/jira/browse/GERONIMO-6558 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: specs >Reporter: Mark Struberg >Assignee: Mark Struberg > Attachments: GERONIMO-6558-jsonpatch-doc.patch > > > we already have started working on the JSR-374 JSON-P 1.1 API, but no ticket > for it yet. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (GERONIMO-6558) API for JSR-374 JSON-P 1.1
Mark Struberg created GERONIMO-6558: --- Summary: API for JSR-374 JSON-P 1.1 Key: GERONIMO-6558 URL: https://issues.apache.org/jira/browse/GERONIMO-6558 Project: Geronimo Issue Type: New Feature Security Level: public (Regular issues) Components: specs Reporter: Mark Struberg Assignee: Mark Struberg we already have started working on the JSR-374 JSON-P 1.1 API, but no ticket for it yet. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (GERONIMO-6556) geronimo-jcdi AnnotationLiteral could cache the hashCode and toString values
Mark Struberg created GERONIMO-6556: --- Summary: geronimo-jcdi AnnotationLiteral could cache the hashCode and toString values Key: GERONIMO-6556 URL: https://issues.apache.org/jira/browse/GERONIMO-6556 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Reporter: Mark Struberg Assignee: Mark Struberg We could improve the performance of our AnnotationLiteral implementation by doing more aggressive caching. Currently there is always a getMethods() call via SecurityManager involved. But that is pretty performance intense and not necessary. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GERONIMO-6555) improve documentation of our validation-1.1 spec api
[ https://issues.apache.org/jira/browse/GERONIMO-6555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved GERONIMO-6555. - Resolution: Fixed constraints and a few other important classes now got documented. > improve documentation of our validation-1.1 spec api > - > > Key: GERONIMO-6555 > URL: https://issues.apache.org/jira/browse/GERONIMO-6555 > Project: Geronimo > Issue Type: Task > Security Level: public(Regular issues) > Components: specs >Reporter: Mark Struberg >Assignee: Mark Struberg > > Currently the bean validation spec api is really underdocumented. > We should pimp this and release a 1.0 jar -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GERONIMO-6555) improve documentation of our validation-1.1 spec api
[ https://issues.apache.org/jira/browse/GERONIMO-6555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated GERONIMO-6555: Summary: improve documentation of our validation-1.1 spec api (was: improve documentation of our valication-1.1 spec api ) > improve documentation of our validation-1.1 spec api > - > > Key: GERONIMO-6555 > URL: https://issues.apache.org/jira/browse/GERONIMO-6555 > Project: Geronimo > Issue Type: Task > Security Level: public(Regular issues) > Components: specs >Reporter: Mark Struberg >Assignee: Mark Struberg > > Currently the bean validation spec api is really underdocumented. > We should pimp this and release a 1.0 jar -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (GERONIMO-6555) improve documentation of our valication-1.1 spec api
Mark Struberg created GERONIMO-6555: --- Summary: improve documentation of our valication-1.1 spec api Key: GERONIMO-6555 URL: https://issues.apache.org/jira/browse/GERONIMO-6555 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Components: specs Reporter: Mark Struberg Assignee: Mark Struberg Currently the bean validation spec api is really underdocumented. We should pimp this and release a 1.0 jar -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GERONIMO-6553) CDI 2.0 Spec JAR Updates
[ https://issues.apache.org/jira/browse/GERONIMO-6553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved GERONIMO-6553. - Resolution: Fixed Assignee: Mark Struberg txs for the patch, committed! > CDI 2.0 Spec JAR Updates > > > Key: GERONIMO-6553 > URL: https://issues.apache.org/jira/browse/GERONIMO-6553 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: specs >Reporter: John D. Ament >Assignee: Mark Struberg > Attachments: GERONIMO-6553.patch > > > Enhancements to the CDI 2.0 spec jar to include: > - async observers. > - prioritized elements > - configuration builders > - native literals > - Java 8 compatibility with bundles -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (GERONIMO-6546) add geronimo-jcdi-2.0 EDR package
Mark Struberg created GERONIMO-6546: --- Summary: add geronimo-jcdi-2.0 EDR package Key: GERONIMO-6546 URL: https://issues.apache.org/jira/browse/GERONIMO-6546 Project: Geronimo Issue Type: New Feature Security Level: public (Regular issues) Components: specs Reporter: Mark Struberg Assignee: Mark Struberg The JSR-365 EG has started with the work on CDI-2.0. I'm an active EG member and over in OpenWebBeans we like to start with the work on CDI-2.0 as well. Thus I'm copying over the CDI-1.1 api and will tweak it acordingly. This package will explicitly be marked as EDR until the final spec is out and we pas the TCKs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GERONIMO-6533) [Geronimo Javamail] InternetAddress should throw exception in strict mode for invalid address
[
https://issues.apache.org/jira/browse/GERONIMO-6533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14176233#comment-14176233
]
Mark Struberg commented on GERONIMO-6533:
-
Hi Hendrik!
I did not look closely but I remember a few pitfalls from Sigfried Göschls work
over at commons-email. E.g. we also need to look at rfc-2606
https://tools.ietf.org/html/rfc2606
{quote}
...
To safely satisfy these needs, four domain names are reserved as
listed and described below.
.test
.example
.invalid
.localhost
".test" is recommended for use in testing of current or new DNS
related code.
".example" is recommended for use in documentation or as examples.
".invalid" is intended for use in online construction of domain
names that are sure to be invalid and which it is obvious at a
glance are invalid.
{quote}
> [Geronimo Javamail] InternetAddress should throw exception in strict mode for
> invalid address
> -
>
> Key: GERONIMO-6533
> URL: https://issues.apache.org/jira/browse/GERONIMO-6533
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: mail
>Reporter: Arnaud MERGEY
>
> Unlike Oracle Javamail to Geronimo Javamail implementation, Geronimo Javamail
> accept invalid emails even in strict mode
> Executing;
> javax.mail.internet.InternetAddress("a",true);
> fails throwing AddressException with Oracle Javamail, but succeed with
> Geronimo Javamail
> validate() succeed as well, it should throw an exception when address is not
> an email address
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (GERONIMO-6530) upgrade geronimo-genesis to latest parent and check plugin upgrades
[ https://issues.apache.org/jira/browse/GERONIMO-6530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved GERONIMO-6530. - Resolution: Fixed Fix Version/s: 2.2 > upgrade geronimo-genesis to latest parent and check plugin upgrades > --- > > Key: GERONIMO-6530 > URL: https://issues.apache.org/jira/browse/GERONIMO-6530 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Reporter: Mark Struberg >Assignee: Mark Struberg > Fix For: 2.2 > > > this also should add apache-rat as default plugin. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GERONIMO-6527) JavaMail 1.5 spec
[ https://issues.apache.org/jira/browse/GERONIMO-6527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14124966#comment-14124966 ] Mark Struberg commented on GERONIMO-6527: - no worries, in the meantime I just rewrote the JavaDoc ;) > JavaMail 1.5 spec > - > > Key: GERONIMO-6527 > URL: https://issues.apache.org/jira/browse/GERONIMO-6527 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) >Reporter: Hendrik Saly >Assignee: Romain Manni-Bucau > Attachments: diff_javamail14_gitpatch.patch > > > Pls. find below a JavaMail 1.5 spec impl: > https://github.com/salyh/geronimo-specs/tree/trunk/geronimo-javamail_1.5_spec > Diff against geronimo JavaMail 1.4 spec: > https://github.com/salyh/geronimo-specs/commit/cda5d35f59eadb2c269d97c29fbe41d83d02dc6a -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (GERONIMO-6527) JavaMail 1.5 spec
[ https://issues.apache.org/jira/browse/GERONIMO-6527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg reopened GERONIMO-6527: - seems like we need to review the patch again. It contains JavaDoc which is obviously taken from the RI. This is a no-go! We need to rewrite the JavaDoc. > JavaMail 1.5 spec > - > > Key: GERONIMO-6527 > URL: https://issues.apache.org/jira/browse/GERONIMO-6527 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) >Reporter: Hendrik Saly >Assignee: Romain Manni-Bucau > Attachments: diff_javamail14_gitpatch.patch > > > Pls. find below a JavaMail 1.5 spec impl: > https://github.com/salyh/geronimo-specs/tree/trunk/geronimo-javamail_1.5_spec > Diff against geronimo JavaMail 1.4 spec: > https://github.com/salyh/geronimo-specs/commit/cda5d35f59eadb2c269d97c29fbe41d83d02dc6a -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GERONIMO-6527) JavaMail 1.5 spec
[ https://issues.apache.org/jira/browse/GERONIMO-6527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14124941#comment-14124941 ] Mark Struberg commented on GERONIMO-6527: - Hendrik, seems your patch missed the Apache License headers. Gonna add them now. Please let us know if you are not ok with this. > JavaMail 1.5 spec > - > > Key: GERONIMO-6527 > URL: https://issues.apache.org/jira/browse/GERONIMO-6527 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) >Reporter: Hendrik Saly >Assignee: Romain Manni-Bucau > Attachments: diff_javamail14_gitpatch.patch > > > Pls. find below a JavaMail 1.5 spec impl: > https://github.com/salyh/geronimo-specs/tree/trunk/geronimo-javamail_1.5_spec > Diff against geronimo JavaMail 1.4 spec: > https://github.com/salyh/geronimo-specs/commit/cda5d35f59eadb2c269d97c29fbe41d83d02dc6a -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (GERONIMO-6530) upgrade geronimo-genesis to latest parent and check plugin upgrades
Mark Struberg created GERONIMO-6530: --- Summary: upgrade geronimo-genesis to latest parent and check plugin upgrades Key: GERONIMO-6530 URL: https://issues.apache.org/jira/browse/GERONIMO-6530 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Reporter: Mark Struberg Assignee: Mark Struberg this also should add apache-rat as default plugin. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GERONIMO-6458) API jar for JSR 346 - CDI 1.1
[ https://issues.apache.org/jira/browse/GERONIMO-6458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13984106#comment-13984106 ] Mark Struberg commented on GERONIMO-6458: - Patch applied, txs Arne! > API jar for JSR 346 - CDI 1.1 > - > > Key: GERONIMO-6458 > URL: https://issues.apache.org/jira/browse/GERONIMO-6458 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) >Reporter: Kevin Sutter >Assignee: Mark Struberg > Attachments: GERONIMO-6458.patch > > > Update jar file for Java EE 7. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (GERONIMO-6451) API jar for JSR 338 - JPA 2.1
[ https://issues.apache.org/jira/browse/GERONIMO-6451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13868089#comment-13868089 ] Mark Struberg commented on GERONIMO-6451: - we can easily release an -alpha1 version. Please note that we must not ship any final jars before we fully passed the TCK! > API jar for JSR 338 - JPA 2.1 > - > > Key: GERONIMO-6451 > URL: https://issues.apache.org/jira/browse/GERONIMO-6451 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) >Reporter: Kevin Sutter > Attachments: geronimo-jpa_2.1_spec-1.0-src.jar, > geronimo-jpa_2.1_spec-1.0.jar, geronimo-jpa_2.1_spec-1.0.jar, > jpa2.1-src.patch.txt > > > Updated JPA 2.1 jar for Java EE 7. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (GERONIMO-6514) cdi-1.1 API misses the 'Unmanaged' class
[ https://issues.apache.org/jira/browse/GERONIMO-6514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved GERONIMO-6514. - Resolution: Fixed > cdi-1.1 API misses the 'Unmanaged' class > > > Key: GERONIMO-6514 > URL: https://issues.apache.org/jira/browse/GERONIMO-6514 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: specs >Reporter: Mark Struberg >Assignee: Mark Struberg > > Unmanaged and UnmanagedInstance are missing in the CDI-1.1 spec API package. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (GERONIMO-6514) cdi-1.1 API misses the 'Unmanaged' class
Mark Struberg created GERONIMO-6514: --- Summary: cdi-1.1 API misses the 'Unmanaged' class Key: GERONIMO-6514 URL: https://issues.apache.org/jira/browse/GERONIMO-6514 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: specs Reporter: Mark Struberg Assignee: Mark Struberg Unmanaged and UnmanagedInstance are missing in the CDI-1.1 spec API package. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Assigned] (GERONIMO-6458) API jar for JSR 346 - CDI 1.1
[ https://issues.apache.org/jira/browse/GERONIMO-6458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg reassigned GERONIMO-6458: --- Assignee: Mark Struberg > API jar for JSR 346 - CDI 1.1 > - > > Key: GERONIMO-6458 > URL: https://issues.apache.org/jira/browse/GERONIMO-6458 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) >Reporter: Kevin Sutter >Assignee: Mark Struberg > > Update jar file for Java EE 7. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (GERONIMO-6464) API jar for JSR 250 (Common Annotations 1.2 MR2)
[ https://issues.apache.org/jira/browse/GERONIMO-6464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg reassigned GERONIMO-6464: --- Assignee: Mark Struberg > API jar for JSR 250 (Common Annotations 1.2 MR2) > > > Key: GERONIMO-6464 > URL: https://issues.apache.org/jira/browse/GERONIMO-6464 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) > Components: Java EE 7 >Reporter: Kevin Sutter >Assignee: Mark Struberg > > Maintenance Release update for Java EE 7. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6441) remove unused genesis modules
[ https://issues.apache.org/jira/browse/GERONIMO-6441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved GERONIMO-6441. - Resolution: Fixed > remove unused genesis modules > - > > Key: GERONIMO-6441 > URL: https://issues.apache.org/jira/browse/GERONIMO-6441 > Project: Geronimo > Issue Type: Task > Security Level: public(Regular issues) > Components: buildsystem >Reporter: Mark Struberg >Assignee: Mark Struberg > > geronimo genesis contains a few modules which are not enabled since a long > time. We shall remove them from our SCM as they just cause confusion... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6441) remove unused genesis modules
[ https://issues.apache.org/jira/browse/GERONIMO-6441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13596920#comment-13596920 ] Mark Struberg commented on GERONIMO-6441: - I now removed * genesis-skin * genesis-maven-plugin They were not contained in the last few releases it seems and were not even enabled in the section thus not available for snapshots neither. > remove unused genesis modules > - > > Key: GERONIMO-6441 > URL: https://issues.apache.org/jira/browse/GERONIMO-6441 > Project: Geronimo > Issue Type: Task > Security Level: public(Regular issues) > Components: buildsystem >Reporter: Mark Struberg >Assignee: Mark Struberg > > geronimo genesis contains a few modules which are not enabled since a long > time. We shall remove them from our SCM as they just cause confusion... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMO-6441) remove unused genesis modules
Mark Struberg created GERONIMO-6441: --- Summary: remove unused genesis modules Key: GERONIMO-6441 URL: https://issues.apache.org/jira/browse/GERONIMO-6441 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Components: buildsystem Reporter: Mark Struberg Assignee: Mark Struberg geronimo genesis contains a few modules which are not enabled since a long time. We shall remove them from our SCM as they just cause confusion... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (XBEAN-239) toURL() is deprecated and causes a build error
[
https://issues.apache.org/jira/browse/XBEAN-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13573437#comment-13573437
]
Mark Struberg commented on XBEAN-239:
-
Additional patch from Romain applied. Waiting for JIRA privileges to set it to
'resolved' ;)
> toURL() is deprecated and causes a build error
> --
>
> Key: XBEAN-239
> URL: https://issues.apache.org/jira/browse/XBEAN-239
> Project: XBean
> Issue Type: Bug
>Affects Versions: 3.12
>Reporter: Mark Struberg
> Attachments: xbean-java7.patch
>
>
> When compiling XBean I get the following error
> [ERROR]
> /Users/struberg/develop/java/apache/geronimo/xbean/xbean-spring/src/main/java/org/apache/xbean/spring/generator/QdoxMappingLoader.java:545:
> warning: [deprecation] toURL() in File has been deprecated
> [ERROR] builder.addSource(new URL("jar:" + base.toURL().toString() + "!/" +
> name));
> The solution is to replace toURL() with .toURI().toURL().
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6433) upgrade genesis to latest apache.parent and plugins
[ https://issues.apache.org/jira/browse/GERONIMO-6433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved GERONIMO-6433. - Resolution: Fixed > upgrade genesis to latest apache.parent and plugins > --- > > Key: GERONIMO-6433 > URL: https://issues.apache.org/jira/browse/GERONIMO-6433 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: buildsystem >Reporter: Mark Struberg > > upgrade genesis to latest apache.parent and plugins. > The currently released genesis version is stone old and outdated... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMO-6433) upgrade genesis to latest apache.parent and plugins
Mark Struberg created GERONIMO-6433: --- Summary: upgrade genesis to latest apache.parent and plugins Key: GERONIMO-6433 URL: https://issues.apache.org/jira/browse/GERONIMO-6433 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: buildsystem Reporter: Mark Struberg upgrade genesis to latest apache.parent and plugins. The currently released genesis version is stone old and outdated... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (XBEAN-239) toURL() is deprecated and causes a build error
Mark Struberg created XBEAN-239:
---
Summary: toURL() is deprecated and causes a build error
Key: XBEAN-239
URL: https://issues.apache.org/jira/browse/XBEAN-239
Project: XBean
Issue Type: Bug
Affects Versions: 3.12
Reporter: Mark Struberg
When compiling XBean I get the following error
[ERROR]
/Users/struberg/develop/java/apache/geronimo/xbean/xbean-spring/src/main/java/org/apache/xbean/spring/generator/QdoxMappingLoader.java:545:
warning: [deprecation] toURL() in File has been deprecated
[ERROR] builder.addSource(new URL("jar:" + base.toURL().toString() + "!/" +
name));
The solution is to replace toURL() with .toURI().toURL().
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMO-6170) jdci-spec AnnotationLiteral hides root Exception
jdci-spec AnnotationLiteral hides root Exception Key: GERONIMO-6170 URL: https://issues.apache.org/jira/browse/GERONIMO-6170 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Reporter: Mark Struberg gerinimo_jcdi_1.0_spec AnnotationLiteral#callMethod catches an Exception and throws a RuntimeException without passing the root cause. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-5444) Add slight delay during async startup of ActiveMQ
[ https://issues.apache.org/jira/browse/GERONIMO-5444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12886862#action_12886862 ] Mark Struberg commented on GERONIMO-5444: - is there any started() or ready() 'event' (callback, etc) which can listen to? I always feel really uncomfortable when I hear the word 'delays' ;) > Add slight delay during async startup of ActiveMQ > - > > Key: GERONIMO-5444 > URL: https://issues.apache.org/jira/browse/GERONIMO-5444 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: ActiveMQ >Affects Versions: 2.2.1 >Reporter: Kevan Miller > Fix For: 2.2.1, 3.0 > > > If ActiveMQ is being started asynchronously (e.g. for a master-slave shared > file system configuration), JMS clients may be started prior to the actual > start of the server. We should allow the doStart of the ActiveMQ service to > have a delay, giving time for the service to start, if this server ends up > being the Master. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-5438) latest geronimo-3 trunk doesn't compile against latest OpenEJB trunk
[ https://issues.apache.org/jira/browse/GERONIMO-5438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved GERONIMO-5438. - Resolution: Fixed This has been fixed by David Blevins in OpenEJB now. > latest geronimo-3 trunk doesn't compile against latest OpenEJB trunk > > > Key: GERONIMO-5438 > URL: https://issues.apache.org/jira/browse/GERONIMO-5438 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: OpenEJB >Affects Versions: 3.0 >Reporter: Mark Struberg > Fix For: 3.0 > > > The following errors happen while compiling geronimo-openejb > /home/msx/develop/java/apache/geronimo/server/plugins/openejb/geronimo-openejb/src/main/java/org/apache/geronimo/openejb/GeronimoSecurityService.java:[53,45] > [deprecation] > login(java.lang.String,javax.security.auth.callback.CallbackHandler) in > org.apache.geronimo.security.ContextManager has been deprecated > /home/msx/develop/java/apache/geronimo/server/plugins/openejb/geronimo-openejb/src/main/java/org/apache/geronimo/openejb/EntityManagerRegistryImpl.java:[52,36] > > getEntityManager(javax.persistence.EntityManagerFactory,java.util.Map,boolean,java.lang.String) > in org.apache.openejb.persistence.JtaEntityManagerRegistry cannot be applied > to (javax.persistence.EntityManagerFactory,java.util.Map,boolean) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5438) latest geronimo-3 trunk doesn't compile against latest OpenEJB trunk
latest geronimo-3 trunk doesn't compile against latest OpenEJB trunk Key: GERONIMO-5438 URL: https://issues.apache.org/jira/browse/GERONIMO-5438 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: OpenEJB Affects Versions: 3.0 Reporter: Mark Struberg Fix For: 3.0 The following errors happen while compiling geronimo-openejb /home/msx/develop/java/apache/geronimo/server/plugins/openejb/geronimo-openejb/src/main/java/org/apache/geronimo/openejb/GeronimoSecurityService.java:[53,45] [deprecation] login(java.lang.String,javax.security.auth.callback.CallbackHandler) in org.apache.geronimo.security.ContextManager has been deprecated /home/msx/develop/java/apache/geronimo/server/plugins/openejb/geronimo-openejb/src/main/java/org/apache/geronimo/openejb/EntityManagerRegistryImpl.java:[52,36] getEntityManager(javax.persistence.EntityManagerFactory,java.util.Map,boolean,java.lang.String) in org.apache.openejb.persistence.JtaEntityManagerRegistry cannot be applied to (javax.persistence.EntityManagerFactory,java.util.Map,boolean) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5436) ClassCastException in Deployer
[ https://issues.apache.org/jira/browse/GERONIMO-5436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12886048#action_12886048 ] Mark Struberg commented on GERONIMO-5436: - nope latest 3.0.0-SNAPSHOT from SVN trunk of today 11:00 GMT > ClassCastException in Deployer > -- > > Key: GERONIMO-5436 > URL: https://issues.apache.org/jira/browse/GERONIMO-5436 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: deployment >Affects Versions: 3.0 >Reporter: Mark Struberg > Fix For: 3.0 > > Attachments: GERONIMO-5436.patch > > > While deploying a EAR I get a ClassCastException in MergeHelper#347 > webFragment = (WebFragment) xmlObject; > but xmlObject is actually of type > org.apache.xmlbeans.impl.values.XmlAnyTypeImpl -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5436) ClassCastException in Deployer
[ https://issues.apache.org/jira/browse/GERONIMO-5436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12885919#action_12885919 ] Mark Struberg commented on GERONIMO-5436: - The web-fragment is coming from this jar: http://repository.prime.com.tr/org/primefaces/primefaces/2.0.2/primefaces-2.0.2.jar > ClassCastException in Deployer > -- > > Key: GERONIMO-5436 > URL: https://issues.apache.org/jira/browse/GERONIMO-5436 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: deployment >Affects Versions: 3.0 >Reporter: Mark Struberg > Fix For: 3.0 > > Attachments: GERONIMO-5436.patch > > > While deploying a EAR I get a ClassCastException in MergeHelper#347 > webFragment = (WebFragment) xmlObject; > but xmlObject is actually of type > org.apache.xmlbeans.impl.values.XmlAnyTypeImpl -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5436) ClassCastException in Deployer
[ https://issues.apache.org/jira/browse/GERONIMO-5436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated GERONIMO-5436: Attachment: GERONIMO-5436.patch this patch logs a warning for such cases and outputs the XmlObjects content. In my situation I now get the following output in the console: 2010-07-07 12:16:01,532 WARN [MergeHelper] Fail: expected WebFragment but got: org.apache.xmlbeans.impl.values.XmlAnyTypeImpl / http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-fragment_3_0.xsd"; version="3.0" xmlns="http://java.sun.com/xml/ns/javaee"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> PrimeFaces PrimeFaces Resource Servlet org.primefaces.resource.ResourceServlet PrimeFaces Resource Servlet /primefaces_resource/* > ClassCastException in Deployer > -- > > Key: GERONIMO-5436 > URL: https://issues.apache.org/jira/browse/GERONIMO-5436 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: deployment >Affects Versions: 3.0 >Reporter: Mark Struberg > Fix For: 3.0 > > Attachments: GERONIMO-5436.patch > > > While deploying a EAR I get a ClassCastException in MergeHelper#347 > webFragment = (WebFragment) xmlObject; > but xmlObject is actually of type > org.apache.xmlbeans.impl.values.XmlAnyTypeImpl -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5436) ClassCastException in Deployer
ClassCastException in Deployer -- Key: GERONIMO-5436 URL: https://issues.apache.org/jira/browse/GERONIMO-5436 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: deployment Affects Versions: 3.0 Reporter: Mark Struberg Fix For: 3.0 While deploying a EAR I get a ClassCastException in MergeHelper#347 webFragment = (WebFragment) xmlObject; but xmlObject is actually of type org.apache.xmlbeans.impl.values.XmlAnyTypeImpl -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5433) improve geronimo openwebbeans plugin
improve geronimo openwebbeans plugin Key: GERONIMO-5433 URL: https://issues.apache.org/jira/browse/GERONIMO-5433 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: OpenWebBeans Affects Versions: 3.0-M1 Reporter: Mark Struberg Fix For: 3.0 The current OpenWebBeans integration does not compile + there is a new OpenWebBeans-1.0.0-alpha-1 release currently in the VOTE. I'd like to provide a few patches to test the integration with geronimo-3.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5433) improve geronimo openwebbeans plugin
[ https://issues.apache.org/jira/browse/GERONIMO-5433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated GERONIMO-5433: Attachment: GERONIMO-5433.patch here we go. This patch is not yet production ready but might be a starting point the further development. TODOs: * openwebbeans-1.0.0-alpha-1 must be finally released * javassist-3.12.2.GA (containing OSGi info) must be released to maven.central. The SNAPSHOT which contains bundle info might be cloned from git clone git://github.com/struberg/javassist.git > improve geronimo openwebbeans plugin > > > Key: GERONIMO-5433 > URL: https://issues.apache.org/jira/browse/GERONIMO-5433 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: OpenWebBeans >Affects Versions: 3.0-M1 >Reporter: Mark Struberg > Fix For: 3.0 > > Attachments: GERONIMO-5433.patch > > > The current OpenWebBeans integration does not compile + there is a new > OpenWebBeans-1.0.0-alpha-1 release currently in the VOTE. > I'd like to provide a few patches to test the integration with geronimo-3.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5427) using a maven snapshot in a plugin causes the osgi-plugin to throw a NFE
[ https://issues.apache.org/jira/browse/GERONIMO-5427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated GERONIMO-5427: Attachment: GERONIMO-5427.patch The reason is the Require-Bundle manifest entry which doesn't get polished by the BND util. This patch is _only_ to show the effect and shall _not_ get applied in this way! Instead this should get properly fixed in the underlying OSGi libraries which got used to create the bundle. I'm not sure if we should add some invalid bundle detection in geronimo to prevent such things. > using a maven snapshot in a plugin causes the osgi-plugin to throw a NFE > > > Key: GERONIMO-5427 > URL: https://issues.apache.org/jira/browse/GERONIMO-5427 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: buildsystem >Affects Versions: 3.0-M1 >Reporter: Mark Struberg > Attachments: GERONIMO-5427.patch > > > This is somehow related to GERONIMO-5392: > It seems that a very similar thing also happens while building plugins which > reference to SNAPSHOT versions. > While upgrading the plugins/myfaces to myfaces-2.0.1-SNAPSHOT locally and > trying to compile the plugin, I get the following Exception: > java.lang.NumberFormatException: For input string: "1-SNAPSHOT" > at > java.lang.NumberFormatException.forInputString(NumberFormatException.java:48) > at java.lang.Integer.parseInt(Integer.java:458) > at java.lang.Integer.parseInt(Integer.java:499) > at org.osgi.framework.Version.(Version.java:133) > at org.osgi.framework.Version.parseVersion(Version.java:218) > at > org.eclipse.osgi.service.resolver.VersionRange.(VersionRange.java:92) > at > org.eclipse.osgi.internal.resolver.StateBuilder.getVersionRange(StateBuilder.java:532) > at > org.eclipse.osgi.internal.resolver.StateBuilder.createRequiredBundle(StateBuilder.java:217) > at > org.eclipse.osgi.internal.resolver.StateBuilder.createRequiredBundles(StateBuilder.java:210) > at > org.eclipse.osgi.internal.resolver.StateBuilder.createBundleDescription(StateBuilder.java:101) > at > org.eclipse.osgi.internal.resolver.StateObjectFactoryImpl.createBundleDescription(StateObjectFactoryImpl.java:32) > at > org.apache.geronimo.mavenplugins.osgi.utils.BundleResolver.addBundle(BundleResolver.java:173) > at > org.apache.geronimo.mavenplugins.osgi.utils.BundleResolver.addBundle(BundleResolver.java:129) > at > org.apache.geronimo.mavenplugins.osgi.utils.BundleResolver.addBundle(BundleResolver.java:119) > at > org.apache.geronimo.mavenplugins.osgi.VerifyManifestMojo.execute(VerifyManifestMojo.java:101) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5427) using a maven snapshot in a plugin causes the osgi-plugin to throw a NFE
using a maven snapshot in a plugin causes the osgi-plugin to throw a NFE Key: GERONIMO-5427 URL: https://issues.apache.org/jira/browse/GERONIMO-5427 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: buildsystem Affects Versions: 3.0-M1 Reporter: Mark Struberg This is somehow related to GERONIMO-5392: It seems that a very similar thing also happens while building plugins which reference to SNAPSHOT versions. While upgrading the plugins/myfaces to myfaces-2.0.1-SNAPSHOT locally and trying to compile the plugin, I get the following Exception: java.lang.NumberFormatException: For input string: "1-SNAPSHOT" at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48) at java.lang.Integer.parseInt(Integer.java:458) at java.lang.Integer.parseInt(Integer.java:499) at org.osgi.framework.Version.(Version.java:133) at org.osgi.framework.Version.parseVersion(Version.java:218) at org.eclipse.osgi.service.resolver.VersionRange.(VersionRange.java:92) at org.eclipse.osgi.internal.resolver.StateBuilder.getVersionRange(StateBuilder.java:532) at org.eclipse.osgi.internal.resolver.StateBuilder.createRequiredBundle(StateBuilder.java:217) at org.eclipse.osgi.internal.resolver.StateBuilder.createRequiredBundles(StateBuilder.java:210) at org.eclipse.osgi.internal.resolver.StateBuilder.createBundleDescription(StateBuilder.java:101) at org.eclipse.osgi.internal.resolver.StateObjectFactoryImpl.createBundleDescription(StateObjectFactoryImpl.java:32) at org.apache.geronimo.mavenplugins.osgi.utils.BundleResolver.addBundle(BundleResolver.java:173) at org.apache.geronimo.mavenplugins.osgi.utils.BundleResolver.addBundle(BundleResolver.java:129) at org.apache.geronimo.mavenplugins.osgi.utils.BundleResolver.addBundle(BundleResolver.java:119) at org.apache.geronimo.mavenplugins.osgi.VerifyManifestMojo.execute(VerifyManifestMojo.java:101) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5396) java.util.logging resources doesn't get picked up
java.util.logging resources doesn't get picked up
-
Key: GERONIMO-5396
URL: https://issues.apache.org/jira/browse/GERONIMO-5396
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Components: Logging
Affects Versions: 3.0-M1
Reporter: Mark Struberg
In OpenWebBeans we use the i18n resource capabilities of
java.util.logging.Logger
In the code:
{noformat}
Logger logger = Logger#getLogger(String name, String resourceBundleName);
logger.info("INFO_0004", param),
{noformat}
In the Message resources:
{noformat}
INFO_0004=Adding OpenWebBeansPlugin \: [{0}]
{noformat}
Where {0} gets filled with the value of 'param'.
In geronimo I only see: "[BeansDeployer] INFO_0004"
, so the jul to slf4j bridge doesn't handle the message bundle.
Also if I add the String myself and call
{noformat}
logger.info("message with param {0}", "rabbit");
{noformat}
I still get no parameter filling, so the resulting text in the logfile is
"message with param {0}"
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5392) invalid OSGi bundle number causes geronimo to blow up
[ https://issues.apache.org/jira/browse/GERONIMO-5392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12881295#action_12881295 ] Mark Struberg commented on GERONIMO-5392: - oh yes, forgot to add: this happens after I shutdown geronimo (after installing some libs) and try to restart it. > invalid OSGi bundle number causes geronimo to blow up > - > > Key: GERONIMO-5392 > URL: https://issues.apache.org/jira/browse/GERONIMO-5392 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: Aries >Affects Versions: 3.0-M1 >Reporter: Mark Struberg > > not sure which bundle I imported to cause this problem but version parsing > seems to have a problem in geronimo: > 2010-06-22 20:43:55,582 ERROR [GBeanInstanceState] Error while starting; > GBean is now in the FAILED state: > abstractName="org.apache.geronimo.framework/j2ee-system/3.0-M1/car?ServiceModule=org.apache.geronimo.framework/j2ee-system/3.0-M1/car,j2eeType=GBean,name=GeronimoOBR" > java.lang.NumberFormatException: For input string: "1-SNAPSHOT" > at > java.lang.NumberFormatException.forInputString(NumberFormatException.java:48) > at java.lang.Integer.parseInt(Integer.java:458) > at java.lang.Integer.parseInt(Integer.java:499) > at org.osgi.framework.Version.(Version.java:133) > at > org.apache.xbean.osgi.bundle.util.VersionRange.parse(VersionRange.java:79) > at > org.apache.xbean.osgi.bundle.util.BundleDescription.getVersionRange(BundleDescription.java:192) > at > org.apache.xbean.osgi.bundle.util.BundleDescription.access$000(BundleDescription.java:36) > at > org.apache.xbean.osgi.bundle.util.BundleDescription$RequireBundle.(BundleDescription.java:299) > at > org.apache.xbean.osgi.bundle.util.BundleDescription.getRequireBundle(BundleDescription.java:113) > at > org.apache.geronimo.obr.ResourceBuilder.convertRequireBundleToRequirement(ResourceBuilder.java:108) > at > org.apache.geronimo.obr.ResourceBuilder.createResource(ResourceBuilder.java:56) > at > org.apache.geronimo.obr.GeronimoOBRGBean.generateOBRModel(GeronimoOBRGBean.java:140) > at > org.apache.geronimo.obr.GeronimoOBRGBean.generateOBR(GeronimoOBRGBean.java:96) > at > org.apache.geronimo.obr.GeronimoOBRGBean.generateOBR(GeronimoOBRGBean.java:92) > at > org.apache.geronimo.obr.GeronimoOBRGBean.doStart(GeronimoOBRGBean.java:172) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:959) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:269) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:103) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:125) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:544) > at > org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:386) > at > org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:461) > at > org.apache.geronimo.kernel.config.ConfigurationUtil.loadBootstrapConfiguration(ConfigurationUtil.java:216) > at > org.apache.geronimo.system.osgi.BootActivator.start(BootActivator.java:70) > at > org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:661) > at org.apache.felix.framework.Felix.activateBundle(Felix.java:1760) > at org.apache.felix.framework.Felix.startBundle(Felix.java:1682) > at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1128) > at > org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:264) > at java.lang.Thread.run(Thread.java:619) > ERROR: Error starting > mvn:org.apache.geronimo.framework/j2ee-system/3.0-M1/car > (org.osgi.framework.BundleException: Activator start error in bundle > org.apache.geronimo.framework.j2ee-system [55].) > org.apache.geronimo.kernel.config.InvalidConfigException: Unknown start > exception > at > org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:523) > at > org.apache.geronimo.kernel.config.ConfigurationUtil.loadBootstrapConfiguration(ConfigurationUtil.java:216) > at > org.apache.geronimo.system.osgi.BootActivator.start(BootActivator.java:70) > at > org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:661) > at org.apache.felix.framework.Felix.activateBundle(Felix.java:1760) > at org.apache.felix.framework.Felix.startBundle(Felix.java:1682) > at org.apache.felix.framework.Felix.setActiveStartLevel(Felix
[jira] Created: (GERONIMO-5392) invalid OSGi bundle number causes geronimo to blow up
invalid OSGi bundle number causes geronimo to blow up - Key: GERONIMO-5392 URL: https://issues.apache.org/jira/browse/GERONIMO-5392 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: Aries Affects Versions: 3.0-M1 Reporter: Mark Struberg not sure which bundle I imported to cause this problem but version parsing seems to have a problem in geronimo: 2010-06-22 20:43:55,582 ERROR [GBeanInstanceState] Error while starting; GBean is now in the FAILED state: abstractName="org.apache.geronimo.framework/j2ee-system/3.0-M1/car?ServiceModule=org.apache.geronimo.framework/j2ee-system/3.0-M1/car,j2eeType=GBean,name=GeronimoOBR" java.lang.NumberFormatException: For input string: "1-SNAPSHOT" at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48) at java.lang.Integer.parseInt(Integer.java:458) at java.lang.Integer.parseInt(Integer.java:499) at org.osgi.framework.Version.(Version.java:133) at org.apache.xbean.osgi.bundle.util.VersionRange.parse(VersionRange.java:79) at org.apache.xbean.osgi.bundle.util.BundleDescription.getVersionRange(BundleDescription.java:192) at org.apache.xbean.osgi.bundle.util.BundleDescription.access$000(BundleDescription.java:36) at org.apache.xbean.osgi.bundle.util.BundleDescription$RequireBundle.(BundleDescription.java:299) at org.apache.xbean.osgi.bundle.util.BundleDescription.getRequireBundle(BundleDescription.java:113) at org.apache.geronimo.obr.ResourceBuilder.convertRequireBundleToRequirement(ResourceBuilder.java:108) at org.apache.geronimo.obr.ResourceBuilder.createResource(ResourceBuilder.java:56) at org.apache.geronimo.obr.GeronimoOBRGBean.generateOBRModel(GeronimoOBRGBean.java:140) at org.apache.geronimo.obr.GeronimoOBRGBean.generateOBR(GeronimoOBRGBean.java:96) at org.apache.geronimo.obr.GeronimoOBRGBean.generateOBR(GeronimoOBRGBean.java:92) at org.apache.geronimo.obr.GeronimoOBRGBean.doStart(GeronimoOBRGBean.java:172) at org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:959) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:269) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:103) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:125) at org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:544) at org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:386) at org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:461) at org.apache.geronimo.kernel.config.ConfigurationUtil.loadBootstrapConfiguration(ConfigurationUtil.java:216) at org.apache.geronimo.system.osgi.BootActivator.start(BootActivator.java:70) at org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:661) at org.apache.felix.framework.Felix.activateBundle(Felix.java:1760) at org.apache.felix.framework.Felix.startBundle(Felix.java:1682) at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1128) at org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:264) at java.lang.Thread.run(Thread.java:619) ERROR: Error starting mvn:org.apache.geronimo.framework/j2ee-system/3.0-M1/car (org.osgi.framework.BundleException: Activator start error in bundle org.apache.geronimo.framework.j2ee-system [55].) org.apache.geronimo.kernel.config.InvalidConfigException: Unknown start exception at org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:523) at org.apache.geronimo.kernel.config.ConfigurationUtil.loadBootstrapConfiguration(ConfigurationUtil.java:216) at org.apache.geronimo.system.osgi.BootActivator.start(BootActivator.java:70) at org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:661) at org.apache.felix.framework.Felix.activateBundle(Felix.java:1760) at org.apache.felix.framework.Felix.startBundle(Felix.java:1682) at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1128) at org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:264) at java.lang.Thread.run(Thread.java:619) Caused by: org.apache.geronimo.gbean.InvalidConfigurationException: Configuration org.apache.geronimo.framework/j2ee-system/3.0-M1/car failed to start due to the following reasons: The service ServiceModule=org.apache.geronimo.framework/j2ee-system/3.0-M1/car,j2eeType=GBean,name=GeronimoOBR did not start because For in
[jira] Updated: (GERONIMO-5014) JSR-303 api needs to update the ElementDescriptor section to fit the latest spec
[ https://issues.apache.org/jira/browse/GERONIMO-5014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated GERONIMO-5014: Attachment: GERONIMO-5014.patch > JSR-303 api needs to update the ElementDescriptor section to fit the latest > spec > > > Key: GERONIMO-5014 > URL: https://issues.apache.org/jira/browse/GERONIMO-5014 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: specs >Reporter: Mark Struberg > Attachments: GERONIMO-5014.patch > > > there have been a few changes in the spec. > I made all changes to make agimatec-validator (which currently uses the RI) > compile against our spec api. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5014) JSR-303 api needs to update the ElementDescriptor section to fit the latest spec
JSR-303 api needs to update the ElementDescriptor section to fit the latest spec Key: GERONIMO-5014 URL: https://issues.apache.org/jira/browse/GERONIMO-5014 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: specs Reporter: Mark Struberg there have been a few changes in the spec. I made all changes to make agimatec-validator (which currently uses the RI) compile against our spec api. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
