date:20180516

Re: completely weird unit test failure

2018-05-16 Thread Romain Manni-Bucau

Did you rebuild bval 2 too?

Le jeu. 17 mai 2018 00:39, Matthew Broadhead 
a écrit :

> i pulled and it is still failing one
>
> INFO - Deployed
>
> Application(path=/home/matthew/git/tomee/server/openejb-cxf-rs/ProviderWithoutAnnotationTest)
> WARNING - Interceptor for
> {http://rs.cxf.server.openejb.apache.org/}Endpoint has thrown exception,
> unwinding now
> java.util.MissingFormatArgumentException: Format specifier '%s'
>  at java.util.Formatter.format(Formatter.java:2519)
>  at java.util.Formatter.format(Formatter.java:2455)
>  at java.lang.String.format(String.java:2940)
>  at org.apache.bval.util.Exceptions.lambda$create$0(Exceptions.java:44)
>  at org.apache.bval.util.Exceptions.create(Exceptions.java:53)
>  at org.apache.bval.util.Exceptions.create(Exceptions.java:44)
>  at org.apache.bval.util.Exceptions.raise(Exceptions.java:63)
>  at org.apache.bval.util.Exceptions.raiseIf(Exceptions.java:69)
>  at org.apache.bval.util.Exceptions.raiseUnless(Exceptions.java:75)
>  at org.apache.bval.util.Validate.isTrue(Validate.java:43)
>
> [INFO] OpenEJB :: Server :: CXF RS  FAILURE
> [02:17 min]
>
>
>
> On 16/05/18 23:15, Romain Manni-Bucau wrote:
> > fixed (the message issue, the underlying bval@getter issue + the cxf
> > validation issue), you need bval  (bval2 branch) snapshot and tomee
> > fb_tomee8 branch snapshot to get it
> >
> > Romain Manni-Bucau
> > @rmannibucau  |  Blog
> >  | Old Blog
> >  | Github <
> https://github.com/rmannibucau> |
> > LinkedIn  | Book
> > <
> https://www.packtpub.com/application-development/java-ee-8-high-performance
> >
> >
> >
> > Le mer. 16 mai 2018 à 20:07, Matthew Broadhead <
> > matthew.broadh...@nbmlaw.co.uk> a écrit :
> >
> >> [INFO] OpenEJB :: Server :: CXF RS
> >>
> >> WARNING - Interceptor for
> >> {http://johnzon.rs.cxf.server.openejb.apache.org/}Endpoint has thrown
> >> exception, unwinding now
> >> java.util.MissingFormatArgumentException: Format specifier '%s'
> >>
> >> SEVERE - can't instantiate
> >> org.apache.openejb.server.cxf.rs.AppPropertiesPropagationTest$Writer
> >> java.lang.InstantiationException:
> >> org.apache.openejb.server.cxf.rs.AppPropertiesPropagationTest$Writer
> >>
> >> SEVERE - EjbTransactionUtil.handleSystemException: null
> >> org.apache.openejb.server.cxf.rs.CustomExceptionMapperTest$FooException
> >>
> >> WARNING - Interceptor for {http://rs.cxf.server.openejb.apache.org/}En
> >> has thrown exception, unwinding now
> >> java.lang.IllegalArgumentException:
> >> org.apache.openejb.server.cxf.rs.JSonStreamingOutputTest$En$1@3b4ce8d6
> >> is not an instance of class javax.ws.rs.core.Response
> >>   at
> >>
> >>
> org.apache.bval.jsr.job.ValidateReturnValue.(ValidateReturnValue.java:123)
> >>
> >> these are some of the fails i get on mvn clean install.  although my
> >> terminal cuts off output over a certain level
> >>
> >> On 16/05/18 17:35, Mark Struberg wrote:
> >>> In which module do you get the error?
> >>> Will try to later share my build results.
> >>>
> >>> LieGrue,
> >>> strub
> >>>
>  Am 16.05.2018 um 13:51 schrieb Matthew Broadhead <
> >> matthew.broadh...@nbmlaw.co.uk>:
>  if i try to compile fb_tomee8 i get
> 
>  WARNING - Interceptor for {
> http://rs.cxf.server.openejb.apache.org/}En
> >> has thrown exception, unwinding now
>  java.lang.IllegalArgumentException:
> >> org.apache.openejb.server.cxf.rs.JSonStreamingOutputTest$En$1@69762669
> is
> >> not an instance of class javax.ws.rs.core.Response
>    at
> >>
> org.apache.bval.jsr.job.ValidateReturnValue.(ValidateReturnValue.java:123)
> 
>  On 15/05/18 23:16, Mark Struberg wrote:
> >fb_tomee8
> > I've fixed this now by fixing the broken bean. Wonder how this could
> >> have ever worked.Might also be partly random due to different build
> order?
> > But now I'm off to the next bug.
> > EarModuleNamesTest
> > This one also scans for a resource due to haing the
> >> openejb-itests-beans on the classpath.But since the config is done
> manually
> >> it misses the TxMgr setup, which is null.
> > I exclude this test for now and want to see how far I come with the
> >> other tests.
> > LieGrue,strub
> >
> >   On Tuesday, 15 May 2018, 22:03:03 CEST, Jonathan Gallimore <
> >> jonathan.gallim...@gmail.com> wrote:
> >  Which branch?
> >
> > Jon
> >
> > On Tue, May 15, 2018 at 9:51 PM, Mark Struberg
> >> 
> > wrote:
> >
> >> Well, this looks weird anyhow
> >> @Stateless
> >> public class AnnotatedFieldInjectionStatefulBean {
> >>
> >> compare the name and the annotation
> >> And the additional error messages
> >> are:org.apache.openejb.config.ValidationWarning:
> >> @Init is

Re: Example request

2018-05-16 Thread Romain Manni-Bucau

Hi

Add a conf/exclusions.list file with this content (assuming tibco- is a
common prefix of tibco jars):

default-list
tibco-

Le jeu. 17 mai 2018 02:41, Lakshmikanth W  a écrit :

> Are there any particular settings to integrate tibco with tomee plus?
> I am seeing below error while tomee starting. I have added necessary
> tibco jars to lib folder.
>
> java.lang.Exception: Could not load com.tibco.security.ssl.String.class
> at
> org.apache.openejb.util.AnnotationFinder.readClassDef(AnnotationFinder.java:305)
> at
> org.apache.openejb.util.AnnotationFinder.find(AnnotationFinder.java:164)
> at
> org.apache.openejb.config.DeploymentLoader.checkAnnotations(DeploymentLoader.java:2088)
> at
> org.apache.openejb.config.DeploymentLoader.discoverModuleType(DeploymentLoader.java:1971)
> at
> org.apache.openejb.config.DeploymentsResolver.processUrls(DeploymentsResolver.java:361)
> at
> org.apache.openejb.config.DeploymentsResolver.loadFromClasspath(DeploymentsResolver.java:257)
> at
> org.apache.openejb.config.DeploymentsResolver.loadFromClasspath(DeploymentsResolver.java:322)
> at
> org.apache.openejb.config.DeploymentLoader.createAppModule(DeploymentLoader.java:648)
> at
> org.apache.openejb.config.DeploymentLoader.load(DeploymentLoader.java:168)
> at
> org.apache.openejb.config.ConfigurationFactory.configureApplication(ConfigurationFactory.java:855)
> at
> org.apache.openejb.config.ConfigurationFactory.getOpenEjbConfiguration(ConfigurationFactory.java:547)
> at
> org.apache.openejb.config.ConfigurationFactory.getOpenEjbConfiguration(ConfigurationFactory.java:634)
> at
> org.apache.openejb.assembler.classic.Assembler.getOpenEjbConfiguration(Assembler.java:507)
> at
> org.apache.openejb.assembler.classic.Assembler.build(Assembler.java:486)
> at org.apache.openejb.OpenEJB$Instance.(OpenEJB.java:150)
> at org.apache.openejb.OpenEJB.init(OpenEJB.java:307)
> at
> org.apache.tomee.catalina.TomcatLoader.initialize(TomcatLoader.java:247)
> at
> org.apache.tomee.catalina.ServerListener.lifecycleEvent(ServerListener.java:168)
> at
> org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:94)
> at
> org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:395)
> at
> org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:108)
> at org.apache.catalina.startup.Catalina.load(Catalina.java:607)
> at org.apache.catalina.startup.Catalina.load(Catalina.java:630)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:311)
> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:494)
>
> Thanks,
> Laks
>

