Re: JAX-RS integration with managed beans

2018-05-04 Thread kkriszti
Hi,

I have added stacktrace too in HTML format but it seems to be vanished after
preview!
So here again:
May 04, 2018 6:09:20 PM org.apache.cxf.phase.PhaseInterceptorChain
doDefaultLogging
WARNING: Application {http://example.com/}MyService has thrown exception,
unwinding now
org.apache.cxf.interceptor.Fault: org.apache.openejb.SystemException:
java.lang.NullPointerException: Cannot obtain an instance of the stateful
session bean with a null session id: Cannot obtain an instance of the
stateful session bean with a null session id:
java.lang.NullPointerException: Cannot obtain an instance of the stateful
session bean with a null session id: Cannot obtain an instance of the
stateful session bean with a null session id
at
org.apache.cxf.service.invoker.AbstractInvoker.createFault(AbstractInvoker.java:162)
at
org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:128)
at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:165)
at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:89)
at
org.apache.openejb.server.cxf.rs.AutoJAXRSInvoker.invoke(AutoJAXRSInvoker.java:68)
at
org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:57)
at
org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:93)
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:263)
at
org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
at
org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:240)
at
org.apache.openejb.server.cxf.rs.CxfRsHttpListener.doInvoke(CxfRsHttpListener.java:227)
at
org.apache.tomee.webservices.CXFJAXRSFilter.doFilter(CXFJAXRSFilter.java:94)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at 
org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
at org.apache.tomee.catalina.OpenEJBValve.invoke(OpenEJBValve.java:44)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:505)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:169)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:956)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:436)
at
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1078)
at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:625)
at
org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:316)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at
org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.apache.openejb.ApplicationException:
org.apache.openejb.SystemException: java.lang.NullPointerException: Cannot
obtain an instance of the stateful session bean with a null session id:
Cannot obtain an instance of the stateful session bean with a null session
id: java.lang.NullPointerException: Cannot obtain an instance of the
stateful session bean with a null session id: Cannot obtain an instance of
the stateful session bean with a null session id
at
org.apache.openejb.core.transaction.EjbTransactionUtil.handleApplicationException(EjbTransactionUtil.java:125)
at
org.apache.openejb.core.managed.ManagedContainer.handleException(ManagedContainer.java:750)
at
org.apache.openejb.core.managed.ManagedContainer.businessMethod(ManagedContainer.java:620)
at
org.apache.openejb.core.managed.ManagedContainer.invoke(ManagedContainer.java:352)
at 
org.apache.openejb.util.proxy.ProxyEJB$Handler.invoke(ProxyEJB.java:74)
at
com.example.MyService$$LocalBeanProxy.sayPlainTextHello(com/example/MyService.java)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at

Re: JAX-RS integration with managed beans

2018-05-04 Thread Romain Manni-Bucau
Hi

Which managedbean annotation is it? Maybe use cdi integration too.

Side note: tomee 1 uses jaxrs 1, not 2 which is in tomee 7.

Le 5 mai 2018 00:07, "kkriszti"  a écrit :

> Hi,
>
> I'm trying to migrate from WebSphere to TomEE.
> I have a @ManagedBean annotated JAX-RS resource, but when I run my EAR on
> apache-tomee-jaxrs-1.7.4 I'm getting below error:
> Please advise.
>
> For reference:  IBM JAX-RS 2.0 integration with managed beans
>  0/com.ibm.websphere.base.doc/ae/rwbs_jaxrs2.0_managedbeans.html>
>
>
> Thank you and regards,
> Krisztina
>
>
>
> --
> Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Users-
> f979441.html


JAX-RS integration with managed beans

2018-05-04 Thread kkriszti
Hi,

I'm trying to migrate from WebSphere to TomEE.
I have a @ManagedBean annotated JAX-RS resource, but when I run my EAR on
apache-tomee-jaxrs-1.7.4 I'm getting below error:
Please advise.

For reference:  IBM JAX-RS 2.0 integration with managed beans

  


Thank you and regards,
Krisztina



--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Users-f979441.html

Re: TomEE Stable and OpenJDK

2018-05-04 Thread Mark Struberg

I think what the download page fails to communicate is which EE level it 
addresses. 

We should probably split this into different areas on the download page.

To clarify this

TomEE-1.7.x adresses the JavaEE 6 specifications, with minimum requirement 
Java7 (up to Java8)
TomEE-7.0.x adresses JavaEE 7, with minimum Java7, soon up to Java11 (7.0.5 in 
preparation right now)
TomEE-7.1.x (wip) will address JavaEE7 + MicroProfile 1.3, with minimum Java8
TomEE-8.0.x (wip) will address JavaEE8 (+ MicroProfile 1.0) with minimum Java8

ATTENTION: we switched the maven groupId from org.apache.openejb.* in 
TomEE-1.7.x and before to now org.apache.tomee.
So in case you want to update, just change the groupId. All the rest remained 
the same.