Example request

2018-05-16 Thread Lakshmikanth W

Are there any particular settings to integrate tibco with tomee plus?
I am seeing below error while tomee starting. I have added necessary
tibco jars to lib folder.

java.lang.Exception: Could not load com.tibco.security.ssl.String.class
at 
org.apache.openejb.util.AnnotationFinder.readClassDef(AnnotationFinder.java:305)
at 
org.apache.openejb.util.AnnotationFinder.find(AnnotationFinder.java:164)
at 
org.apache.openejb.config.DeploymentLoader.checkAnnotations(DeploymentLoader.java:2088)
at 
org.apache.openejb.config.DeploymentLoader.discoverModuleType(DeploymentLoader.java:1971)
at 
org.apache.openejb.config.DeploymentsResolver.processUrls(DeploymentsResolver.java:361)
at 
org.apache.openejb.config.DeploymentsResolver.loadFromClasspath(DeploymentsResolver.java:257)
at 
org.apache.openejb.config.DeploymentsResolver.loadFromClasspath(DeploymentsResolver.java:322)
at 
org.apache.openejb.config.DeploymentLoader.createAppModule(DeploymentLoader.java:648)
at 
org.apache.openejb.config.DeploymentLoader.load(DeploymentLoader.java:168)
at 
org.apache.openejb.config.ConfigurationFactory.configureApplication(ConfigurationFactory.java:855)
at 
org.apache.openejb.config.ConfigurationFactory.getOpenEjbConfiguration(ConfigurationFactory.java:547)
at 
org.apache.openejb.config.ConfigurationFactory.getOpenEjbConfiguration(ConfigurationFactory.java:634)
at 
org.apache.openejb.assembler.classic.Assembler.getOpenEjbConfiguration(Assembler.java:507)
at 
org.apache.openejb.assembler.classic.Assembler.build(Assembler.java:486)
at org.apache.openejb.OpenEJB$Instance.(OpenEJB.java:150)
at org.apache.openejb.OpenEJB.init(OpenEJB.java:307)
at 
org.apache.tomee.catalina.TomcatLoader.initialize(TomcatLoader.java:247)
at 
org.apache.tomee.catalina.ServerListener.lifecycleEvent(ServerListener.java:168)
at 
org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:94)
at 
org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:395)
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:108)
at org.apache.catalina.startup.Catalina.load(Catalina.java:607)
at org.apache.catalina.startup.Catalina.load(Catalina.java:630)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:311)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:494)

Thanks,
Laks

Re: completely weird unit test failure

2018-05-16 Thread Matthew Broadhead


i pulled and it is still failing one