Fabian, I hope I did cover what you were looking for.

txs and LieGrue,
strub


> Am 04.05.2018 um 15:05 schrieb Romain Manni-Bucau :
> 
> Hi Fabian,
> 
> answered inline
> 
> 2018-05-04 14:56 GMT+02:00 :
> 
>> Hello everyone,
>> 
>> 
>> 
>> we are currently using TomEE 1.7.4 and started to discuss an upgrade to
>> the latest version.
>> 
>> 
>> 
>> Questions (spawned by the TomEE Wikipedia article) arose as to which one
>> is currently the stable (production) release of TomEE: Is it 1.7.5 (as
>> Wikipedia suggests) or the 7.0.4 (as tomee.apache.org suggest) or even
>> 7.0.5 which we have found on a JIRA release notes page?
>> 
> 
> 1.7.5 for the 1 branch and 7.0.4 for the last one
> 
> you can refer to http://tomee.apache.org/download-ng.html to know which one
> you can pick
> 
> 
>> 
>> 
>> Another important question we were discussing: Can TomEE run on the
>> OpenJDK JVM without issues or is it necessary to run it on an Oracle JVM? I
>> have read that they are essentially the same, which doesn’t necessarily
>> mean the JDK/JREs are interchangeable, or are they?
>> 
> 
> Both work well.
> 
> 
>> 
>> 
>> Thanks in advance for your answers!
>> 
>> 
>> 
>> All the best,
>> 
>> Fabian Richter



Re: TomEE Stable and OpenJDK

2018-05-04 Thread Romain Manni-Bucau
Hi Fabian,

answered inline

2018-05-04 14:56 GMT+02:00 :

> Hello everyone,
>
>
>
> we are currently using TomEE 1.7.4 and started to discuss an upgrade to
> the latest version.
>
>
>
> Questions (spawned by the TomEE Wikipedia article) arose as to which one
> is currently the stable (production) release of TomEE: Is it 1.7.5 (as
> Wikipedia suggests) or the 7.0.4 (as tomee.apache.org suggest) or even
> 7.0.5 which we have found on a JIRA release notes page?
>

1.7.5 for the 1 branch and 7.0.4 for the last one

you can refer to http://tomee.apache.org/download-ng.html to know which one
you can pick


>
>
> Another important question we were discussing: Can TomEE run on the
> OpenJDK JVM without issues or is it necessary to run it on an Oracle JVM? I
> have read that they are essentially the same, which doesn’t necessarily
> mean the JDK/JREs are interchangeable, or are they?
>

Both work well.


>
>
> Thanks in advance for your answers!
>
>
>
> All the best,
>
> Fabian Richter
>


Re: TomEE Stable and OpenJDK

2018-05-04 Thread Andy Gumbrecht

Hi Fabian,

We're using OpenJDK & TomEE on many prod systems, so I'd say it's good 
to go in that sense.


The 1.7.5 branch is the EE6 only version, of which the webprofile is 
certified.


The 7.x branch is EE7 compatible, but not certified due only to 
licensing issues - It's still very stable and used on many prod systems.


The 8.x branch that will soon be available is EE8 compatible.

Hope that helps,

Andy Gumbrecht.


On 05/04/2018 02:56 PM, fabian-a.rich...@rohde-schwarz.com wrote:


Hello everyone,

we are currently using TomEE 1.7.4 and started to discuss an upgrade 
to the latest version.


Questions (spawned by the TomEE Wikipedia article) arose as to which 
one is currently the stable (production) release of TomEE: Is it 1.7.5 
(as Wikipedia suggests) or the 7.0.4 (as tomee.apache.org suggest) or 
even 7.0.5 which we have found on a JIRA release notes page?


Another important question we were discussing: Can TomEE run on the 
OpenJDK JVM without issues or is it necessary to run it on an Oracle 
JVM? I have read that they are essentially the same, which doesn’t 
necessarily mean the JDK/JREs are interchangeable, or are they?


Thanks in advance for your answers!

All the best,

Fabian Richter





TomEE Stable and OpenJDK

2018-05-04 Thread fabian-a . richter
Hello everyone,

 

we are currently using TomEE 1.7.4 and started to discuss an upgrade to the 
latest version.

 

Questions (spawned by the TomEE Wikipedia article) arose as to which one is 
currently the stable (production) release of TomEE: Is it 1.7.5 (as Wikipedia 
suggests) or the 7.0.4 (as tomee.apache.org suggest) or even 7.0.5 which we 
have found on a JIRA release notes page?

 

Another important question we were discussing: Can TomEE run on the OpenJDK JVM 
without issues or is it necessary to run it on an Oracle JVM? I have read that 
they are essentially the same, which doesn’t necessarily mean the JDK/JREs are 
interchangeable, or are they?

 

Thanks in advance for your answers!

 

All the best,

Fabian Richter



smime.p7s
Description: S/MIME Cryptographic Signature