INFO - Deployed 
Application(path=/home/matthew/git/tomee/server/openejb-cxf-rs/ProviderWithoutAnnotationTest)
WARNING - Interceptor for 
{http://rs.cxf.server.openejb.apache.org/}Endpoint has thrown exception, 
unwinding now

java.util.MissingFormatArgumentException: Format specifier '%s'
    at java.util.Formatter.format(Formatter.java:2519)
    at java.util.Formatter.format(Formatter.java:2455)
    at java.lang.String.format(String.java:2940)
    at org.apache.bval.util.Exceptions.lambda$create$0(Exceptions.java:44)
    at org.apache.bval.util.Exceptions.create(Exceptions.java:53)
    at org.apache.bval.util.Exceptions.create(Exceptions.java:44)
    at org.apache.bval.util.Exceptions.raise(Exceptions.java:63)
    at org.apache.bval.util.Exceptions.raiseIf(Exceptions.java:69)
    at org.apache.bval.util.Exceptions.raiseUnless(Exceptions.java:75)
    at org.apache.bval.util.Validate.isTrue(Validate.java:43)

[INFO] OpenEJB :: Server :: CXF RS  FAILURE 
[02:17 min]




On 16/05/18 23:15, Romain Manni-Bucau wrote:

fixed (the message issue, the underlying bval@getter issue + the cxf
validation issue), you need bval  (bval2 branch) snapshot and tomee
fb_tomee8 branch snapshot to get it

Romain Manni-Bucau
@rmannibucau  |  Blog
 | Old Blog
 | Github  |
LinkedIn  | Book



Le mer. 16 mai 2018 à 20:07, Matthew Broadhead <
matthew.broadh...@nbmlaw.co.uk> a écrit :


[INFO] OpenEJB :: Server :: CXF RS

WARNING - Interceptor for
{http://johnzon.rs.cxf.server.openejb.apache.org/}Endpoint has thrown
exception, unwinding now
java.util.MissingFormatArgumentException: Format specifier '%s'

SEVERE - can't instantiate
org.apache.openejb.server.cxf.rs.AppPropertiesPropagationTest$Writer
java.lang.InstantiationException:
org.apache.openejb.server.cxf.rs.AppPropertiesPropagationTest$Writer

SEVERE - EjbTransactionUtil.handleSystemException: null
org.apache.openejb.server.cxf.rs.CustomExceptionMapperTest$FooException

WARNING - Interceptor for {http://rs.cxf.server.openejb.apache.org/}En
has thrown exception, unwinding now
java.lang.IllegalArgumentException:
org.apache.openejb.server.cxf.rs.JSonStreamingOutputTest$En$1@3b4ce8d6
is not an instance of class javax.ws.rs.core.Response
  at

org.apache.bval.jsr.job.ValidateReturnValue.(ValidateReturnValue.java:123)

these are some of the fails i get on mvn clean install.  although my
terminal cuts off output over a certain level

On 16/05/18 17:35, Mark Struberg wrote:

In which module do you get the error?
Will try to later share my build results.

LieGrue,
strub


Am 16.05.2018 um 13:51 schrieb Matthew Broadhead <

matthew.broadh...@nbmlaw.co.uk>:

if i try to compile fb_tomee8 i get

WARNING - Interceptor for {http://rs.cxf.server.openejb.apache.org/}En

has thrown exception, unwinding now

java.lang.IllegalArgumentException:

org.apache.openejb.server.cxf.rs.JSonStreamingOutputTest$En$1@69762669 is
not an instance of class javax.ws.rs.core.Response

  at

org.apache.bval.jsr.job.ValidateReturnValue.(ValidateReturnValue.java:123)


On 15/05/18 23:16, Mark Struberg wrote:

   fb_tomee8
I've fixed this now by fixing the broken bean. Wonder how this could

have ever worked.Might also be partly random due to different build order?

But now I'm off to the next bug.
EarModuleNamesTest
This one also scans for a resource due to haing the

openejb-itests-beans on the classpath.But since the config is done manually
it misses the TxMgr setup, which is null.

I exclude this test for now and want to see how far I come with the

other tests.

LieGrue,strub

  On Tuesday, 15 May 2018, 22:03:03 CEST, Jonathan Gallimore <

jonathan.gallim...@gmail.com> wrote:

 Which branch?

Jon

On Tue, May 15, 2018 at 9:51 PM, Mark Struberg



wrote:


Well, this looks weird anyhow
@Stateless
public class AnnotatedFieldInjectionStatefulBean {

compare the name and the annotation
And the additional error messages

are:org.apache.openejb.config.ValidationWarning:

@Init is ignored for beans of type Stateless.  Class:
org.apache.openejb.test.stateful.AnnotatedFieldInjectionStatefulBean
Method: create"
"org.apache.openejb.config.ValidationWarning: @Remove is ignored for
beans of type Stateless.  Class: org.apache.openejb.test.stateful.
AnnotatedFieldInjectionStatefulBean Method: remove""

Well, yes, true!
Is this a negative test bean? ^^

  On Tuesday, 15 May 2018, 21:48:26 CEST, Mark Struberg
 wrote:

hi folks!
I get 2 unit test failures which look completely weird to me.Plus they
pass in the IDE but fail in mvn.
ERROR] Failures:
[ERROR]  CheckDescriptorLocationTest.testWarWithDescriptorInMetaInf

Keys

do not

Re: completely weird unit test failure

2018-05-16 Thread Romain Manni-Bucau

fixed (the message issue, the underlying bval@getter issue + the cxf
validation issue), you need bval  (bval2 branch) snapshot and tomee
fb_tomee8 branch snapshot to get it

Romain Manni-Bucau
@rmannibucau  |  Blog
 | Old Blog
 | Github  |
LinkedIn  | Book



Le mer. 16 mai 2018 à 20:07, Matthew Broadhead <
matthew.broadh...@nbmlaw.co.uk> a écrit :

> [INFO] OpenEJB :: Server :: CXF RS
>
> WARNING - Interceptor for
> {http://johnzon.rs.cxf.server.openejb.apache.org/}Endpoint has thrown
> exception, unwinding now
> java.util.MissingFormatArgumentException: Format specifier '%s'
>
> SEVERE - can't instantiate
> org.apache.openejb.server.cxf.rs.AppPropertiesPropagationTest$Writer
> java.lang.InstantiationException:
> org.apache.openejb.server.cxf.rs.AppPropertiesPropagationTest$Writer
>
> SEVERE - EjbTransactionUtil.handleSystemException: null
> org.apache.openejb.server.cxf.rs.CustomExceptionMapperTest$FooException
>
> WARNING - Interceptor for {http://rs.cxf.server.openejb.apache.org/}En
> has thrown exception, unwinding now
> java.lang.IllegalArgumentException:
> org.apache.openejb.server.cxf.rs.JSonStreamingOutputTest$En$1@3b4ce8d6
> is not an instance of class javax.ws.rs.core.Response
>  at
>
> org.apache.bval.jsr.job.ValidateReturnValue.(ValidateReturnValue.java:123)
>
> these are some of the fails i get on mvn clean install.  although my
> terminal cuts off output over a certain level
>
> On 16/05/18 17:35, Mark Struberg wrote:
> > In which module do you get the error?
> > Will try to later share my build results.
> >
> > LieGrue,
> > strub
> >
> >> Am 16.05.2018 um 13:51 schrieb Matthew Broadhead <
> matthew.broadh...@nbmlaw.co.uk>:
> >>
> >> if i try to compile fb_tomee8 i get
> >>
> >> WARNING - Interceptor for {http://rs.cxf.server.openejb.apache.org/}En
> has thrown exception, unwinding now
> >> java.lang.IllegalArgumentException:
> org.apache.openejb.server.cxf.rs.JSonStreamingOutputTest$En$1@69762669 is
> not an instance of class javax.ws.rs.core.Response
> >>  at
> org.apache.bval.jsr.job.ValidateReturnValue.(ValidateReturnValue.java:123)
> >>
> >>
> >> On 15/05/18 23:16, Mark Struberg wrote:
> >>>   fb_tomee8
> >>> I've fixed this now by fixing the broken bean. Wonder how this could
> have ever worked.Might also be partly random due to different build order?
> >>>
> >>> But now I'm off to the next bug.
> >>> EarModuleNamesTest
> >>> This one also scans for a resource due to haing the
> openejb-itests-beans on the classpath.But since the config is done manually
> it misses the TxMgr setup, which is null.
> >>> I exclude this test for now and want to see how far I come with the
> other tests.
> >>> LieGrue,strub
> >>>
> >>>  On Tuesday, 15 May 2018, 22:03:03 CEST, Jonathan Gallimore <
> jonathan.gallim...@gmail.com> wrote:
> >>> Which branch?
> >>>
> >>> Jon
> >>>
> >>> On Tue, May 15, 2018 at 9:51 PM, Mark Struberg
> 
> >>> wrote:
> >>>
> Well, this looks weird anyhow
>  @Stateless
>  public class AnnotatedFieldInjectionStatefulBean {
> 
>  compare the name and the annotation
>  And the additional error messages
> are:org.apache.openejb.config.ValidationWarning:
>  @Init is ignored for beans of type Stateless.  Class:
>  org.apache.openejb.test.stateful.AnnotatedFieldInjectionStatefulBean
>  Method: create"
>  "org.apache.openejb.config.ValidationWarning: @Remove is ignored for
>  beans of type Stateless.  Class: org.apache.openejb.test.stateful.
>  AnnotatedFieldInjectionStatefulBean Method: remove""
> 
>  Well, yes, true!
>  Is this a negative test bean? ^^
> 
>   On Tuesday, 15 May 2018, 21:48:26 CEST, Mark Struberg
>   wrote:
> 
> hi folks!
>  I get 2 unit test failures which look completely weird to me.Plus they
>  pass in the IDE but fail in mvn.
>  ERROR] Failures:
>  [ERROR]  CheckDescriptorLocationTest.testWarWithDescriptorInMetaInf
> Keys
>  do not match expected:<...or.incorrectLocation[]> but
>  was:<...or.incorrectLocation[
>  ignoredMethodAnnotation
>  ignoredMethodAnnotation]>
>  [ERROR]  CheckDescriptorLocationTest.testWarWithDescriptorInRoot Keys
> do
>  not match expected:<...or.incorrectLocation[]> but
>  was:<...or.incorrectLocation[
>  ignoredMethodAnnotation
>  ignoredMethodAnnotation]>
> 
> 
>  The unit test in question is
>  org.apache.openejb.config.CheckDescriptorLocationTest#
>  testWarWithDescriptorInRoot
>  This bundles a single FooBean.class with a single error.We get this
> error,
>  but also a few other test failures which apparently should not happen.
>  Those come

Re: completely weird unit test failure

2018-05-16 Thread Matthew Broadhead


[INFO] OpenEJB :: Server :: CXF RS

WARNING - Interceptor for 
{http://johnzon.rs.cxf.server.openejb.apache.org/}Endpoint has thrown 
exception, unwinding now

java.util.MissingFormatArgumentException: Format specifier '%s'

SEVERE - can't instantiate 
org.apache.openejb.server.cxf.rs.AppPropertiesPropagationTest$Writer
java.lang.InstantiationException: 
org.apache.openejb.server.cxf.rs.AppPropertiesPropagationTest$Writer


SEVERE - EjbTransactionUtil.handleSystemException: null
org.apache.openejb.server.cxf.rs.CustomExceptionMapperTest$FooException

WARNING - Interceptor for {http://rs.cxf.server.openejb.apache.org/}En 
has thrown exception, unwinding now
java.lang.IllegalArgumentException: 
org.apache.openejb.server.cxf.rs.JSonStreamingOutputTest$En$1@3b4ce8d6 
is not an instance of class javax.ws.rs.core.Response
    at 
org.apache.bval.jsr.job.ValidateReturnValue.(ValidateReturnValue.java:123)


these are some of the fails i get on mvn clean install.  although my 
terminal cuts off output over a certain level


On 16/05/18 17:35, Mark Struberg wrote:

In which module do you get the error?
Will try to later share my build results.

LieGrue,
strub


Am 16.05.2018 um 13:51 schrieb Matthew Broadhead 
:

if i try to compile fb_tomee8 i get

WARNING - Interceptor for {http://rs.cxf.server.openejb.apache.org/}En has 
thrown exception, unwinding now
java.lang.IllegalArgumentException: 
org.apache.openejb.server.cxf.rs.JSonStreamingOutputTest$En$1@69762669 is not 
an instance of class javax.ws.rs.core.Response
 at 
org.apache.bval.jsr.job.ValidateReturnValue.(ValidateReturnValue.java:123)


On 15/05/18 23:16, Mark Struberg wrote:

  fb_tomee8
I've fixed this now by fixing the broken bean. Wonder how this could have ever 
worked.Might also be partly random due to different build order?

But now I'm off to the next bug.
EarModuleNamesTest
This one also scans for a resource due to haing the openejb-itests-beans on the 
classpath.But since the config is done manually it misses the TxMgr setup, 
which is null.
I exclude this test for now and want to see how far I come with the other tests.
LieGrue,strub

 On Tuesday, 15 May 2018, 22:03:03 CEST, Jonathan Gallimore 
 wrote:
Which branch?

Jon

On Tue, May 15, 2018 at 9:51 PM, Mark Struberg 
wrote:


   Well, this looks weird anyhow
@Stateless
public class AnnotatedFieldInjectionStatefulBean {

compare the name and the annotation
And the additional error messages 
are:org.apache.openejb.config.ValidationWarning:
@Init is ignored for beans of type Stateless.  Class:
org.apache.openejb.test.stateful.AnnotatedFieldInjectionStatefulBean
Method: create"
"org.apache.openejb.config.ValidationWarning: @Remove is ignored for
beans of type Stateless.  Class: org.apache.openejb.test.stateful.
AnnotatedFieldInjectionStatefulBean Method: remove""

Well, yes, true!
Is this a negative test bean? ^^

 On Tuesday, 15 May 2018, 21:48:26 CEST, Mark Struberg
 wrote:

   hi folks!
I get 2 unit test failures which look completely weird to me.Plus they
pass in the IDE but fail in mvn.
ERROR] Failures:
[ERROR]  CheckDescriptorLocationTest.testWarWithDescriptorInMetaInf Keys
do not match expected:<...or.incorrectLocation[]> but
was:<...or.incorrectLocation[
ignoredMethodAnnotation
ignoredMethodAnnotation]>
[ERROR]  CheckDescriptorLocationTest.testWarWithDescriptorInRoot Keys do
not match expected:<...or.incorrectLocation[]> but
was:<...or.incorrectLocation[
ignoredMethodAnnotation
ignoredMethodAnnotation]>


The unit test in question is
org.apache.openejb.config.CheckDescriptorLocationTest#
testWarWithDescriptorInRoot
This bundles a single FooBean.class with a single error.We get this error,
but also a few other test failures which apparently should not happen.
Those come from beans in transitive dependency projects like
openejb-itests-beans.
It passes in my IDE since there the classpath is different...
Any idea what happened?
LieGrue,strub

Re: completely weird unit test failure

2018-05-16 Thread Mark Struberg

In which module do you get the error?
Will try to later share my build results.

LieGrue,
strub

> Am 16.05.2018 um 13:51 schrieb Matthew Broadhead 
> :
> 
> if i try to compile fb_tomee8 i get
> 
> WARNING - Interceptor for {http://rs.cxf.server.openejb.apache.org/}En has 
> thrown exception, unwinding now
> java.lang.IllegalArgumentException: 
> org.apache.openejb.server.cxf.rs.JSonStreamingOutputTest$En$1@69762669 is not 
> an instance of class javax.ws.rs.core.Response
> at 
> org.apache.bval.jsr.job.ValidateReturnValue.(ValidateReturnValue.java:123)
> 
> 
> On 15/05/18 23:16, Mark Struberg wrote:
>>  fb_tomee8
>> I've fixed this now by fixing the broken bean. Wonder how this could have 
>> ever worked.Might also be partly random due to different build order?
>> 
>> But now I'm off to the next bug.
>> EarModuleNamesTest
>> This one also scans for a resource due to haing the openejb-itests-beans on 
>> the classpath.But since the config is done manually it misses the TxMgr 
>> setup, which is null.
>> I exclude this test for now and want to see how far I come with the other 
>> tests.
>> LieGrue,strub
>> 
>> On Tuesday, 15 May 2018, 22:03:03 CEST, Jonathan Gallimore 
>>  wrote:
>>Which branch?
>> 
>> Jon
>> 
>> On Tue, May 15, 2018 at 9:51 PM, Mark Struberg 
>> wrote:
>> 
>>>   Well, this looks weird anyhow
>>> @Stateless
>>> public class AnnotatedFieldInjectionStatefulBean {
>>> 
>>> compare the name and the annotation
>>> And the additional error messages 
>>> are:org.apache.openejb.config.ValidationWarning:
>>> @Init is ignored for beans of type Stateless.  Class:
>>> org.apache.openejb.test.stateful.AnnotatedFieldInjectionStatefulBean
>>> Method: create"
>>> "org.apache.openejb.config.ValidationWarning: @Remove is ignored for
>>> beans of type Stateless.  Class: org.apache.openejb.test.stateful.
>>> AnnotatedFieldInjectionStatefulBean Method: remove""
>>> 
>>> Well, yes, true!
>>> Is this a negative test bean? ^^
>>> 
>>> On Tuesday, 15 May 2018, 21:48:26 CEST, Mark Struberg
>>>  wrote:
>>> 
>>>   hi folks!
>>> I get 2 unit test failures which look completely weird to me.Plus they
>>> pass in the IDE but fail in mvn.
>>> ERROR] Failures:
>>> [ERROR]  CheckDescriptorLocationTest.testWarWithDescriptorInMetaInf Keys
>>> do not match expected:<...or.incorrectLocation[]> but
>>> was:<...or.incorrectLocation[
>>> ignoredMethodAnnotation
>>> ignoredMethodAnnotation]>
>>> [ERROR]  CheckDescriptorLocationTest.testWarWithDescriptorInRoot Keys do
>>> not match expected:<...or.incorrectLocation[]> but
>>> was:<...or.incorrectLocation[
>>> ignoredMethodAnnotation
>>> ignoredMethodAnnotation]>
>>> 
>>> 
>>> The unit test in question is
>>> org.apache.openejb.config.CheckDescriptorLocationTest#
>>> testWarWithDescriptorInRoot
>>> This bundles a single FooBean.class with a single error.We get this error,
>>> but also a few other test failures which apparently should not happen.
>>> Those come from beans in transitive dependency projects like
>>> openejb-itests-beans.
>>> It passes in my IDE since there the classpath is different...
>>> Any idea what happened?
>>> LieGrue,strub
>>> 
>>   
>

Re: completely weird unit test failure

2018-05-16 Thread Matthew Broadhead


if i try to compile fb_tomee8 i get

WARNING - Interceptor for {http://rs.cxf.server.openejb.apache.org/}En 
has thrown exception, unwinding now
java.lang.IllegalArgumentException: 
org.apache.openejb.server.cxf.rs.JSonStreamingOutputTest$En$1@69762669 
is not an instance of class javax.ws.rs.core.Response
    at 
org.apache.bval.jsr.job.ValidateReturnValue.(ValidateReturnValue.java:123)



On 15/05/18 23:16, Mark Struberg wrote:

  fb_tomee8
I've fixed this now by fixing the broken bean. Wonder how this could have ever 
worked.Might also be partly random due to different build order?

But now I'm off to the next bug.
EarModuleNamesTest
This one also scans for a resource due to haing the openejb-itests-beans on the 
classpath.But since the config is done manually it misses the TxMgr setup, 
which is null.
I exclude this test for now and want to see how far I come with the other tests.
LieGrue,strub

 On Tuesday, 15 May 2018, 22:03:03 CEST, Jonathan Gallimore 
 wrote:
  
  Which branch?


Jon

On Tue, May 15, 2018 at 9:51 PM, Mark Struberg 
wrote:


   Well, this looks weird anyhow
@Stateless
public class AnnotatedFieldInjectionStatefulBean {

compare the name and the annotation
And the additional error messages 
are:org.apache.openejb.config.ValidationWarning:
@Init is ignored for beans of type Stateless.  Class:
org.apache.openejb.test.stateful.AnnotatedFieldInjectionStatefulBean
Method: create"
"org.apache.openejb.config.ValidationWarning: @Remove is ignored for
beans of type Stateless.  Class: org.apache.openejb.test.stateful.
AnnotatedFieldInjectionStatefulBean Method: remove""

Well, yes, true!
Is this a negative test bean? ^^

     On Tuesday, 15 May 2018, 21:48:26 CEST, Mark Struberg
 wrote:

   hi folks!
I get 2 unit test failures which look completely weird to me.Plus they
pass in the IDE but fail in mvn.
ERROR] Failures:
[ERROR]  CheckDescriptorLocationTest.testWarWithDescriptorInMetaInf Keys
do not match expected:<...or.incorrectLocation[]> but
was:<...or.incorrectLocation[
ignoredMethodAnnotation
ignoredMethodAnnotation]>
[ERROR]  CheckDescriptorLocationTest.testWarWithDescriptorInRoot Keys do
not match expected:<...or.incorrectLocation[]> but
was:<...or.incorrectLocation[
ignoredMethodAnnotation
ignoredMethodAnnotation]>


The unit test in question is
org.apache.openejb.config.CheckDescriptorLocationTest#
testWarWithDescriptorInRoot
This bundles a single FooBean.class with a single error.We get this error,
but also a few other test failures which apparently should not happen.
Those come from beans in transitive dependency projects like
openejb-itests-beans.
It passes in my IDE since there the classpath is different...
Any idea what happened?
LieGrue,strub

Re: completely weird unit test failure

2018-05-16 Thread Romain Manni-Bucau

seems due to our exclusion changes, will try to fix it now

Romain Manni-Bucau
@rmannibucau  |  Blog
 | Old Blog
 | Github  |
LinkedIn  | Book



Le mer. 16 mai 2018 à 08:44, Mark Struberg  a
écrit :

> Can you probably take a look? This is clearly beyond my foo.
>
> LieGrue,
> strub
>
>
> > Am 16.05.2018 um 07:51 schrieb Romain Manni-Bucau  >:
> >
> > That was the trick with link(), if you have the child in classloader C
> and
> > the parent in C.parent then you get the parent included. This is why i
> > think something can have been broken.
> >
> > Romain Manni-Bucau
> > @rmannibucau  |  Blog
> >  | Old Blog
> >  | Github <
> https://github.com/rmannibucau> |
> > LinkedIn  | Book
> > <
> https://www.packtpub.com/application-development/java-ee-8-high-performance
> >
> >
> >
> > Le mer. 16 mai 2018 à 07:43, Mark Struberg  a
> > écrit :
> >
> >> Yes, but the weird thing is that it comes from the parent CL, so the
> >> scanner has not too much to do with it.
> >> Btw, by excluding the Earname test I came a bit further.
> >>
> >> Now the following are failing in the RS module
> >> [ERROR] Errors:
> >> [ERROR]   ApplicationStarTest.checkStarIsNotAnIssue:43 »
> >> InternalServerError HTTP 500 In...
> >> [ERROR]   DisableTomEEJohnzonTest.client:71 » InternalServerError HTTP
> 500
> >> Internal Serv...
> >> [ERROR]   DisableTomEEJohnzonTest.server:66 » IO Server returned HTTP
> >> response code: 500...
> >> [ERROR]   JSonStreamingOutputTest.run:51 » InternalServerError HTTP 500
> >> Internal Server ...
> >> [ERROR]   ProviderWithoutAnnotationTest.run:62 » InternalServerError
> HTTP
> >> 500 Internal S...
> >> [ERROR]   TomEEConfigurableJohnzonTest.run:91 » IO Server returned HTTP
> >> response code: 5...
> >> [INFO]
> >>
> >>
> >>
> >> But this is likely to a glitch in new bval.Or due to me being de_AT
> >> located... ;)
> >> LieGrue,strub
> >>
> >>On Wednesday, 16 May 2018, 06:51:59 CEST, Romain Manni-Bucau <
> >> rmannibu...@gmail.com> wrote:
> >>
> >> Mark
> >>
> >> Previous test issue can be due to xbean upgrades or scanning changes,
> did
> >> you check that? We tend to link implicitly the finder for these tests
> but
> >> can have been broken at some point.
> >>
> >> Le mar. 15 mai 2018 23:16, Mark Struberg  a
> >> écrit :
> >>
> >>> fb_tomee8
> >>> I've fixed this now by fixing the broken bean. Wonder how this could
> have
> >>> ever worked.Might also be partly random due to different build order?
> >>>
> >>> But now I'm off to the next bug.
> >>> EarModuleNamesTest
> >>> This one also scans for a resource due to haing the
> openejb-itests-beans
> >>> on the classpath.But since the config is done manually it misses the
> >> TxMgr
> >>> setup, which is null.
> >>> I exclude this test for now and want to see how far I come with the
> other
> >>> tests.
> >>> LieGrue,strub
> >>>
> >>>   On Tuesday, 15 May 2018, 22:03:03 CEST, Jonathan Gallimore <
> >>> jonathan.gallim...@gmail.com> wrote:
> >>>
> >>> Which branch?
> >>>
> >>> Jon
> >>>
> >>> On Tue, May 15, 2018 at 9:51 PM, Mark Struberg
>  >>>
> >>> wrote:
> >>>
>  Well, this looks weird anyhow
>  @Stateless
>  public class AnnotatedFieldInjectionStatefulBean {
> 
>  compare the name and the annotation
>  And the additional error messages
> >>> are:org.apache.openejb.config.ValidationWarning:
>  @Init is ignored for beans of type Stateless.  Class:
>  org.apache.openejb.test.stateful.AnnotatedFieldInjectionStatefulBean
>  Method: create"
>  "org.apache.openejb.config.ValidationWarning: @Remove is ignored for
>  beans of type Stateless.  Class: org.apache.openejb.test.stateful.
>  AnnotatedFieldInjectionStatefulBean Method: remove""
> 
>  Well, yes, true!
>  Is this a negative test bean? ^^
> 
>    On Tuesday, 15 May 2018, 21:48:26 CEST, Mark Struberg
>   wrote:
> 
>  hi folks!
>  I get 2 unit test failures which look completely weird to me.Plus they
>  pass in the IDE but fail in mvn.
>  ERROR] Failures:
>  [ERROR]  CheckDescriptorLocationTest.testWarWithDescriptorInMetaInf
> >> Keys
>  do not match expected:<...or.incorrectLocation[]> but
>  was:<...or.incorrectLocation[
>  ignoredMethodAnnotation
>  ignoredMethodAnnotation]>
>  [ERROR]  CheckDescriptorLocationTest.testWarWithDescriptorInRoot Keys
> >> do
>  not match expected:<...or.incorrectLocation[]> but
>

MP snapshots in tomee8

2018-05-16 Thread Mark Struberg

Hi folks!

I've downgraded some microprofile versions to released artifacts. The reason is 
that the snapshots we used to have in our poms simply are not available on 
maven.central. And once e.g. mp-config 1.3 is really released we will do a 
mp-config release and then upgrade tomee8 (and 7.1 once it exists).
Until that I'd prefer to stick to the released versions and try to avoid moving 
targets.

LieGrue,
strub

Re: completely weird unit test failure

2018-05-16 Thread Mark Struberg

Can you probably take a look? This is clearly beyond my foo.

LieGrue,
strub


> Am 16.05.2018 um 07:51 schrieb Romain Manni-Bucau :
> 
> That was the trick with link(), if you have the child in classloader C and
> the parent in C.parent then you get the parent included. This is why i
> think something can have been broken.
> 
> Romain Manni-Bucau
> @rmannibucau  |  Blog
>  | Old Blog
>  | Github  |
> LinkedIn  | Book
> 
> 
> 
> Le mer. 16 mai 2018 à 07:43, Mark Struberg  a
> écrit :
> 
>> Yes, but the weird thing is that it comes from the parent CL, so the
>> scanner has not too much to do with it.
>> Btw, by excluding the Earname test I came a bit further.
>> 
>> Now the following are failing in the RS module
>> [ERROR] Errors:
>> [ERROR]   ApplicationStarTest.checkStarIsNotAnIssue:43 »
>> InternalServerError HTTP 500 In...
>> [ERROR]   DisableTomEEJohnzonTest.client:71 » InternalServerError HTTP 500
>> Internal Serv...
>> [ERROR]   DisableTomEEJohnzonTest.server:66 » IO Server returned HTTP
>> response code: 500...
>> [ERROR]   JSonStreamingOutputTest.run:51 » InternalServerError HTTP 500
>> Internal Server ...
>> [ERROR]   ProviderWithoutAnnotationTest.run:62 » InternalServerError HTTP
>> 500 Internal S...
>> [ERROR]   TomEEConfigurableJohnzonTest.run:91 » IO Server returned HTTP
>> response code: 5...
>> [INFO]
>> 
>> 
>> 
>> But this is likely to a glitch in new bval.Or due to me being de_AT
>> located... ;)
>> LieGrue,strub
>> 
>>On Wednesday, 16 May 2018, 06:51:59 CEST, Romain Manni-Bucau <
>> rmannibu...@gmail.com> wrote:
>> 
>> Mark
>> 
>> Previous test issue can be due to xbean upgrades or scanning changes, did
>> you check that? We tend to link implicitly the finder for these tests but
>> can have been broken at some point.
>> 
>> Le mar. 15 mai 2018 23:16, Mark Struberg  a
>> écrit :
>> 
>>> fb_tomee8
>>> I've fixed this now by fixing the broken bean. Wonder how this could have
>>> ever worked.Might also be partly random due to different build order?
>>> 
>>> But now I'm off to the next bug.
>>> EarModuleNamesTest
>>> This one also scans for a resource due to haing the openejb-itests-beans
>>> on the classpath.But since the config is done manually it misses the
>> TxMgr
>>> setup, which is null.
>>> I exclude this test for now and want to see how far I come with the other
>>> tests.
>>> LieGrue,strub
>>> 
>>>   On Tuesday, 15 May 2018, 22:03:03 CEST, Jonathan Gallimore <
>>> jonathan.gallim...@gmail.com> wrote:
>>> 
>>> Which branch?
>>> 
>>> Jon
>>> 
>>> On Tue, May 15, 2018 at 9:51 PM, Mark Struberg >> 
>>> wrote:
>>> 
 Well, this looks weird anyhow
 @Stateless
 public class AnnotatedFieldInjectionStatefulBean {
 
 compare the name and the annotation
 And the additional error messages
>>> are:org.apache.openejb.config.ValidationWarning:
 @Init is ignored for beans of type Stateless.  Class:
 org.apache.openejb.test.stateful.AnnotatedFieldInjectionStatefulBean
 Method: create"
 "org.apache.openejb.config.ValidationWarning: @Remove is ignored for
 beans of type Stateless.  Class: org.apache.openejb.test.stateful.
 AnnotatedFieldInjectionStatefulBean Method: remove""
 
 Well, yes, true!
 Is this a negative test bean? ^^
 
   On Tuesday, 15 May 2018, 21:48:26 CEST, Mark Struberg
  wrote:
 
 hi folks!
 I get 2 unit test failures which look completely weird to me.Plus they
 pass in the IDE but fail in mvn.
 ERROR] Failures:
 [ERROR]  CheckDescriptorLocationTest.testWarWithDescriptorInMetaInf
>> Keys
 do not match expected:<...or.incorrectLocation[]> but
 was:<...or.incorrectLocation[
 ignoredMethodAnnotation
 ignoredMethodAnnotation]>
 [ERROR]  CheckDescriptorLocationTest.testWarWithDescriptorInRoot Keys
>> do
 not match expected:<...or.incorrectLocation[]> but
 was:<...or.incorrectLocation[
 ignoredMethodAnnotation
 ignoredMethodAnnotation]>
 
 
 The unit test in question is
 org.apache.openejb.config.CheckDescriptorLocationTest#
 testWarWithDescriptorInRoot
 This bundles a single FooBean.class with a single error.We get this
>>> error,
 but also a few other test failures which apparently should not happen.
 Those come from beans in transitive dependency projects like
 openejb-itests-beans.
 It passes in my IDE since there the classpath is different...
 Any idea what happened?
 LieGrue,strub
 
>>>

Re: completely weird unit test failure

Re: Example request

Example request

Re: completely weird unit test failure

Re: completely weird unit test failure

Re: completely weird unit test failure

Re: completely weird unit test failure

Re: completely weird unit test failure

Re: completely weird unit test failure

MP snapshots in tomee8

Re: completely weird unit test failure

11 matches

Site Navigation

Mail list logo

Footer information