Re: IllegalProductException: return type must be Serializable for Hibernate SessionImpl???

[Romain Manni-Bucau]

Yes, org.apache.webbeans.component.AbstractProducerBean#checkScopeType
enforces the returned type to be serializable.

Tracked at https://issues.apache.org/jira/browse/OWB-1177


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2017-04-11 10:04 GMT+02:00 DonatasCiuksys :

> Well, I don't think this is that simple. CDI 1.2 spec chapter 6.6.5 says:
>
> "If a producer method declares a passivating scope and doesn’t only return
> Serializable types at runtime, then the container must throw an
> IllegalProductException."
>
> and
>
> "If a producer field declares a passivating scope and doesn’t only contain
> Serializable values at runtime then the container must throw an
> IllegalProductException."
>
> Especially "producer field" stresses "Serializable values", not types. And
> if my producer returns Hibernate SessionImpl, why would you say that it is
> not "Serializable type"?
>
> "only return Serializable types at runtime" - this says to check the return
> value, not the method signature.
>
> As a final point: check chapter 3.5.2. It contains this example:
>
>  @Produces @ConversationScoped @UserDatabase
> public EntityManager create(EntityManagerFactory emf) {
> return emf.createEntityManager();
> }
>
> It seems this is not possible with OpenWebBeans at all. I remember CDI 1.1
> spec requiring to check method signatures, but 1.2 no longer says anything
> about method signatures, CDI must check the object that is being returned.
>
> Donatas
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.n4.nabble.com/
> IllegalProductException-return-type-must-be-Serializable-for-Hibernate-
> SessionImpl-tp4681517p4681520.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: IllegalProductException: return type must be Serializable for Hibernate SessionImpl???

[Romain Manni-Bucau]

Hi

check out emf.createEntityManager(SynchronizationType.
SYNCHRONIZED)).getClass()


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2017-04-10 22:28 GMT+02:00 DonatasCiuksys :

> Hi,
>
> I'm using TomEE 7.0.3 WebProfile (thus latest OpenWebBeans) with Hibernate
> 5.2.9. I'm trying to write CDI producer for ViewScoped EntityManager:
>
> @PersistenceUnit
> private EntityManagerFactory emf;
>
> @Produces
> @ViewScoped
> private EntityManager createJTAViewScopedEntityManager() {
> return emf.createEntityManager(SynchronizationType.SYNCHRONIZED));
> }
>
> Yet at the injection point I'm getting exception:
> javax.el.ELException: javax.enterprise.inject.IllegalProductException:
> WebBeans producer : createJTAViewScopedEntityManager return type in the
> component implementation class : lt.vu.usecases.cdi.JPAResources with
> passivating scope @javax.faces.view.ViewScoped must be Serializable
>
> I don't understand the reason for this exception, because Hibernate returns
> instance of class "SessionImpl" (as can be seen with debugger), and this
> class implements Serializable. What is the problem?
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.n4.nabble.com/
> IllegalProductException-return-type-must-be-Serializable-for-Hibernate-
> SessionImpl-tp4681517p4681518.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: Local lookup for ejb beans

[Romain Manni-Bucau]

It forces you to use tomee lookups and bypass contextuality (tomcat per
classloader context) yes. Then not sure i followed the naming of your
example but happy if it works.

However openejb/global and openejb/Deployment etc.. subtrees are internals
so not guanranteed to work

Le 8 avr. 2017 16:06, "Dignesh"  a écrit :

> Hi Romain,
> Below is the snip of code I have used.
>
> Properties properties = new Properties();
> properties.setProperty(Context.INITIAL_CONTEXT_FACTORY,
> "org.apache.openejb.core.OpenEJBInitialContextFactory");
> final Context ctx = new InitialContext(properties);
>
>
> When I use openejb: global/global local jndi lookup is successful
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.
> n4.nabble.com/Local-lookup-for-ejb-beans-tp4681498p4681506.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: Local lookup for ejb beans

[Romain Manni-Bucau]

Le 8 avr. 2017 12:57, "Dignesh"  a écrit :

Hi Romain,
 I already did that passing that.it did not work.Do we Need to ass some
other property apart from context factory in local lookup mode ?


No

Maybe you dont use the right name?

May I know the reason why we cannot use openejb:global/global?


Sure: it is not bound, why should it work? All EJB are bound there but not
with global/global.





--
View this message in context: http://tomee-openejb.979440.
n4.nabble.com/Local-lookup-for-ejb-beans-tp4681498p4681504.html
Sent from the TomEE Dev mailing list archive at Nabble.com.

Re: Local lookup for ejb beans

[Romain Manni-Bucau]

Yes but in local lookup mode, see
http://tomee.apache.org/advanced/client/jndi.html

Le 8 avr. 2017 10:57, "Dignesh"  a écrit :

> Hi Romain,
>  I haven't understood what below means.
> Passing as context factory openejb one you would get stable names
>
> Does it mean I need to pass CONTEXT_FACTORY something similar to way i do
> the remote look up ?
> "INITIAL_CONTEXT_FACTORY"="org.apache.openejb.client.
> RemoteInitialContextFactory"
>
>
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.
> n4.nabble.com/Local-lookup-for-ejb-beans-tp4681498p4681500.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: tomee-1.7.x bug hunting

[Romain Manni-Bucau]

Hi Mark

>From phone but first one is likely linked to last upgrades versus last one
log is normal (likely more a timing issue, we saw it when buildbot was
highly used but if we increase too much wait time we dont test that well so
kind of a compromise).

Can help on monday with first one if still weird why context is not found
properly.

Le 8 avr. 2017 12:35, "Mark Struberg"  a écrit :

> I try to finally get our CI all green again. RELIABLY. Currently a few of
> them are randomly failing.
>
>
> Current target 2 failure left.
>
> in:
> https://ci.apache.org/builders/tomee-1.7.x-ubuntu/
> builds/183/steps/test/logs/stdio
>
> Seems to happen only in the ExtCdi bug for tomee-plus tests.
>
> Apr 08, 2017 1:50:12 AM org.apache.openejb.assembler.classic.Assembler
> createApplication
> INFO: Deployed Application(path=/home/buildslave/slave/tomee-1.7.x-
> ubuntu/build/arquillian/arquillian-tomee-tests/
> arquillian-tomee-codi-tests/target/arquillian-test-working-dir/0/
> MyFacesExtCdiDeploymentTest
> )
> Apr 08, 2017 1:50:12 AM org.apache.catalina.core.ContainerBase
> addChildInternal
> SEVERE: ContainerBase.addChild: start:
> org.apache.catalina.LifecycleException: Failed to start component
> [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/
> MyFacesExtCdiDeploymentTest]]
> 
> Caused by: java.lang.NullPointerException
> at org.apache.openejb.util.AppFinder.findAppContextOrWeb(
> AppFinder.java:28)
> at org.apache.openejb.cdi.ThreadSingletonServiceImpl.get(
> ThreadSingletonServiceImpl.java:260)
> at org.apache.openejb.cdi.ThreadSingletonServiceImpl.getContext(
> ThreadSingletonServiceImpl.java:240)
> at org.apache.openejb.cdi.ThreadSingletonServiceImpl.get(
> ThreadSingletonServiceImpl.java:300)
> at org.apache.openejb.cdi.ThreadSingletonServiceImpl.get(
> ThreadSingletonServiceImpl.java:57)
> at org.apache.webbeans.config.WebBeansFinder.getSingletonInstance(
> WebBeansFinder.java:51)
> at org.apache.webbeans.config.WebBeansContext.getInstance(
> WebBeansContext.java:168)
> at org.apache.webbeans.el22.WebBeansELResolver.(
> WebBeansELResolver.java:61)
> at org.apache.openejb.cdi.CustomELAdapter.getOwbELResolver(
> CustomELAdapter.java:41)
> at org.apache.tomee.catalina.TomcatWebAppBuilder.startInternal(
> TomcatWebAppBuilder.java:1405)
> at org.apache.tomee.catalina.TomcatWebAppBuilder.configureStart(
> TomcatWebAppBuilder.java:1100)
> at org.apache.tomee.catalina.GlobalListenerSupport.lifecycleEvent(
> GlobalListenerSupport.java:130)
> at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(
> LifecycleSupport.java:117)
> at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(
> LifecycleBase.java:90)
> at org.apache.catalina.core.StandardContext.startInternal(
> StandardContext.java:5522)
> at org.apache.catalina.util.LifecycleBase.start(
> LifecycleBase.java:145)
> ... 56 more
>
> Apr 08, 2017 1:50:12 AM org.apache.openejb.assembler.classic.Assembler
> destroyApplication
> INFO: Undeploying app: /home/buildslave/slave/tomee-
> 1.7.x-ubuntu/build/arquillian/arquillian-tomee-tests/
> arquillian-tomee-codi-tests/target/arquillian-test-working-dir/0/
> MyFacesExtCdiDeploymentTest
> Apr 08, 2017 1:50:12 AM org.apache.openejb.core.transaction.EjbTransactionUtil
> handleSystemException
>
>
> in:
> https://ci.apache.org/builders/tomee-1.7.x-ubuntu/
> builds/184/steps/test/logs/stdio
>
> Running org.apache.openejb.concurrencyutilities.test.
> ManagedScheduledExecutorServiceImplFactoryTest
> WARNING - Unable to create configured thread factory: org.apache.openejb.
> concurrencyutilities.test.ManagedScheduledExecutorServiceImplFactoryTest$
> MyThreadFactory
> java.lang.RuntimeException: Throwing test exception in MyThreadFactory - I
> expect to see this logged as a warning!
> at org.apache.openejb.concurrencyutilities.test.
> ManagedScheduledExecutorServiceImplFactoryTest$MyThreadFactory.(
> ManagedScheduledExecutorServiceImplFactoryTest.java:41)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(
> NativeConstructorAccessorImpl.java:57)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(
> DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
> at java.lang.Class.newInstance(Class.java:383)
> at org.apache.openejb.concurrencyutilities.ee.factory.
> ManagedScheduledExecutorServiceImplFactory.createScheduledExecutorService(
> ManagedScheduledExecutorServiceImplFactory.java:40)
> at org.apache.openejb.concurrencyutilities.ee.factory.
> ManagedScheduledExecutorServiceImplFactory.create(
> ManagedScheduledExecutorServiceImplFactory.java:34)
> at org.apache.openejb.concurrencyutilities.test.
> ManagedScheduledExecutorServiceImplFact

Re: Local lookup for ejb beans

[Romain Manni-Bucau]

Hi

Le 8 avr. 2017 10:46, "Dignesh"  a écrit :

Hi,

Can we use "openejb:global/global" as JNDI prefix when doing the local ejb
lookup instead of "java:global".



No






The problem is in general that "new InitialContext()" is not always the
same.It depends in which thread/classloader this call is made. As long as
you call it within an EJB or Servlet and appropriate thread you see
everything. I have logged the JNDI tree, once within an approriate
thread/classloader and once outside it .So Can we use openejb:global/global
as JNDI prefix to access the beans within the TomEE ?


Passing as context factory openejb one you would get stable names



Thank you,
Dignesh,



--
View this message in context: http://tomee-openejb.979440.
n4.nabble.com/Local-lookup-for-ejb-beans-tp4681498.html
Sent from the TomEE Dev mailing list archive at Nabble.com.

Re: Java EE Security API implementation plans for TomEE 8?

[Romain Manni-Bucau]

Hi Rudy,

I guess it would pass by a new incubator project then tomee would just
integrate it (like batchee).

ATM we are a bit waiting to see what's the outcome and specs are still
moving in various ways, sometimes surprisingly (see jaxrs 2.1 nio revert
for instance) soo too early could be too wrong too ;)


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2017-04-06 12:11 GMT+02:00 Rudy De Busscher :

> Hi All,
>
> I'm working as individual on the Expert Group of the Java EE Security API
> (JSR-375).
>
> And I was wondering what the plans are within TomEE or Apache to make an
> implementation of this specification? As this will be required when TomEE
> will be Java EE 8 compliant I guess.
>
> And if I can help in any way? (as I'm also an Apache committer on various
> projects)
>
> Thanks
>
> Best regards
> Rudy De Busscher
>

Re: Issue with OracleXA datasource (unable to enlist XAResource)

[Romain Manni-Bucau]

then do you have a transaction?


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2017-04-04 13:47 GMT+02:00 Dignesh :

> Hi Romain,
> I dont think it is a network issue. If I change it to a normal datasource
> from XA, it is working fine. And it is a simple delete query
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.
> n4.nabble.com/Issue-with-OracleXA-datasource-unable-to-enlist-XAResource-
> tp4681459p4681477.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: Issue with OracleXA datasource (unable to enlist XAResource)

[Romain Manni-Bucau]

the issue is a network issue from what we have in the dump so not related
to tomee. You need to check your infra and why you dont get the answer
there. Can also be a too "big" query.


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2017-04-04 13:43 GMT+02:00 Dignesh :

> No.Should it be added ? if yes can you please let me what needs to be
> added.
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.
> n4.nabble.com/Issue-with-OracleXA-datasource-unable-to-enlist-XAResource-
> tp4681459p4681475.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: Issue with OracleXA datasource (unable to enlist XAResource)

[Romain Manni-Bucau]

do you have a timeout on the datasource or something like that?


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2017-04-04 13:36 GMT+02:00 Dignesh :

> Yes it is bean call at shutdown.
> The thread is getting frezzed when I call connection.preparedStatement().
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.
> n4.nabble.com/Issue-with-OracleXA-datasource-unable-to-enlist-XAResource-
> tp4681459p4681473.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: Issue with OracleXA datasource (unable to enlist XAResource)

[Romain Manni-Bucau]

2017-04-04 13:24 GMT+02:00 Dignesh :

> Thank you Romain. I made the change.
> Now when I shutdown the TomEE, it is not stopped. When I see the thread
> dump,It is freezed at this point. Is there any other configuration that
> needs to be added?
>
> "localhost-startStop-2" daemon prio=6 tid=0x1a7cf000 nid=0x8bc
> runnable [0x17fed000]
>java.lang.Thread.State: RUNNABLE
> at java.net.SocketInputStream.socketRead0(Native Method)
> at java.net.SocketInputStream.read(SocketInputStream.java:152)
> at java.net.SocketInputStream.read(SocketInputStream.java:122)
> at oracle.net.ns.Packet.receive(Packet.java:282)
> at oracle.net.ns.DataPacket.receive(DataPacket.java:103)
> at oracle.net.ns.NetInputStream.getNextPacket(NetInputStream.
> java:230)
> at oracle.net.ns.NetInputStream.read(NetInputStream.java:175)
> at oracle.net.ns.NetInputStream.read(NetInputStream.java:100)
> at oracle.net.ns.NetInputStream.read(NetInputStream.java:85)
> at
> oracle.jdbc.driver.T4CSocketInputStreamWrapper.readNextPacket(
> T4CSocketInputStreamWrapper.java:122)
> at
> oracle.jdbc.driver.T4CSocketInputStreamWrapper.read(
> T4CSocketInputStreamWrapper.java:78)
> at oracle.jdbc.driver.T4CMAREngine.unmarshalUB1(
> T4CMAREngine.java:1179)
> at oracle.jdbc.driver.T4CMAREngine.unmarshalSB1(
> T4CMAREngine.java:1155)
> at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:279)
> at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:186)
> at oracle.jdbc.driver.T4CTTIOtxse.doOTXSE(T4CTTIOtxse.java:163)
> at oracle.jdbc.driver.T4CXAResource.doStart(
> T4CXAResource.java:185)
> - locked <0x000720c1adf8> (a oracle.jdbc.driver.T4CConnection)
> at oracle.jdbc.xa.client.OracleXAResource.start(
> OracleXAResource.java:228)
> - locked <0x000720c1adf8> (a oracle.jdbc.driver.T4CConnection)
> at
> org.apache.geronimo.transaction.manager.TransactionImpl.enlistResource(
> TransactionImpl.java:202)
> - locked <0x0006f7519400> (a
> org.apache.geronimo.transaction.manager.TransactionImpl)
> at
> org.apache.openejb.resource.jdbc.managed.local.ManagedConnection.invoke(
> ManagedConnection.java:134)
>
>
>
Sure it is this dump? this thread is daemon so shouldnt prevent to stop.
ALso the rest of the stack would say which part of the code is triggered
(probably a bean call at shutdown).


>
> --
> View this message in context: http://tomee-openejb.979440.
> n4.nabble.com/Issue-with-OracleXA-datasource-unable-to-enlist-XAResource-
> tp4681459p4681470.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: Issue with OracleXA datasource (unable to enlist XAResource)

[Romain Manni-Bucau]

idea was if you want to use dbcp which seems the case you need to set it in
the other resource.

I'm not sure of the whole usage but looks like you use a CMT resource (XA
or JtaManaged=true) with a manual management of quartz which cant works
since the quartz store will try to manage the autocommit and the datasource
will not allow it


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2017-04-03 16:47 GMT+02:00 Dignesh :

> I have removed the DataSourceCreator = dbcp from the resource itself and
> tried, Still I see the issue.
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.
> n4.nabble.com/Issue-with-OracleXA-datasource-unable-to-enlist-XAResource-
> tp4681459p4681467.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: Issue with OracleXA datasource (unable to enlist XAResource)

[Romain Manni-Bucau]

is it a typo or not: datasource creator should be in the datasource, not
the xa impl (other resource to make it clear)


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2017-04-03 16:31 GMT+02:00 Dignesh :

> Added user and password - still i see the same issue.
>  class-name="oracle.jdbc.xa.client.OracleXADataSource">
> Url *
> DataSourceCreator = dbcp
> User dignesh
> Password dignesh
> 
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.
> n4.nabble.com/Issue-with-OracleXA-datasource-unable-to-enlist-XAResource-
> tp4681459p4681465.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: Issue with OracleXA datasource (unable to enlist XAResource)

[Romain Manni-Bucau]

User and Password (OracleXADataSource doesn't know about UserName field)


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2017-04-03 16:23 GMT+02:00 Dignesh :

> Below is my configuration in tomee.xml file.
> So you mean i need to add username in "XA/Datasource" ?
>
> 
> XaDataSource Xa/ds
> UserName 
> Password 
> PasswordCipher 
> 
>  class-name="oracle.jdbc.xa.client.OracleXADataSource">
> Url *
> DataSourceCreator = dbcp
> 
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.
> n4.nabble.com/Issue-with-OracleXA-datasource-unable-to-enlist-XAResource-
> tp4681459p4681463.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: Issue with OracleXA datasource (unable to enlist XAResource)

[Romain Manni-Bucau]

can you ensure both xa and wrapper/pool have the user set correctly please?


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2017-04-03 16:18 GMT+02:00 Dignesh :

> No.
> I just see only errorCode: 4 in the logs.
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.
> n4.nabble.com/Issue-with-OracleXA-datasource-unable-to-enlist-XAResource-
> tp4681459p4681461.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: Issue with OracleXA datasource (unable to enlist XAResource)

[Romain Manni-Bucau]

do you have the oracle error code before?


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2017-04-03 16:15 GMT+02:00 Dignesh :

> Hi ,
>
> I am using 7.0.2 version of TomEE. And below is my resource configuration
> in
> tomee.xml file.
>
> 
> XaDataSource Xa/ds
> UserName 
> Password 
> PasswordCipher 
> 
>  class-name="oracle.jdbc.xa.client.OracleXADataSource">
> Url *
> DataSourceCreator = dbcp
> 
>
> I am seeing the unable to enlist XAResource error messages in the log file.
>
> WARNING: Unable to enlist XAResource
> oracle.jdbc.driver.T4CXAResource@657d3ab1, errorCode: 4
> oracle.jdbc.xa.OracleXAException
> at
> oracle.jdbc.xa.OracleXAResource.checkError(OracleXAResource.java:1033)
> at
> oracle.jdbc.xa.client.OracleXAResource.start(OracleXAResource.java:240)
> at
> org.apache.geronimo.transaction.manager.TransactionImpl.enlistResource(
> TransactionImpl.java:202)
> at
> org.apache.openejb.resource.jdbc.managed.local.ManagedConnection.invoke(
> ManagedConnection.java:134)
> at com.sun.proxy.$Proxy82.getAutoCommit(Unknown Source)
> at
> org.quartz.impl.jdbcjobstore.AttributeRestoringConnectionIn
> vocationHandler.setAutoCommit(AttributeRestoringConnectionIn
> vocationHandler.java:90)
> at
> org.quartz.impl.jdbcjobstore.AttributeRestoringConnectionIn
> vocationHandler.invoke(AttributeRestoringConnectionIn
> vocationHandler.java:66)
> at com.sun.proxy.$Proxy82.setAutoCommit(Unknown Source)
> at
> org.quartz.impl.jdbcjobstore.JobStoreSupport.getConnection(
> JobStoreSupport.java:799)
> at
> org.quartz.impl.jdbcjobstore.JobStoreCMT.executeInLock(
> JobStoreCMT.java:235)
> at
> org.quartz.impl.jdbcjobstore.JobStoreSupport.storeJobsAndTriggers(
> JobStoreSupport.java:1323)
> at
> org.quartz.core.QuartzScheduler.scheduleJobs(QuartzScheduler.java:1056)
> at
> org.quartz.core.QuartzScheduler.scheduleJob(QuartzScheduler.java:1066)
>
> Is there any other configuration to done which i am missing ?
>
> Thank you,
> Dignesh,
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.
> n4.nabble.com/Issue-with-OracleXA-datasource-unable-to-
> enlist-XAResource-tp4681459.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: Why do we have two mailing lists for our commits

[Romain Manni-Bucau]

Should but probably time to drop it anyway

Le 2 avr. 2017 13:54, "Mark Struberg"  a écrit :

> doesn't the openejb one just forward to the tomee? So it's just an alias?
>
> LieGrue,
> strub
>
>
> > Am 01.04.2017 um 21:47 schrieb Romain Manni-Bucau  >:
> >
> > Historical, only tomee ones should be kept active.
> >
> > Think now we can remove the old one but in 2011 we kept it for a smooth
> > transition.
> >
> > Le 1 avr. 2017 16:13, "Alan Cabrera"  a écrit :
> >
> > I’ve noticed that we have two mailing for commits:
> > comm...@openejb.apache.org
> > comm...@tomee.apache.org
> > Why do we have two?
> >
> >
> > Regards,
> > Alan
>
>

Re: Why do we have two mailing lists for our commits

[Romain Manni-Bucau]

Historical, only tomee ones should be kept active.

Think now we can remove the old one but in 2011 we kept it for a smooth
transition.

Le 1 avr. 2017 16:13, "Alan Cabrera"  a écrit :

I’ve noticed that we have two mailing for commits:
comm...@openejb.apache.org
comm...@tomee.apache.org
Why do we have two?


Regards,
Alan

Re: issue with XADatasource in sqlserver.

[Romain Manni-Bucau]

depending the xadatasource impl you can need to repeat jdbcurl/username etc
on the pool itself


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2017-03-29 11:32 GMT+02:00 Dignesh :

> Yes. I am able to connect .
>
> If I configure to Non XA datasource it is working fine.
> I am able to get it work with below configuration
>
> 
> JdbcDriver com.microsoft.sqlserver.jdbc.SQLServerDriver
> JdbcUrl 
> UserName OTMM
> Password ***
> JtaManaged false
> 
>
>
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.
> n4.nabble.com/issue-with-XADatasource-in-sqlserver-tp4681379p4681383.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: issue with XADatasource in sqlserver.

[Romain Manni-Bucau]

did you check you can connect on that url (telnet host port)


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2017-03-29 11:25 GMT+02:00 Dignesh :

>
> C:\dignesh\TomEE\apache-tomee-plus-7.0.2\bin>tomee.bat setters -c
> com.microsoft.sqlserver.jdbc.SQLServerXADataSource
> - ApplicationName
> - DatabaseName
> - Description
> - Encrypt
> - FailoverPartner
> - HostNameInCertificate
> - InstanceName
> - IntegratedSecurity
> - LastUpdateCount
> - LockTimeout
> - LogWriter
> - LoginTimeout
> - PacketSize
> - Password
> - PortNumber
> - ResponseBuffering
> - SelectMethod
> - SendStringParametersAsUnicode
> - ServerName
> - TrustServerCertificate
> - TrustStore
> - TrustStorePassword
> - URL
> - User
> - WorkstationID
> - XopenStates
>
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.
> n4.nabble.com/issue-with-XADatasource-in-sqlserver-tp4681379p4681381.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: issue with XADatasource in sqlserver.

[Romain Manni-Bucau]

can you run ./bin/tomee.sh setters -c com.microsoft.sqlserver.jdbc.
SQLServerXADataSource

Don't think there is a "Url" config on that class


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2017-03-29 11:11 GMT+02:00 Dignesh :

> Hi,
> I am using TomEE 7.0.2
>
> I am configuring the XAdatasources in TomEE. I was able to do it
> successfully in Oracle and PostgreSQL. I am facing some issues with it in
> Sqlserver.
>
> Below is my resource configuration in tomee.xml file.
>
> 
> XaDataSource Xa/ds
> UserName 
> Password 
> PasswordCipher 
> 
>
> For postgres :-
>
> 
> Url *
> DataSourceCreator = dbcp
> 
>
> For Oracle :-
>  class-name="oracle.jdbc.xa.client.OracleXADataSource">
> Url *
> DataSourceCreator = dbcp
> 
>
> For SQlserver :-
>
>  id="XA/Datasource">
> Url *
> DataSourceCreator = dbcp
> 
>
> So the above configurations work fine in oracle and postgres. In sqlserver
> when I start TomEE it is giving me the connection exceptions.When I revert
> back to non xadatsource it is working fine. Is there any extra
> configuration
> that needs to be done in sqlserver or is it the approach which i am using
> is
> incorrect. can any one please help me on this.
>
> Below is the error when i start the server
>
> com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to
> the host 10.6.32.25, port 2300 has failed. Error: Connection timed out:
> connect. Please verify the connection properties and check that a SQL
> Server
> instance is running on the host and accepting TCP/IP connections at the
> port, and that no firewall is blocking TCP connections to the port.
> at
> com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(
> SQLServerException.java:130)
> at
> com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(
> SQLServerConnection.java:1195)
> at
> com.microsoft.sqlserver.jdbc.SQLServerConnection.loginWithoutFailover(
> SQLServerConnection.java:1054)
> at
> com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(
> SQLServerConnection.java:758)
> at
> com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(
> SQLServerDriver.java:842)
> at
> org.apache.tomcat.jdbc.pool.PooledConnection.connectUsingDriver(
> PooledConnection.java:310)
> at
> org.apache.tomcat.jdbc.pool.PooledConnection.connect(
> PooledConnection.java:203)
> at
> org.apache.tomcat.jdbc.pool.ConnectionPool.createConnection(
> ConnectionPool.java:718)
> at
> org.apache.tomcat.jdbc.pool.ConnectionPool.borrowConnection(
> ConnectionPool.java:650)
> at
> org.apache.tomcat.jdbc.pool.ConnectionPool.init(ConnectionPool.java:468)
> at
> org.apache.tomcat.jdbc.pool.ConnectionPool.(ConnectionPool.java:143)
> at
> org.apache.tomee.jdbc.TomEEDataSourceCreator$TomEEConnectionPool.(
> TomEEDataSourceCreator.java:221)
> at
> org.apache.tomee.jdbc.TomEEDataSourceCreator$TomEEDataSource.createPool(
> TomEEDataSourceCreator.java:154)
> at
> org.apache.tomee.jdbc.TomEEDataSourceCreator$TomEEDataSource.(
> TomEEDataSourceCreator.java:131)
> at
> org.apache.tomee.jdbc.TomEEDataSourceCreator.pool(
> TomEEDataSourceCreator.java:68)
> at
> org.apache.openejb.resource.jdbc.DataSourceFactory.create(
> DataSourceFactory.java:216)
> 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.xbean.recipe.ReflectionUtil$StaticFactory.
> create(ReflectionUtil.java:997)
> at
> org.apache.xbean.recipe.ObjectRecipe.internalCreate(ObjectRecipe.java:276)
> at
> org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:96)
> at
> org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:61)
> at
> org.apache.openejb.assembler.classic.Assembler.doCreateResource(Ass

Re: Exception seen while TomEE start up

[Romain Manni-Bucau]

Hi

Application needs to be instantiated during scanning (before actual
deployment) to be able to enrich the getClasses even without cdi. just
don't use the constructor but a lazy init there.


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2017-03-25 5:16 GMT+01:00 Dignesh :

> Hi,
> I am using TomEE 7.0.2.
>
> To get a defined startup order we use an application.xml including
> true tag.
> We are using Jersey as JAX-RS provider.
> We have written a custom class in a war (B.war) which extends the resource
> config of jersey.we are doing an ejb look up from the custom class, which
> is
> failing. - Reason my beans are not initailzed at this moment.
> My webApp (B.war) will be initialised only after the beans are initialised.
> Looks like openejb is matching the resource config during the start up and
> I
> see the below error in my log file. After this error I see my beans are
> initialised.
>
>
>
> media ->  09:33:05,535 ERROR [BaseServices] Unhandled
> exception:javax.naming.NameNotFoundException: Name
> [java:global/dignesh/dignesh-ejb/SystemBean!com.dignesh.system.interfaces.
> SystemServiceLocal]
> is not bound in this Context. Unable to find [java:global].
> media ->  09:33:05,568 ERROR [LogUtils]
> Exception Stack Trace:
> com.dignesh.common.exception.CustomException: An error occurred attempting
> to execute an ejb call.
> at
> com.dignesh.common.services.BaseServices.executeEjbMethod(
> BaseServices.java:247)
> at
> com.dignesh.system.services.SystemServices.retreivesetting(
> SystemServices.java:142)
> at com.dignesh.common.prefs.TPrefJApi.getValue(TPrefJApi.java:307)
> at com.dignesh.common.prefs.Tpef.TPrefGetString(Tpef.java:106)
> at
> com.dignesh.common.prefs.Settings.getPreference(Settings.java:103)
> at
> dignesh.learning.restapi.core.RestAPIApplication.(
> RestAPIApplication.java:42)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(
> NativeConstructorAccessorImpl.java:57)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(
> DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
> at java.lang.Class.newInstance(Class.java:374)
> at
> org.apache.openejb.config.AnnotationDeployer$ProcessAnnotatedBeans.deploy(
> AnnotationDeployer.java:2237)
> at
> org.apache.openejb.config.AnnotationDeployer$ProcessAnnotatedBeans.deploy(
> AnnotationDeployer.java:2022)
> at
> org.apache.openejb.config.AnnotationDeployer.deploy(
> AnnotationDeployer.java:383)
> at
> org.apache.openejb.config.ConfigurationFactory$Chain.
> deploy(ConfigurationFactory.java:420)
> at
> org.apache.openejb.config.ConfigurationFactory.configureApplication(
> ConfigurationFactory.java:1037)
> at
> org.apache.openejb.config.ConfigurationFactory.configureApplication(
> ConfigurationFactory.java:856)
> 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:503)
> at
> org.apache.openejb.assembler.classic.Assembler.build(Assembler.java:482)
> 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:606)
> at org.apache.catalina.startup.Catalina.load(Catalina.java:629)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorIm

Re: Issue with TomEE shutdown

[Romain Manni-Bucau]

pool-21-thread-1@6 is still not closed.


Did you identify where it is coming from?


Le 23 mars 2017 05:06, "Dignesh"  a écrit :

> Hi Romain,
>
> I made the changes in my code closing the threadpoolexecutor . I am still
> seeing the issue more often now.
>
> I have attached the latest thread dumps captured. threaddump-latest.txt
>  threaddump-latest.txt>
>
>
> Thank you very much in advance
>
> -Dignesh-
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.
> n4.nabble.com/Issue-with-TomEE-shutdown-tp4681128p4681363.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: few java 9 jigsaw pointers and thoughts

[Romain Manni-Bucau]

2017-03-20 21:17 GMT+01:00 Bjorn Danielsson <
bjorn-apa...@lists.cuspycode.com>:

> Hi Romain and everyone,
>
> I have just recently become aware of this issue with Java 9,
> and I'm not sure I understand everything yet. But my spontaneous
> reaction is that a classloader hack would be an acceptable solution,
> because it's easy to understand for ordinary devops people.
>
>
Hmm, not sure it would be easy cause it can lead to bypass the JVM for the
JVM classes so can be quite tricky to get right (and slower at startup)


> Does anyone know if the Tomcat core team has been discussing this?
> I haven't had time to follow any of the lists for ages unfortunately,
> and googling has not been very helpful to me.
>
>
They worked with Java core dev to make their code passing but I don't think
the overall system (jvm+server+apps+libs) has been discussed.


> --
> Bjorn Danielsson
> Cuspy Code AB
>
>
> Romain Manni-Bucau  wrote:
> > Hey guys,
> >
> > not sure anyone tried to run tomee on java 9 but wondered if j9 module
> > system was kind of "fixed" since it was really broken last time i tested
> > and tried to run our simple-singleton sample today.
> >
> > Have to admit I tend to think it is a feature breaiking java ecosystem
> but
> > here is a few more pragmatic feedback and how we can make this module
> > running:
> >
> > - (easy) ORB/corba is not exported by default so we need to check by
> > reflection we can access it or not, I guess the fix for us is to remove
> > corba reference from our codebase, AFAIK it is not used and no more
> needed.
> > - (medium) bytecode reading: our current code base can read until java 8
> > bytecode and we need to upgrade xbean-asm-shaded and xbean-finder-shaded
> > (xbean snapshot is ready). We also need to upgrade the finders we have in
> > our codebase to ASM6 (java 9) but nothing hurting a lot - that's what we
> do
> > for each new java version.
> > - (unknown) we need all our dependencies to upgrade
> > - (open and likely hard if it takes into account our full stack) to run
> the
> > simple-singleton example I needed to add jaxb dependency (alternative is
> to
> > activate the module) and open a few modules, typically:
> >
> > --add-modules java.logging --add-opens
> > java.logging/java.util.logging=ALL-UNNAMED
> > --add-opens=java.base/java.lang=ALL-UNNAMED
> >
> > This globally request to add to our code the missing permission in the
> JVM
> > (keep in mind i ran simple-singleton which doesnt cover much of our
> > codebase/stack). The issue is this option is on the JVM so we can hide it
> > in tomee in catalina scripts and in arquillian through RemoteServer but
> for
> > embedded tests we'll require the user to do it.
> >
> > We can likely rework a bit our code to not require them all (some are
> easy
> > to workaround like the logging one or the GET_PACKAGE usage for @Vetoed)
> > but when we'll start to create a module-info.java ourself and our stack
> > we'll not just be in the unamed module merged but in several modules
> we'll
> > need to maintain these references exactly like we did when we were still
> > handling OSGi and even if maven helps a bit it breaks the ability to
> change
> > a little bit the stack (it was common to upgrade cxf for instance) since
> it
> > depends if cxf export is stable or not.
> >
> > I'm not yet sure how we want to tackle it. Good news is "yes it will
> work".
> > Bad one is "yes it will mess up each version".
> >
> > I fear jigsaw can't be removed from java 9 anymore (not sure why to be
> > honest) but I start to wonder if we should do a system (subclassloader?)
> to
> > completely bypass it and keep user experience smooth.
> >
> > Anyone having some other feedback?
> >
> > Romain Manni-Bucau
> > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > <https://blog-rmannibucau.rhcloud.com> | Old Blog
> > <http://rmannibucau.wordpress.com> | Github <https://github.com/
> rmannibucau> |
> > LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
> > <https://javaeefactory-rmannibucau.rhcloud.com>
>

Re: Specify the order of deploying the ears

[Romain Manni-Bucau]

Hi

I'm assuming you use something like



Instead just do






Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2017-03-17 12:32 GMT+01:00 Dignesh :

> Hi,
>
> I am using the TomEE 7.0.2. I have multiple ears in apps folder. I have an
> ear(A) which is dependent on ear(B).
> I want ear(B) to be deployed 1st followed by ear(A). Is there any
> configuration that can be done to achieve this.
>
> Thank you,
> Dignesh,
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.
> n4.nabble.com/Specify-the-order-of-deploying-the-ears-tp4681320.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

[RESULT][VOTE] Apache TomEE 7.0.3

[Romain Manni-Bucau]

which makes 3 +1 bindings (Mark, JL and me) and one +-0 binding and one +1
non-binding (cocorosello)

therefore this vote passes, thank you all guys, will continue with the
release steps


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2017-03-12 22:25 GMT+01:00 Jean-Louis Monteiro :

> Here is my +1
> Thanks Romain
>
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
> On Sat, Mar 11, 2017 at 1:43 PM, Romain Manni-Bucau  >
> wrote:
>
> > https://issues.apache.org/jira/browse/TOMEE-2022
> >
> >
> > Romain Manni-Bucau
> > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > <https://blog-rmannibucau.rhcloud.com> | Old Blog
> > <http://rmannibucau.wordpress.com> | Github <https://github.com/
> > rmannibucau> |
> > LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
> > <https://javaeefactory-rmannibucau.rhcloud.com>
> >
> > 2017-03-11 13:38 GMT+01:00 Romain Manni-Bucau :
> >
> > > no reason, missed it basically. feel free to open a ticket
> > >
> > >
> > > Romain Manni-Bucau
> > > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > > <https://blog-rmannibucau.rhcloud.com> | Old Blog
> > > <http://rmannibucau.wordpress.com> | Github
> > > <https://github.com/rmannibucau> | LinkedIn
> > > <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
> > > <https://javaeefactory-rmannibucau.rhcloud.com>
> > >
> > > 2017-03-10 23:22 GMT+01:00 cocorossello :
> > >
> > >> +1 (tested)
> > >>
> > >> Just wanted to ask if there is any reason to bundle myfaces 2.2.11,
> > since
> > >> there is a 2.2.12 release (not that I need it anyway)
> > >>
> > >>
> > >>
> > >> --
> > >> View this message in context: http://tomee-openejb.979440.n4
> > >> .nabble.com/VOTE-Apache-TomEE-7-0-3-tp4681228p4681278.html
> > >> Sent from the TomEE Dev mailing list archive at Nabble.com.
> > >>
> > >
> > >
> >
>

few java 9 jigsaw pointers and thoughts

[Romain Manni-Bucau]

Hey guys,

not sure anyone tried to run tomee on java 9 but wondered if j9 module
system was kind of "fixed" since it was really broken last time i tested
and tried to run our simple-singleton sample today.

Have to admit I tend to think it is a feature breaiking java ecosystem but
here is a few more pragmatic feedback and how we can make this module
running:

- (easy) ORB/corba is not exported by default so we need to check by
reflection we can access it or not, I guess the fix for us is to remove
corba reference from our codebase, AFAIK it is not used and no more needed.
- (medium) bytecode reading: our current code base can read until java 8
bytecode and we need to upgrade xbean-asm-shaded and xbean-finder-shaded
(xbean snapshot is ready). We also need to upgrade the finders we have in
our codebase to ASM6 (java 9) but nothing hurting a lot - that's what we do
for each new java version.
- (unknown) we need all our dependencies to upgrade
- (open and likely hard if it takes into account our full stack) to run the
simple-singleton example I needed to add jaxb dependency (alternative is to
activate the module) and open a few modules, typically:

--add-modules java.logging --add-opens
java.logging/java.util.logging=ALL-UNNAMED
--add-opens=java.base/java.lang=ALL-UNNAMED

This globally request to add to our code the missing permission in the JVM
(keep in mind i ran simple-singleton which doesnt cover much of our
codebase/stack). The issue is this option is on the JVM so we can hide it
in tomee in catalina scripts and in arquillian through RemoteServer but for
embedded tests we'll require the user to do it.

We can likely rework a bit our code to not require them all (some are easy
to workaround like the logging one or the GET_PACKAGE usage for @Vetoed)
but when we'll start to create a module-info.java ourself and our stack
we'll not just be in the unamed module merged but in several modules we'll
need to maintain these references exactly like we did when we were still
handling OSGi and even if maven helps a bit it breaks the ability to change
a little bit the stack (it was common to upgrade cxf for instance) since it
depends if cxf export is stable or not.

I'm not yet sure how we want to tackle it. Good news is "yes it will work".
Bad one is "yes it will mess up each version".

I fear jigsaw can't be removed from java 9 anymore (not sure why to be
honest) but I start to wonder if we should do a system (subclassloader?) to
completely bypass it and keep user experience smooth.

Anyone having some other feedback?

Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

Re: [VOTE] Apache TomEE 7.0.3

[Romain Manni-Bucau]

https://issues.apache.org/jira/browse/TOMEE-2022


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2017-03-11 13:38 GMT+01:00 Romain Manni-Bucau :

> no reason, missed it basically. feel free to open a ticket
>
>
> Romain Manni-Bucau
> @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> <https://blog-rmannibucau.rhcloud.com> | Old Blog
> <http://rmannibucau.wordpress.com> | Github
> <https://github.com/rmannibucau> | LinkedIn
> <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
> <https://javaeefactory-rmannibucau.rhcloud.com>
>
> 2017-03-10 23:22 GMT+01:00 cocorossello :
>
>> +1 (tested)
>>
>> Just wanted to ask if there is any reason to bundle myfaces 2.2.11, since
>> there is a 2.2.12 release (not that I need it anyway)
>>
>>
>>
>> --
>> View this message in context: http://tomee-openejb.979440.n4
>> .nabble.com/VOTE-Apache-TomEE-7-0-3-tp4681228p4681278.html
>> Sent from the TomEE Dev mailing list archive at Nabble.com.
>>
>
>

Re: [VOTE] Apache TomEE 7.0.3

[Romain Manni-Bucau]

no reason, missed it basically. feel free to open a ticket


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2017-03-10 23:22 GMT+01:00 cocorossello :

> +1 (tested)
>
> Just wanted to ask if there is any reason to bundle myfaces 2.2.11, since
> there is a 2.2.12 release (not that I need it anyway)
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.
> n4.nabble.com/VOTE-Apache-TomEE-7-0-3-tp4681228p4681278.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: [VOTE] Apache TomEE 7.0.3

[Romain Manni-Bucau]

Yep, but have to admit I was hoping they fix it since they don't have any
blocker for it. Note they have the same issue with a 2 scan passes fragile
workaround in wildfly. If you are motivated enough there is this long
thread dealing a bit with it on https://issues.jboss.org/browse/WFLY-2387
(note the solution doesnt work for cdi/jpa but makes things less
deterministic and if you add other specs it is worse :(). If you are in a
hurry check out https://hibernate.atlassian.net/browse/HHH-10477 and
https://hibernate.atlassian.net/browse/HHH-8706 which ares supposed to
solve the issue without requiring anything from our part except setting
hibernate.delay_cdi_access. Not yet sure why they don't set the default to
work. I'm tempted to say users should push on hibernate bugtracker to get
it fixed on the long term (set the setting to true by default instead of
false). But if it persist for too much versions we can set it ourself.


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2017-03-10 19:54 GMT+01:00 agumbrecht :

> Maybe it's possible where this is evaluated to make an attempt to detect
> hibernate and then set it automatically to true unless the property exists
> as false.
>
>
>
> -
> --
> Andy Gumbrecht
>
> http://www.tomitribe.com
> agumbre...@tomitribe.com
> https://twitter.com/AndyGeeDe
>
> TomEE treibt Tomitribe ! | http://tomee.apache.org
> --
> View this message in context: http://tomee-openejb.979440.
> n4.nabble.com/VOTE-Apache-TomEE-7-0-3-tp4681228p4681276.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: [VOTE] Apache TomEE 7.0.3

[Romain Manni-Bucau]

cause it is breaking the compat even if fine in 90% of the apps
instantiating the EMF after cdi. You can need JPA before CDI or CDI after
JPA, both cases are valid and we can't handle both


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2017-03-10 19:17 GMT+01:00 Andy Gumbrecht :

> If this is the case, why is tomee.jpa.factory.lazy=tue not the default?
> I'm guessing this will be an issue for anyone using hibernate.
>
> Andy.
>
>
>
> On 08/03/2017 20:22, DonatasCiuksys wrote:
>
>> Yes, with property tomee.jpa.factory.lazy=true it started to work.
>> Thank you very much, Adam!
>>
>>
>>
>> --
>> View this message in context: http://tomee-openejb.979440.n4
>> .nabble.com/VOTE-Apache-TomEE-7-0-3-tp4681228p4681238.html
>> Sent from the TomEE Dev mailing list archive at Nabble.com.
>>
>
> --
>   Andy Gumbrecht
>   https://twitter.com/AndyGeeDe
>   http://www.tomitribe.com
>
>

Re: TomEE Documentation Suggestion

[Romain Manni-Bucau]

BTW added a word on the website on the website:
http://tomee.apache.org/community/index.html


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2017-03-10 13:10 GMT+01:00 Romain Manni-Bucau :

>
>
> Le 10 mars 2017 13:04, "Ivan Junckes Filho"  a
> écrit :
>
> I did start writing stuff, but was doing in the html. Seems that I was
> doing wrong because it is unclear how to do it.
>
>
> Clearly not the way, can add a page on the how to help.
>
>
> I consider even this email a contribution btw, discussing possible ways to
> improve it is a good start to better things.
>
> If we don't have an integration and a way to do PR's at the moment I think
> we should fix that. Having it in a personal github account is not ideal.
>
>
> We dont, just proposed it from there.
>
>
>
>
> Even though I respect your opinion I still would like to hear more
> thoughts.
>
> Thank you.
>
>
>
>
>
>
> On Fri, Mar 10, 2017 at 8:44 AM, Romain Manni-Bucau  >
> wrote:
>
> > 2017-03-10 12:38 GMT+01:00 Ivan Junckes Filho :
> >
> > > As far as I understood JBake is a tool to generate websites (deal with
> > > html, css etc.), what I am proposing is a tool to make the
> documentation
> > > process friendly without caring with html, css, website structure etc.
> > >
> > >
> > Yes but point of using jbake is to be adoc based. You don't care about
> the
> > css, html etc... using it, was one of the criteria.
> >
> >
> > > We don't need to remove JBake from the website, but for documentation,
> we
> > > can use a tool that is proven to work and make it simple.
> > >
> > >
> > Matches jbake definition to be honest.
> >
> >
> > > I don't know where SEO has anything to do with this sorry, but the
> > content
> > > in gitbook is indexed on google if that it what you mean.
> > >
> > >
> > Search Engine Optimization, google integration if you pefer ;)
> >
> >
> > > Well, just my suggestion, I was willing to help on that.
> > >
> > >
> > Did you try contributing on current website - sounds like not? assume we
> > have a github proxy and you can do a PR, do you miss really anything? You
> > can *test* (it isoutdated now but to test it is ok, or if you want i can
> > sync it up for testing purposes) on
> > https://github.com/rmannibucau/site-tomee-ng
> >
> > gitbook gain is mainly about the infra and @ASF we have it provided with
> > standard choices so only the tool and interactions are the remaining
> parts
> > and jbake matches all your criteria for the tool and we can make github
> > integrated so really not seeing what could miss and justify yet another
> > switch.
> >
> >
> > > I would like to hear more thoughts from other developers if possible.
> > >
> > > Thank you.
> > >
> > >
> > >
> > > On Fri, Mar 10, 2017 at 8:10 AM, Romain Manni-Bucau <
> > rmannibu...@gmail.com
> > > >
> > > wrote:
> > >
> > > > 2017-03-10 12:02 GMT+01:00 Ivan Junckes Filho  >:
> > > >
> > > > > Hi guys, thank you for the feedback.
> > > > >
> > > > > What would bring gitbook which would make it better we don't have
> > > > already?
> > > > > 1 - Documentation is a very tough thing to keep up to date, so we
> > don't
> > > > > want to make it hard for people to do it. What I see in gitbook is
> a
> > > very
> > > > > straightforward way to update it and make it organized regardless
> of
> > a
> > > > > website.
> > > > >
> > > >
> > > > Can you go one step further and say how compared to what we have it
> > will
> > > > help (it is the same kind of infra).
> > > >
> > > >
> > > > > 2 - We'll have a tool that is specialized in this, websites need to
> > be
> > > > > redesigned over time and we don't want to be worrying about
> migrating
> > > all
> > > > > the docs like we need to do now, from the old to the new.
> > > > >
> > > >
> > > > JBake as 

Re: TomEE Documentation Suggestion

[Romain Manni-Bucau]

Le 10 mars 2017 13:04, "Ivan Junckes Filho"  a
écrit :

I did start writing stuff, but was doing in the html. Seems that I was
doing wrong because it is unclear how to do it.


Clearly not the way, can add a page on the how to help.


I consider even this email a contribution btw, discussing possible ways to
improve it is a good start to better things.

If we don't have an integration and a way to do PR's at the moment I think
we should fix that. Having it in a personal github account is not ideal.


We dont, just proposed it from there.




Even though I respect your opinion I still would like to hear more thoughts.

Thank you.






On Fri, Mar 10, 2017 at 8:44 AM, Romain Manni-Bucau 
wrote:

> 2017-03-10 12:38 GMT+01:00 Ivan Junckes Filho :
>
> > As far as I understood JBake is a tool to generate websites (deal with
> > html, css etc.), what I am proposing is a tool to make the documentation
> > process friendly without caring with html, css, website structure etc.
> >
> >
> Yes but point of using jbake is to be adoc based. You don't care about the
> css, html etc... using it, was one of the criteria.
>
>
> > We don't need to remove JBake from the website, but for documentation,
we
> > can use a tool that is proven to work and make it simple.
> >
> >
> Matches jbake definition to be honest.
>
>
> > I don't know where SEO has anything to do with this sorry, but the
> content
> > in gitbook is indexed on google if that it what you mean.
> >
> >
> Search Engine Optimization, google integration if you pefer ;)
>
>
> > Well, just my suggestion, I was willing to help on that.
> >
> >
> Did you try contributing on current website - sounds like not? assume we
> have a github proxy and you can do a PR, do you miss really anything? You
> can *test* (it isoutdated now but to test it is ok, or if you want i can
> sync it up for testing purposes) on
> https://github.com/rmannibucau/site-tomee-ng
>
> gitbook gain is mainly about the infra and @ASF we have it provided with
> standard choices so only the tool and interactions are the remaining parts
> and jbake matches all your criteria for the tool and we can make github
> integrated so really not seeing what could miss and justify yet another
> switch.
>
>
> > I would like to hear more thoughts from other developers if possible.
> >
> > Thank you.
> >
> >
> >
> > On Fri, Mar 10, 2017 at 8:10 AM, Romain Manni-Bucau <
> rmannibu...@gmail.com
> > >
> > wrote:
> >
> > > 2017-03-10 12:02 GMT+01:00 Ivan Junckes Filho :
> > >
> > > > Hi guys, thank you for the feedback.
> > > >
> > > > What would bring gitbook which would make it better we don't have
> > > already?
> > > > 1 - Documentation is a very tough thing to keep up to date, so we
> don't
> > > > want to make it hard for people to do it. What I see in gitbook is a
> > very
> > > > straightforward way to update it and make it organized regardless of
> a
> > > > website.
> > > >
> > >
> > > Can you go one step further and say how compared to what we have it
> will
> > > help (it is the same kind of infra).
> > >
> > >
> > > > 2 - We'll have a tool that is specialized in this, websites need to
> be
> > > > redesigned over time and we don't want to be worrying about
migrating
> > all
> > > > the docs like we need to do now, from the old to the new.
> > > >
> > >
> > > JBake as well so once again not sure the gain
> > >
> > >
> > > > 3 - The tool is completely integrated with github, we'll have a
> project
> > > > inside the github with folders that we could even separate per
> > language,
> > > > would be useful for example if someone with time could go there and
> > > create
> > > > a french folder and translate the docs.
> > > >
> > >
> > > Here again we can do it with jbake but have to admit I wonder if this
> > > someone exist after all the round trips and tries we got on the doc so
> I
> > > would prefer to take the opposite approad: if someone asks to
translate
> > the
> > > whole website we'll ensure it is setup than setting it up to nothing
> now.
> > >
> > >
> > > > 4 - We can easily have doc versioning, and make sure from now on
when
> > we
> > > > have a new feature we add it to the doc.
> > > >
> > >
> > > We can but dec

Re: TomEE Documentation Suggestion

[Romain Manni-Bucau]

2017-03-10 12:38 GMT+01:00 Ivan Junckes Filho :

> As far as I understood JBake is a tool to generate websites (deal with
> html, css etc.), what I am proposing is a tool to make the documentation
> process friendly without caring with html, css, website structure etc.
>
>
Yes but point of using jbake is to be adoc based. You don't care about the
css, html etc... using it, was one of the criteria.


> We don't need to remove JBake from the website, but for documentation, we
> can use a tool that is proven to work and make it simple.
>
>
Matches jbake definition to be honest.


> I don't know where SEO has anything to do with this sorry, but the content
> in gitbook is indexed on google if that it what you mean.
>
>
Search Engine Optimization, google integration if you pefer ;)


> Well, just my suggestion, I was willing to help on that.
>
>
Did you try contributing on current website - sounds like not? assume we
have a github proxy and you can do a PR, do you miss really anything? You
can *test* (it isoutdated now but to test it is ok, or if you want i can
sync it up for testing purposes) on
https://github.com/rmannibucau/site-tomee-ng

gitbook gain is mainly about the infra and @ASF we have it provided with
standard choices so only the tool and interactions are the remaining parts
and jbake matches all your criteria for the tool and we can make github
integrated so really not seeing what could miss and justify yet another
switch.


> I would like to hear more thoughts from other developers if possible.
>
> Thank you.
>
>
>
> On Fri, Mar 10, 2017 at 8:10 AM, Romain Manni-Bucau  >
> wrote:
>
> > 2017-03-10 12:02 GMT+01:00 Ivan Junckes Filho :
> >
> > > Hi guys, thank you for the feedback.
> > >
> > > What would bring gitbook which would make it better we don't have
> > already?
> > > 1 - Documentation is a very tough thing to keep up to date, so we don't
> > > want to make it hard for people to do it. What I see in gitbook is a
> very
> > > straightforward way to update it and make it organized regardless of a
> > > website.
> > >
> >
> > Can you go one step further and say how compared to what we have it will
> > help (it is the same kind of infra).
> >
> >
> > > 2 - We'll have a tool that is specialized in this, websites need to be
> > > redesigned over time and we don't want to be worrying about migrating
> all
> > > the docs like we need to do now, from the old to the new.
> > >
> >
> > JBake as well so once again not sure the gain
> >
> >
> > > 3 - The tool is completely integrated with github, we'll have a project
> > > inside the github with folders that we could even separate per
> language,
> > > would be useful for example if someone with time could go there and
> > create
> > > a french folder and translate the docs.
> > >
> >
> > Here again we can do it with jbake but have to admit I wonder if this
> > someone exist after all the round trips and tries we got on the doc so I
> > would prefer to take the opposite approad: if someone asks to translate
> the
> > whole website we'll ensure it is setup than setting it up to nothing now.
> >
> >
> > > 4 - We can easily have doc versioning, and make sure from now on when
> we
> > > have a new feature we add it to the doc.
> > >
> >
> > We can but decided to not do it cause majors arent really breaking.
> >
> >
> > > 5 - Authoring is tracked by github itself and can be shared just like
> > code
> > >
> >
> > Same with svn today and once again no blocker to have a proxy on github.
> >
> >
> > > 6 - Tool is based on .md (markdown) not html
> > >
> >
> > adoc so better no? ;)
> >
> >
> > > 7 - Maybe a straightforward way without learning curve can make people
> > > start contributing?
> > >
> > >
> > Learning curve for gitbook ~= jbake I think so not sure.
> >
> >
> > > Imagine this scenario:
> > > Let's say I am an application developer that uses TomEE and I learned
> > > something about it that is not clear in the docs. I don't want to learn
> > the
> > > whole website thing (structure) etc, I just want to write it and send
> it
> > in
> > > an easy manner. This way seems pretty easy in my opinion.
> > >
> > > We need to make the environment welcoming if we want to improve this
> > guys!
> > >
> > > These 2 JavaEE servers have some documentation a

Re: TomEE Documentation Suggestion

[Romain Manni-Bucau]

2017-03-10 12:02 GMT+01:00 Ivan Junckes Filho :

> Hi guys, thank you for the feedback.
>
> What would bring gitbook which would make it better we don't have already?
> 1 - Documentation is a very tough thing to keep up to date, so we don't
> want to make it hard for people to do it. What I see in gitbook is a very
> straightforward way to update it and make it organized regardless of a
> website.
>

Can you go one step further and say how compared to what we have it will
help (it is the same kind of infra).


> 2 - We'll have a tool that is specialized in this, websites need to be
> redesigned over time and we don't want to be worrying about migrating all
> the docs like we need to do now, from the old to the new.
>

JBake as well so once again not sure the gain


> 3 - The tool is completely integrated with github, we'll have a project
> inside the github with folders that we could even separate per language,
> would be useful for example if someone with time could go there and create
> a french folder and translate the docs.
>

Here again we can do it with jbake but have to admit I wonder if this
someone exist after all the round trips and tries we got on the doc so I
would prefer to take the opposite approad: if someone asks to translate the
whole website we'll ensure it is setup than setting it up to nothing now.


> 4 - We can easily have doc versioning, and make sure from now on when we
> have a new feature we add it to the doc.
>

We can but decided to not do it cause majors arent really breaking.


> 5 - Authoring is tracked by github itself and can be shared just like code
>

Same with svn today and once again no blocker to have a proxy on github.


> 6 - Tool is based on .md (markdown) not html
>

adoc so better no? ;)


> 7 - Maybe a straightforward way without learning curve can make people
> start contributing?
>
>
Learning curve for gitbook ~= jbake I think so not sure.


> Imagine this scenario:
> Let's say I am an application developer that uses TomEE and I learned
> something about it that is not clear in the docs. I don't want to learn the
> whole website thing (structure) etc, I just want to write it and send it in
> an easy manner. This way seems pretty easy in my opinion.
>
> We need to make the environment welcoming if we want to improve this guys!
>
> These 2 JavaEE servers have some documentation and they don't keep on a
> website, they use tools very similar to what I am proposing.
>
> Wildfly documentation
> https://docs.jboss.org/author/display/WFLY10/Documentation
>
> Payara documentation
> https://payara.gitbooks.io/payara-server/content/?
> hsCtaTracking=8a4f0637-38ea-458c-a66c-6307d6f21923%
> 7C26bb561b-3f60-4d3b-b64d-06398f00d8e2&__hstc=229474563.
> 6de427338f64d2f474c236a686036ee9.1489142671622.
> 1489142671622.1489142671622.1&__hssc=229474563.1.1489142671623&__hsfp=
> 2299569188
>
> Even though I agree content is more important than tools, I think tools
> help greatly if we choose the right ones, and they can avoid rework which I
> am sure nobody wants to do if not necessary.
>
>
So globally does your feedback means we need to proxy the website content
on github and maybe enhance the SEO?


>
> On Fri, Mar 10, 2017 at 5:00 AM, Romain Manni-Bucau  >
> wrote:
>
> > 2017-03-10 3:16 GMT+01:00 Thomas Whitmore  com
> > >:
> >
> > > Hi Romain, Ivan,
> > >
> > > I agree with Romain and raised the suggestion of improving doc a month
> or
> > > two ago. At the time I offered a few hours to help -- am probably busy
> > for
> > > another month now but do see documentation as an important factor.
> > >
> > > My feeling would be that content is more important than tools -- I
> would
> > > see a librarian exercise to collect relevant docs and make them
> > accessible
> > > from the new site, as the most relevant. This I believe would give the
> > most
> > > easy and worthwhile improvement.
> > >
> > > My suggestion to move forward:
> > > - collate docs from "old" openejb.apache.org site;  get these reviewed
> > > and edit to remove outdated material.
> > > - reviewing/ marking of what's outdated & what can be corrected
> > to
> > > be delegated to appropriate people.
> > > - make all docs accessible from Documentation areas on new
> > > tomee.apache.org site;
> > > - collect prioritized suggestions as to what documentation gaps remain.
> > > - (probably also)  for those who found the old site by accident, add
> > links
> > > from old site to new Documentation areas on tomee.apache.o

Re: TomEE Documentation Suggestion

[Romain Manni-Bucau]

2017-03-10 3:16 GMT+01:00 Thomas Whitmore :

> Hi Romain, Ivan,
>
> I agree with Romain and raised the suggestion of improving doc a month or
> two ago. At the time I offered a few hours to help -- am probably busy for
> another month now but do see documentation as an important factor.
>
> My feeling would be that content is more important than tools -- I would
> see a librarian exercise to collect relevant docs and make them accessible
> from the new site, as the most relevant. This I believe would give the most
> easy and worthwhile improvement.
>
> My suggestion to move forward:
> - collate docs from "old" openejb.apache.org site;  get these reviewed
> and edit to remove outdated material.
> - reviewing/ marking of what's outdated & what can be corrected to
> be delegated to appropriate people.
> - make all docs accessible from Documentation areas on new
> tomee.apache.org site;
> - collect prioritized suggestions as to what documentation gaps remain.
> - (probably also)  for those who found the old site by accident, add links
> from old site to new Documentation areas on tomee.apache.org site.
>
> This should make it possible to cheaply & easily gather all useful
> material from existing docs, consolidate the docs, and produce a shortlist
> of doc to fill in.
>
> However I did look at Gitbook (www.gitbook.com) and it looks quite
> interesting. How is the website/ documentation maintained at the moment?
> Would a tool like Gitbook enable better shared authoring or make content
> writing easier (eg rich text editor, not raw HTML)? These are interesting
> questions. It might also be possible to use gitbook to share writing, then
> upload resulting HTML to an existing website repo if that's how website is
> maintained at the moment. See https://docs.duckduckhack.com/ for an
> example of Gitbook-produced docs.
>
>
we use a jbake site (
http://svn.apache.org/repos/asf/tomee/site/trunk/generators/site-tomee-ng/src/main/jbake/
- development with tomee itself ;))  the we just sync with site content
http://svn.apache.org/repos/asf/tomee/site/trunk/content/ and push through
ASF mecanism ("CMS") which is basically a svn deployed on a click. Nice
thing of that tooling is the autostaging mode so you have a site preview
before the prod one.

So concretely we are in managed and public so already shareable. If github
is better we can sync with github like tomee itself, that's a detail. And
we are adoc so github would just bring another structure but if you check
we already have one. The search is interesting and I guess we'll need to
add a kind of client search at build time or just use google.




> I would suggest that TomEE as a project is technically nice, but
> documentation may be holding it back. People on the mailing list are great
> & very helpful and willing to answer questions, but I would believe that
> providing this material as findable written documentation on the current
> (new) website is important, as documentation is one of the #1 things people
> consider when considering a platform.
>
>
> Regards,
> Thomas
>
> -Original Message-
> From: Romain Manni-Bucau [mailto:rmannibu...@gmail.com]
> Sent: Friday, 10 March 2017 1:37 PM
> To: dev@tomee.apache.org
> Subject: Re: TomEE Documentation Suggestion
>
> Hi Ivan,
>
> we just revamped the website with a new structure, I know it is not
> perfect but a step to something better. Tooling is also way easier now to
> get started with. So question is: what would bring gitbook which would make
> it better we don't have already? If github we can ask infra to proxy our
> site repo on ASF github org.
>
>
> Romain Manni-Bucau
> @rmannibucau <https://twitter.com/rmannibucau> |  Blog <
> https://blog-rmannibucau.rhcloud.com> | Old Blog <
> http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau>
> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory <
> https://javaeefactory-rmannibucau.rhcloud.com>
>
> 2017-03-10 1:14 GMT+01:00 Ivan Junckes Filho :
>
> > Hello TomEE developers,
> >
> > Today TomEE documentation is spread across multiple places, some are
> > not up to date anymore and some are just really hard to find on the
> > website. It is easier to find something on google than on
> http://tomee.apache.org.
> >
> > I would like to suggest that TomEE uses www.gitbook.com, and we
> > migrate there the relevant documentation. Updating a website with doc
> > is ok, but I think it will make the job way easier and will open the
> > gates for contributors.
>
> __
> This email has been scanned by the Symantec Email Security.cloud service.
> For more information please visit http://www.symanteccloud.com
> __
>

Re: TomEE Documentation Suggestion

[Romain Manni-Bucau]

Hi Ivan,

we just revamped the website with a new structure, I know it is not perfect
but a step to something better. Tooling is also way easier now to get
started with. So question is: what would bring gitbook which would make it
better we don't have already? If github we can ask infra to proxy our site
repo on ASF github org.


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2017-03-10 1:14 GMT+01:00 Ivan Junckes Filho :

> Hello TomEE developers,
>
> Today TomEE documentation is spread across multiple places, some are not up
> to date anymore and some are just really hard to find on the website. It is
> easier to find something on google than on http://tomee.apache.org.
>
> I would like to suggest that TomEE uses www.gitbook.com, and we migrate
> there the relevant documentation. Updating a website with doc is ok, but I
> think it will make the job way easier and will open the gates for
> contributors.
>
> All of us here are interested in TomEE documentation to get better and I
> think that is a good start, we will not need to keep updating the website,
> maintain pages etc we'll just need to use centralized tool.
>
> Please let me know your thoughts.
>
> Please see JNoSQL documentation as a reference:
> https://www.gitbook.com/book/jnosql/jnosql-book/details
> https://github.com/jnoSQL/jnosql-book
>
> Thank you.
>
> +1? -1?
>

Re: PR to remove dead code

[Romain Manni-Bucau]

Hi Ivan, thanks for the PR, applied


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2017-03-10 0:35 GMT+01:00 Ivan Junckes Filho :

> Hi guys, there is a dead code in TomEE. Probably a copy paste issue, could
> you please merge it?
>
> https://github.com/apache/tomee/pull/61
>

Re: [VOTE] Apache TomEE 7.0.3

[Romain Manni-Bucau]

This is already in 7.0.2 and there is a property to avoid this issue. This
is due to a chicken-egg problem and triggered by fixing CDI/JPA integration
in 7.0.2 (was a bug before).


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2017-03-08 14:19 GMT+01:00 DonatasCiuksys :

> Previous versions (7.0.0-M1 etc) allowed to replace OpenJPA by Hibernate
> (by
> putting Hibernate libraries to lib and setting "javax.persistence.provider"
> property in system.properties).
> Now tomee fails during startup:
>
> Caused by: javax.persistence.PersistenceException: [PersistenceUnit:
> StudentsPU] Unable to build Hibernate SessionFactory
> at
> org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImp
> l.persistenceException(EntityManagerFactoryBuilderImpl.java:954)
> at
> org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(
> EntityManagerFactoryBuilderImpl.java:882)
> at
> org.hibernate.jpa.HibernatePersistenceProvider.
> createContainerEntityManagerFactory(HibernatePersistenceProvider.java:135)
> at
> org.apache.openejb.assembler.classic.EntityManagerFactoryCallable.call(
> EntityManagerFactoryCallable.java:122)
> at
> org.apache.openejb.assembler.classic.ReloadableEntityManagerFactory
> .createDelegate(ReloadableEntityManagerFactory.java:134)
> ... 68 more
> Caused by: org.hibernate.HibernateException: Could not access BeanManager
> ListenerFactory class
> [org.hibernate.jpa.event.internal.jpa.ListenerFactoryBeanManagerStan
> dardImpl]
> to handle CDI extensions
> at
> org.hibernate.jpa.event.spi.jpa.ListenerFactoryBuilder.
> buildBeanManagerListenerFactory(ListenerFactoryBuilder.java:88)
> at
> org.hibernate.jpa.event.spi.jpa.ListenerFactoryBuilder.
> buildStandardBeanManagerListenerFactory(ListenerFactoryBuilder.java:51)
> at
> org.hibernate.jpa.event.spi.jpa.ListenerFactoryBuilder.
> buildListenerFactory(ListenerFactoryBuilder.java:39)
> at
> org.hibernate.jpa.event.spi.JpaIntegrator.integrate(
> JpaIntegrator.java:129)
> at
> org.hibernate.internal.SessionFactoryImpl.(
> SessionFactoryImpl.java:280)
> at
> org.hibernate.boot.internal.SessionFactoryBuilderImpl.build(
> SessionFactoryBuilderImpl.java:444)
> at
> org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(
> EntityManagerFactoryBuilderImpl.java:879)
> ... 71 more
> Caused by: java.lang.IllegalStateException: On a thread without an
> initialized context nor a classloader mapping a deployed app
> at
> org.apache.openejb.cdi.ThreadSingletonServiceImpl.get(
> ThreadSingletonServiceImpl.java:287)
> at
> org.apache.openejb.cdi.ThreadSingletonServiceImpl.getContext(
> ThreadSingletonServiceImpl.java:263)
> at
> org.apache.openejb.cdi.ThreadSingletonServiceImpl.get(
> ThreadSingletonServiceImpl.java:298)
> at
> org.apache.openejb.cdi.ThreadSingletonServiceImpl.get(
> ThreadSingletonServiceImpl.java:60)
> at
> org.apache.webbeans.config.WebBeansFinder.getSingletonInstance(
> WebBeansFinder.java:51)
> at
> org.apache.webbeans.config.WebBeansContext.getInstance(
> WebBeansContext.java:185)
> at
> org.apache.webbeans.config.WebBeansContext.currentInstance(
> WebBeansContext.java:203)
> at
> org.apache.openejb.assembler.classic.EntityManagerFactoryCallable$
> 1.findBm(EntityManagerFactoryCallable.java:105)
> at
> org.apache.openejb.assembler.classic.EntityManagerFactoryCallable$
> 1.invoke(EntityManagerFactoryCallable.java:96)
> at com.sun.proxy.$Proxy99.toString(Unknown Source)
> at java.lang.String.valueOf(String.java:2994)
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.
> n4.nabble.com/VOTE-Apache-TomEE-7-0-3-tp4681228p4681234.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: [VOTE] Apache TomEE 7.0.3

[Romain Manni-Bucau]

i sent it to the list on the commit thread that it was not needed and
leading to close twice the pool which is an issue so just wrapped it in a
finally (other parts of the commit were introducing regressions as
explained in the thread).

Since we start to lock the pool the race condition shouldnt occur there but
there was a little chance under start[abrupt ctrl+x] case to not close
properly the pool so added a finally. Also this method is not intended to
be used in a concurrent environment (actually issue would be higher level
if you underploy concurrently the same app which is more than unlikely. It
is an undeploy method bound to one bean so no supported concurrency there -
except in tests?).

Anyway since it is there since > 5 years and not causing any security issue
it is not a cancel reason I think.



Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2017-03-08 11:10 GMT+01:00 Andy Gumbrecht :

> -1
>
> https://github.com/rmannibucau/tomee/commit/55d6d5ec89da68a6794487bc75f95b
> 55cad7b483
>
> Not sure why the public boolean close(final long timeout, final TimeUnit
> unit) throws InterruptedException { method doesn't look like this one in
> 1.7.x?:
> https://github.com/apache/tomee/blob/tomee-1.7.x/
> container/openejb-core/src/main/java/org/apache/openejb/util/Pool.java
> - Was pretty sure I checked it in on master too. Looks like an older commit
> and not the last one I have? My fault, as I guess I didn't push to master.
>
> The stop() method also needs to be called before draining (in the close
> method), else there is a potential race.
>
> The atomics must be set to null on stop(), so getAndSet is better as it is
> a single atomic action rather than two (get, compare = 4 locks in total).
>
> Basically the tomee-1.7.x Pool stop() and close() methods are correct and
> tested (also on site), and can be forwarded to master. I won't be able to
> fix master till I get home tonight, so if someone could compare the
> tomee-1.7.x methods and update master that would be cool.
>
> Andy.
>
>
> On 8 March 2017 at 08:32, Romain Manni-Bucau 
> wrote:
>
> > Hi guys,
> >
> > as discussed on the list here is the vote for 7.0.3. It is mainly
> > dependencies upgrades and a few fixes.
> >
> > Staging repo:
> > https://repository.apache.org/content/repositories/orgapachetomee-1104/
> > Source zip:
> > https://repository.apache.org/content/repositories/
> > orgapachetomee-1104/org/apache/tomee/tomee-project/7.
> > 0.3/tomee-project-7.0.3-source-release.zip
> > Dist area: https://dist.apache.org/repos/dist/dev/tomee/7.0.3/
> > Changelog:
> > https://issues.apache.org/jira/browse/TOMEE-2018?jql=
> > project%20%3D%20TOMEE%20AND%20fixVersion%20%3D%207.0.3%
> > 20AND%20(resolution%20%3D%20Resolved%20OR%20resolution%20%3D%20Fixed)
> > Green buildbot:
> > https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/603
> > Branch: https://github.com/rmannibucau/tomee/tree/release/7.0.3
> >
> > Please vote:
> > - +1: it rocks, release it
> > - +-0: why do you bother me?
> > - -1 don't release it cause ${blocker}
> >
> > As usual vote will be open for 3 days or until we get 3 +1 bindings and
> no
> > -1. Anyone is welcomed to vote!
> >
> > Romain Manni-Bucau
> > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > <https://blog-rmannibucau.rhcloud.com> | Old Blog
> > <http://rmannibucau.wordpress.com> | Github <https://github.com/
> > rmannibucau> |
> > LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
> > <https://javaeefactory-rmannibucau.rhcloud.com>
> >
>
>
>
> --
>   Andy Gumbrecht
>   https://twitter.com/AndyGeeDe
>   http://www.tomitribe.com
>

Re: [VOTE] Apache TomEE 7.0.3

[Romain Manni-Bucau]

+1 from me as well


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2017-03-08 11:22 GMT+01:00 Mark Struberg :

>
> * sig fine
> * sha1 and md5 ok
> * source builds fine
> * rat check passes
> * LICENSE and NOTICE ok for 5 jars and zips I checked
> * LICENSE and NOTICE ok for the source distributable
> * tested in 2 big world projects without any glitches.
>
> +1
>
>
> txs and LieGrue,
> strub
>
>
> > Am 08.03.2017 um 08:32 schrieb Romain Manni-Bucau  >:
> >
> > Hi guys,
> >
> > as discussed on the list here is the vote for 7.0.3. It is mainly
> > dependencies upgrades and a few fixes.
> >
> > Staging repo:
> > https://repository.apache.org/content/repositories/orgapachetomee-1104/
> > Source zip:
> > https://repository.apache.org/content/repositories/
> orgapachetomee-1104/org/apache/tomee/tomee-project/7.
> 0.3/tomee-project-7.0.3-source-release.zip
> > Dist area: https://dist.apache.org/repos/dist/dev/tomee/7.0.3/
> > Changelog:
> > https://issues.apache.org/jira/browse/TOMEE-2018?jql=
> project%20%3D%20TOMEE%20AND%20fixVersion%20%3D%207.0.3%
> 20AND%20(resolution%20%3D%20Resolved%20OR%20resolution%20%3D%20Fixed)
> > Green buildbot:
> > https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/603
> > Branch: https://github.com/rmannibucau/tomee/tree/release/7.0.3
> >
> > Please vote:
> > - +1: it rocks, release it
> > - +-0: why do you bother me?
> > - -1 don't release it cause ${blocker}
> >
> > As usual vote will be open for 3 days or until we get 3 +1 bindings and
> no
> > -1. Anyone is welcomed to vote!
> >
> > Romain Manni-Bucau
> > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > <https://blog-rmannibucau.rhcloud.com> | Old Blog
> > <http://rmannibucau.wordpress.com> | Github <https://github.com/
> rmannibucau> |
> > LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
> > <https://javaeefactory-rmannibucau.rhcloud.com>
>
>

[VOTE] Apache TomEE 7.0.3

[Romain Manni-Bucau]

Hi guys,

as discussed on the list here is the vote for 7.0.3. It is mainly
dependencies upgrades and a few fixes.

Staging repo:
https://repository.apache.org/content/repositories/orgapachetomee-1104/
Source zip:
https://repository.apache.org/content/repositories/orgapachetomee-1104/org/apache/tomee/tomee-project/7.0.3/tomee-project-7.0.3-source-release.zip
Dist area: https://dist.apache.org/repos/dist/dev/tomee/7.0.3/
Changelog:
https://issues.apache.org/jira/browse/TOMEE-2018?jql=project%20%3D%20TOMEE%20AND%20fixVersion%20%3D%207.0.3%20AND%20(resolution%20%3D%20Resolved%20OR%20resolution%20%3D%20Fixed)
Green buildbot:
https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/603
Branch: https://github.com/rmannibucau/tomee/tree/release/7.0.3

Please vote:
- +1: it rocks, release it
- +-0: why do you bother me?
- -1 don't release it cause ${blocker}

As usual vote will be open for 3 days or until we get 3 +1 bindings and no
-1. Anyone is welcomed to vote!

Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

Re: [3/3] tomee git commit: Check for null and clean WebBeansContext later

[Romain Manni-Bucau]

confirming, unbinding before cdi destruction prevent to use cdi/EE
integration properly, will revert


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2017-03-03 21:59 GMT+01:00 Romain Manni-Bucau :

> Null checks should be reverted please as said on the list.
>
> About the critical part of the diff can you say a word here why it is
> needed? War and ear behave differently and i fear now we can break some
> working undeployments so trying to avoid to break it for the 7.0.3 - we
> were quite stable and close to release.
>
> -- Message transféré --
> De : 
> Date : 3 mars 2017 21:25
> Objet : [3/3] tomee git commit: Check for null and clean WebBeansContext
> later
> À : 
> Cc :
>
> Check for null and clean WebBeansContext later
>>
>>
>> Project: http://git-wip-us.apache.org/repos/asf/tomee/repo
>> Commit: http://git-wip-us.apache.org/repos/asf/tomee/commit/9b7b4657
>> Tree: http://git-wip-us.apache.org/repos/asf/tomee/tree/9b7b4657
>> Diff: http://git-wip-us.apache.org/repos/asf/tomee/diff/9b7b4657
>>
>> Branch: refs/heads/master
>> Commit: 9b7b46570cf43afa9bb904e1615794400124539a
>> Parents: de09ee0
>> Author: AndyGee 
>> Authored: Fri Mar 3 21:24:42 2017 +0100
>> Committer: AndyGee 
>> Committed: Fri Mar 3 21:24:42 2017 +0100
>>
>> --
>>  .../openejb/assembler/classic/Assembler.java| 166
>> ++-
>>  1 file changed, 85 insertions(+), 81 deletions(-)
>> --
>>
>>
>> http://git-wip-us.apache.org/repos/asf/tomee/blob/9b7b4657/c
>> ontainer/openejb-core/src/main/java/org/apache/openejb/assem
>> bler/classic/Assembler.java
>> --
>> diff --git 
>> a/container/openejb-core/src/main/java/org/apache/openejb/assembler/classic/Assembler.java
>> b/container/openejb-core/src/main/java/org/apache/openejb/as
>> sembler/classic/Assembler.java
>> index cdf7ed2..9af8153 100644
>> --- a/container/openejb-core/src/main/java/org/apache/openejb/as
>> sembler/classic/Assembler.java
>> +++ b/container/openejb-core/src/main/java/org/apache/openejb/as
>> sembler/classic/Assembler.java
>> @@ -377,8 +377,8 @@ public class Assembler extends AssemblerTool
>> implements org.apache.openejb.spi.A
>>  final Object filter = loader.loadClass("org.apache.o
>> penejb.bval.BValCdiFilter").newInstance();
>>  loader.loadClass("org.apache.bval.cdi.BValExtension")
>>  .getMethod(
>> -"setAnnotatedTypeFilter",
>> -loader.loadClass("org.apache.b
>> val.cdi.BValExtension$AnnotatedTypeFilter"))
>> +"setAnnotatedTypeFilter",
>> +loader.loadClass("org.apache.b
>> val.cdi.BValExtension$AnnotatedTypeFilter"))
>>  .invoke(null, filter);
>>  } catch (final Throwable th) {
>>  // ignore, bval not compatible or not present
>> @@ -579,7 +579,7 @@ public class Assembler extends AssemblerTool
>> implements org.apache.openejb.spi.A
>>  final ContainerSystem component = systemInstance.getComponent(Co
>> ntainerSystem.class);
>>  if (component != null) {
>>  postConstructResources(rIds, 
>> ParentClassLoaderFinder.Helper.get(),
>> component.getJNDIContext(), null);
>> -}else{
>> +} else {
>>  throw new RuntimeException("ContainerSystem has not been
>> initialzed");
>>  }
>>
>> @@ -1320,8 +1320,8 @@ public class Assembler extends AssemblerTool
>> implements org.apache.openejb.spi.A
>>
>>  private static List 
>> listCommonInfoObjectsForAppInfo(final
>> AppInfo appInfo) {
>>  final List vfs = new
>> ArrayList(
>> -appInfo.clients.size() + appInfo.connectors.size() +
>> -appInfo.ejbJars.size() + appInfo.webApps.size());
>> +appInfo.clients.size() + appInfo.connectors.size() +
>> +   

Fwd: [3/3] tomee git commit: Check for null and clean WebBeansContext later

[Romain Manni-Bucau]

Null checks should be reverted please as said on the list.

About the critical part of the diff can you say a word here why it is
needed? War and ear behave differently and i fear now we can break some
working undeployments so trying to avoid to break it for the 7.0.3 - we
were quite stable and close to release.

-- Message transféré --
De : 
Date : 3 mars 2017 21:25
Objet : [3/3] tomee git commit: Check for null and clean WebBeansContext
later
À : 
Cc :

Check for null and clean WebBeansContext later
>
>
> Project: http://git-wip-us.apache.org/repos/asf/tomee/repo
> Commit: http://git-wip-us.apache.org/repos/asf/tomee/commit/9b7b4657
> Tree: http://git-wip-us.apache.org/repos/asf/tomee/tree/9b7b4657
> Diff: http://git-wip-us.apache.org/repos/asf/tomee/diff/9b7b4657
>
> Branch: refs/heads/master
> Commit: 9b7b46570cf43afa9bb904e1615794400124539a
> Parents: de09ee0
> Author: AndyGee 
> Authored: Fri Mar 3 21:24:42 2017 +0100
> Committer: AndyGee 
> Committed: Fri Mar 3 21:24:42 2017 +0100
>
> --
>  .../openejb/assembler/classic/Assembler.java| 166 ++-
>  1 file changed, 85 insertions(+), 81 deletions(-)
> --
>
>
> http://git-wip-us.apache.org/repos/asf/tomee/blob/9b7b4657/
> container/openejb-core/src/main/java/org/apache/openejb/
> assembler/classic/Assembler.java
> --
> diff --git a/container/openejb-core/src/main/java/org/apache/openejb/
> assembler/classic/Assembler.java b/container/openejb-core/src/
> main/java/org/apache/openejb/assembler/classic/Assembler.java
> index cdf7ed2..9af8153 100644
> --- a/container/openejb-core/src/main/java/org/apache/openejb/
> assembler/classic/Assembler.java
> +++ b/container/openejb-core/src/main/java/org/apache/openejb/
> assembler/classic/Assembler.java
> @@ -377,8 +377,8 @@ public class Assembler extends AssemblerTool
> implements org.apache.openejb.spi.A
>  final Object filter = loader.loadClass("org.apache.
> openejb.bval.BValCdiFilter").newInstance();
>  loader.loadClass("org.apache.bval.cdi.BValExtension")
>  .getMethod(
> -"setAnnotatedTypeFilter",
> -loader.loadClass("org.apache.
> bval.cdi.BValExtension$AnnotatedTypeFilter"))
> +"setAnnotatedTypeFilter",
> +loader.loadClass("org.apache.
> bval.cdi.BValExtension$AnnotatedTypeFilter"))
>  .invoke(null, filter);
>  } catch (final Throwable th) {
>  // ignore, bval not compatible or not present
> @@ -579,7 +579,7 @@ public class Assembler extends AssemblerTool
> implements org.apache.openejb.spi.A
>  final ContainerSystem component = systemInstance.getComponent(
> ContainerSystem.class);
>  if (component != null) {
>  postConstructResources(rIds, 
> ParentClassLoaderFinder.Helper.get(),
> component.getJNDIContext(), null);
> -}else{
> +} else {
>  throw new RuntimeException("ContainerSystem has not been
> initialzed");
>  }
>
> @@ -1320,8 +1320,8 @@ public class Assembler extends AssemblerTool
> implements org.apache.openejb.spi.A
>
>  private static List 
> listCommonInfoObjectsForAppInfo(final
> AppInfo appInfo) {
>  final List vfs = new
> ArrayList(
> -appInfo.clients.size() + appInfo.connectors.size() +
> -appInfo.ejbJars.size() + appInfo.webApps.size());
> +appInfo.clients.size() + appInfo.connectors.size() +
> +appInfo.ejbJars.size() + appInfo.webApps.size());
>  for (final ClientInfo clientInfo : appInfo.clients) {
>  vfs.add(clientInfo);
>  }
> @@ -1468,12 +1468,12 @@ public class Assembler extends AssemblerTool
> implements org.apache.openejb.spi.A
>  final MethodContext methodContext =
> entry.getValue();
>  for (final ScheduleData scheduleData :
> methodContext.getSchedules()) {
>  timerStore.createCalendarTimer(
> timerService,
> -(String)
> beanContext.getDeploymentID(),
> -null,
> -entry.getKey(),
> -scheduleData.getExpression(),
> -scheduleData.getConfig(),
> -true);
> +(String)
> beanContext.getDeploymentID(),
> +null,
> +entry.getKey(),
> +scheduleData.getExpression(),
> +s

Fwd: [1/2] tomee git commit: Release WebBeansContext later & check for nulls

[Romain Manni-Bucau]

Quick note to say that most of these null checks are useless cause you cant
enter this code if null. This is false postives of your ide i guess. (No
need to fix but dont listen the ide please)
-- Message transféré --
De : 
Date : 3 mars 2017 21:11
Objet : [1/2] tomee git commit: Release WebBeansContext later & check for
nulls
À : 
Cc :

Repository: tomee
> Updated Branches:
>   refs/heads/tomee-1.7.x fdadd4fa8 -> 39b42eb63
>
>
> Release WebBeansContext later & check for nulls
>
>
> Project: http://git-wip-us.apache.org/repos/asf/tomee/repo
> Commit: http://git-wip-us.apache.org/repos/asf/tomee/commit/ffea29dd
> Tree: http://git-wip-us.apache.org/repos/asf/tomee/tree/ffea29dd
> Diff: http://git-wip-us.apache.org/repos/asf/tomee/diff/ffea29dd
>
> Branch: refs/heads/tomee-1.7.x
> Commit: ffea29dda5c7cd85ad3f06bf00bf351edfab6f53
> Parents: fdadd4f
> Author: AndyGee 
> Authored: Fri Mar 3 21:09:54 2017 +0100
> Committer: AndyGee 
> Committed: Fri Mar 3 21:09:54 2017 +0100
>
> --
>  .../openejb/assembler/classic/Assembler.java| 135 ---
>  1 file changed, 85 insertions(+), 50 deletions(-)
> --
>
>
> http://git-wip-us.apache.org/repos/asf/tomee/blob/ffea29dd/
> container/openejb-core/src/main/java/org/apache/openejb/
> assembler/classic/Assembler.java
> --
> diff --git a/container/openejb-core/src/main/java/org/apache/openejb/
> assembler/classic/Assembler.java b/container/openejb-core/src/
> main/java/org/apache/openejb/assembler/classic/Assembler.java
> index 46ff758..eceb615 100644
> --- a/container/openejb-core/src/main/java/org/apache/openejb/
> assembler/classic/Assembler.java
> +++ b/container/openejb-core/src/main/java/org/apache/openejb/
> assembler/classic/Assembler.java
> @@ -556,7 +556,12 @@ public class Assembler extends AssemblerTool
> implements org.apache.openejb.spi.A
>  rIds.add(resourceInfo.id);
>  }
>  rIds.removeAll(reservedResourceIds);
> -postConstructResources(rIds, ParentClassLoaderFinder.Helper.get(),
> systemInstance.getComponent(ContainerSystem.class).getJNDIContext(),
> null);
> +final ContainerSystem containerSystem =
> systemInstance.getComponent(ContainerSystem.class);
> +if (containerSystem != null) {
> +postConstructResources(rIds, 
> ParentClassLoaderFinder.Helper.get(),
> containerSystem.getJNDIContext(), null);
> +}else {
> +logger.error("ContainerSystem not initialized");
> +}
>
>  // Containers
>  for (final ContainerInfo serviceInfo : 
> containerSystemInfo.containers)
> {
> @@ -805,7 +810,9 @@ public class Assembler extends AssemblerTool
> implements org.apache.openejb.spi.A
>
>  if (start) {
>  final EjbResolver globalEjbResolver =
> systemInstance.getComponent(EjbResolver.class);
> -globalEjbResolver.addAll(appInfo.ejbJars);
> +if (globalEjbResolver != null) {
> +globalEjbResolver.addAll(appInfo.ejbJars);
> +}
>  }
>
>  // bind all global values on global context
> @@ -1777,11 +1784,11 @@ public class Assembler extends AssemblerTool
> implements org.apache.openejb.spi.A
>
>  try {
>  timeout = Integer.parseInt(SystemInstance.get().
> getProperty(TOMEE_DATASOURCE_DESTROY_TIMEOUT, "1000"));
> -if(timeout < 50){
> +if (timeout < 50) {
>  logger.warning(TOMEE_DATASOURCE_DESTROY_TIMEOUT + "
> must be at least 50");
>  timeout = 50;
>  }
> -if(timeout > 3){
> +if (timeout > 3) {
>  timeout = 3;
>  logger.warning(TOMEE_DATASOURCE_DESTROY_TIMEOUT + "
> must not be greater than 3");
>  }
> @@ -1915,46 +1922,36 @@ public class Assembler extends AssemblerTool
> implements org.apache.openejb.spi.A
>  deployedApplications.remove(appInfo.path);
>  logger.info("destroyApplication.start", appInfo.path);
>
> -final Context globalContext = containerSystem.
> getJNDIContext();
>  final AppContext appContext = containerSystem.getAppContext(
> appInfo.appId);
> -final ClassLoader classLoader = appContext.getClassLoader();
> -
> -SystemInstance.get().fireEvent(new
> AssemblerBeforeApplicationDestroyed(appInfo, appContext));
>
>  if (null == appContext) {
>  logger.warning("Application id '" + appInfo.appId + "'
> not found in: " + Arrays.toString(containerSystem.getAppContextKeys()));
>  return;
> -} else {
> -final WebBeansContext webBeansContext =
> appContext.getWebBeansCont

Re: Customizing the dynamic deployer chain

[Romain Manni-Bucau]

I'd like to kind of drop the hardcoded chain logic and freeze it until
somebody get enough motivation and time to rework it in a sortable way
(maybe even sortable events). Last one is an option but surprised there is
no way to do it already - I know I did a couple of time but could have been
a bit more hacky switching  jpa provider or datasource factory for
instance, dont recall the details).

Thinking to it this last option can be saner: using template or resource
provider (globally set) you can make the datasource using your custom
config. Can be worth a try.


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2017-02-27 15:08 GMT+01:00 Svetlin Zarev :

> The latest event that is fired before the AutoConfig deployer is the
> BeforeDeploymentEvent, which is fired too early and does not contain the
> AppModule object. A few ideas come to mind
>
> 1. Back to my original idea of extracting the deployer chain creation to a
> protected method. This should be safe as it does not modify the behaviour
> of TomEE at all. If someone modifies the chain, then it's his
> responsibility to verify he has not broken something
>
> 2. The PreAutoConfigDeployer (i.e. the developer provided deployer) should
> be moved right before the AutoConfig deployer.
>
> 3. Maybe a new deployer right before the AutoConfig one, that will fire a
> new event - BeforeAutoConfigEvent(AppModule)
>
> 4. An event is fired after each deployer ->
> AfterDeployerEvent(Deployer.class, AppModule)
>
> What do you think ?
>
> 2017-02-27 15:43 GMT+02:00 Romain Manni-Bucau :
>
> > try this: @Observes Object
> >
> > you will spy them all ;)
> >
> >
> > Romain Manni-Bucau
> > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > <https://blog-rmannibucau.rhcloud.com> | Old Blog
> > <http://rmannibucau.wordpress.com> | Github <https://github.com/
> > rmannibucau> |
> > LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
> > <https://javaeefactory-rmannibucau.rhcloud.com>
> >
> > 2017-02-27 14:40 GMT+01:00 Svetlin Zarev  com
> > >:
> >
> > > Hi,
> > >
> > > That event is fired too late :) When it's fired, the AutoConfig
> deployer
> > > has already created the datasource. Is there an event fired just before
> > the
> > > AutoConfig deployer ?
> > >
> > > Kind regards,
> > > Svetlin
> > >
> > > 2017-02-24 16:23 GMT+02:00 Svetlin Zarev  > com
> > > >:
> > >
> > > > This event is quite powerful :) I'll definitely check it.
> > > >
> > > > Thanks,
> > > > Svetlin
> > > >
> > > > 2017-02-24 16:05 GMT+02:00 Romain Manni-Bucau  >:
> > > >
> > > >> You can observes an event to do that, no need to tune the deployer
> > > chain:
> > > >> BeforeAppInfoBuilderEvent
> > > >>
> > > >>
> > > >> Romain Manni-Bucau
> > > >> @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > > >> <https://blog-rmannibucau.rhcloud.com> | Old Blog
> > > >> <http://rmannibucau.wordpress.com> | Github <
> > > >> https://github.com/rmannibucau> |
> > > >> LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
> > > >> <https://javaeefactory-rmannibucau.rhcloud.com>
> > > >>
> > > >> 2017-02-24 15:02 GMT+01:00 Svetlin Zarev
>  > > com
> > > >> >:
> > > >>
> > > >> > I have a DynamicDeployer that creates the Resource objects for the
> > > >> > datasources and the ConvertDataSourceDefinitions deployer does the
> > > >> (almost)
> > > >> > same thing, so I want to remove it from the chain
> > > >> >
> > > >> > 2017-02-24 15:56 GMT+02:00 Romain Manni-Bucau <
> > rmannibu...@gmail.com
> > > >:
> > > >> >
> > > >> > > Hi
> > > >> > >
> > > >> > > what's the actual goal? (= why do you need to extend
> > > >> > ConfigurationFactory?)
> > > >> > > Wonder if an event can't solve it if not already ther

Re: Customizing the dynamic deployer chain

[Romain Manni-Bucau]

try this: @Observes Object

you will spy them all ;)


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2017-02-27 14:40 GMT+01:00 Svetlin Zarev :

> Hi,
>
> That event is fired too late :) When it's fired, the AutoConfig deployer
> has already created the datasource. Is there an event fired just before the
> AutoConfig deployer ?
>
> Kind regards,
> Svetlin
>
> 2017-02-24 16:23 GMT+02:00 Svetlin Zarev  >:
>
> > This event is quite powerful :) I'll definitely check it.
> >
> > Thanks,
> > Svetlin
> >
> > 2017-02-24 16:05 GMT+02:00 Romain Manni-Bucau :
> >
> >> You can observes an event to do that, no need to tune the deployer
> chain:
> >> BeforeAppInfoBuilderEvent
> >>
> >>
> >> Romain Manni-Bucau
> >> @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> >> <https://blog-rmannibucau.rhcloud.com> | Old Blog
> >> <http://rmannibucau.wordpress.com> | Github <
> >> https://github.com/rmannibucau> |
> >> LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
> >> <https://javaeefactory-rmannibucau.rhcloud.com>
> >>
> >> 2017-02-24 15:02 GMT+01:00 Svetlin Zarev  com
> >> >:
> >>
> >> > I have a DynamicDeployer that creates the Resource objects for the
> >> > datasources and the ConvertDataSourceDefinitions deployer does the
> >> (almost)
> >> > same thing, so I want to remove it from the chain
> >> >
> >> > 2017-02-24 15:56 GMT+02:00 Romain Manni-Bucau  >:
> >> >
> >> > > Hi
> >> > >
> >> > > what's the actual goal? (= why do you need to extend
> >> > ConfigurationFactory?)
> >> > > Wonder if an event can't solve it if not already there.
> >> > >
> >> > >
> >> > > Romain Manni-Bucau
> >> > > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> >> > > <https://blog-rmannibucau.rhcloud.com> | Old Blog
> >> > > <http://rmannibucau.wordpress.com> | Github <https://github.com/
> >> > > rmannibucau> |
> >> > > LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
> >> > > <https://javaeefactory-rmannibucau.rhcloud.com>
> >> > >
> >> > > 2017-02-24 14:54 GMT+01:00 Svetlin Zarev
>  >> > com
> >> > > >:
> >> > >
> >> > > > Hello,
> >> > > >
> >> > > > I want to subclass the org.apache.openejb.config.Conf
> >> igurationFactory
> >> > > > class
> >> > > > in order to customize the deployer chain. Unfortunately the chain
> is
> >> > > > constructed inside ConfigurationFactory(offline,
> >> preAutoConfigDeployer)
> >> > > > constructor, so when I use the ConfigurationFactory(offline,
> >> > > deployerChain,
> >> > > > configuration) constructor I have to copy-paste a huge portion of
> >> the
> >> > > code
> >> > > > that initializes the deployer chain. Hence my suggestion: It would
> >> be
> >> > > great
> >> > > > if the code that initializes the deployer chain is extracted in a
> >> > > protected
> >> > > > method that initializes the passed Chain -> protected void
> >> > > > initDeployerChain(Chain chain). In that way subclasses can reuse
> >> that
> >> > > code
> >> > > > while being able to painlessly add/remove dynamic deployers.
> >> > > >
> >> > > > Kind regards,
> >> > > > Svetlin
> >> > > >
> >> > >
> >> >
> >>
> >
> >
>

Re: Customizing the dynamic deployer chain

[Romain Manni-Bucau]

You can observes an event to do that, no need to tune the deployer chain:
BeforeAppInfoBuilderEvent


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2017-02-24 15:02 GMT+01:00 Svetlin Zarev :

> I have a DynamicDeployer that creates the Resource objects for the
> datasources and the ConvertDataSourceDefinitions deployer does the (almost)
> same thing, so I want to remove it from the chain
>
> 2017-02-24 15:56 GMT+02:00 Romain Manni-Bucau :
>
> > Hi
> >
> > what's the actual goal? (= why do you need to extend
> ConfigurationFactory?)
> > Wonder if an event can't solve it if not already there.
> >
> >
> > Romain Manni-Bucau
> > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > <https://blog-rmannibucau.rhcloud.com> | Old Blog
> > <http://rmannibucau.wordpress.com> | Github <https://github.com/
> > rmannibucau> |
> > LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
> > <https://javaeefactory-rmannibucau.rhcloud.com>
> >
> > 2017-02-24 14:54 GMT+01:00 Svetlin Zarev  com
> > >:
> >
> > > Hello,
> > >
> > > I want to subclass the org.apache.openejb.config.ConfigurationFactory
> > > class
> > > in order to customize the deployer chain. Unfortunately the chain is
> > > constructed inside ConfigurationFactory(offline, preAutoConfigDeployer)
> > > constructor, so when I use the ConfigurationFactory(offline,
> > deployerChain,
> > > configuration) constructor I have to copy-paste a huge portion of the
> > code
> > > that initializes the deployer chain. Hence my suggestion: It would be
> > great
> > > if the code that initializes the deployer chain is extracted in a
> > protected
> > > method that initializes the passed Chain -> protected void
> > > initDeployerChain(Chain chain). In that way subclasses can reuse that
> > code
> > > while being able to painlessly add/remove dynamic deployers.
> > >
> > > Kind regards,
> > > Svetlin
> > >
> >
>

Re: Customizing the dynamic deployer chain

[Romain Manni-Bucau]

Hi

what's the actual goal? (= why do you need to extend ConfigurationFactory?)
Wonder if an event can't solve it if not already there.


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2017-02-24 14:54 GMT+01:00 Svetlin Zarev :

> Hello,
>
> I want to subclass the org.apache.openejb.config.ConfigurationFactory
> class
> in order to customize the deployer chain. Unfortunately the chain is
> constructed inside ConfigurationFactory(offline, preAutoConfigDeployer)
> constructor, so when I use the ConfigurationFactory(offline, deployerChain,
> configuration) constructor I have to copy-paste a huge portion of the code
> that initializes the deployer chain. Hence my suggestion: It would be great
> if the code that initializes the deployer chain is extracted in a protected
> method that initializes the passed Chain -> protected void
> initDeployerChain(Chain chain). In that way subclasses can reuse that code
> while being able to painlessly add/remove dynamic deployers.
>
> Kind regards,
> Svetlin
>

Re: Issue with TomEE shutdown

[Romain Manni-Bucau]

Hi

seems there is a ScheduledThreadPoolExecutor not shutdowned. Is it in your
application or dependency stack?


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2017-02-21 12:42 GMT+01:00 Dignesh :

> Hi,
> I am using 7.0.2 version of TomEE plus.When I invoke the shutdown.bat, it
> hangs and never gets shutdown.
> I have taken the threaddump and I see lot of Worker threads in waiting
> state. Is there any additional configuration to be done to happen a clean
> shutdown ?
>
> Attaching the thread dump  Threaddump.txt
> <http://tomee-openejb.979440.n4.nabble.com/file/n4681128/Threaddump.txt>
>
> Can anyone help me on this ?
>
> Thank you,
> Dignesh,
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.
> n4.nabble.com/Issue-with-TomEE-shutdown-tp4681128.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: Log files are not generated in %TOMEE_HOME%\logs folder

[Romain Manni-Bucau]

Log4j support a system property to set it so yes if you use the extrrnal
property.

Le 18 févr. 2017 12:21, "Dignesh"  a écrit :

> Hi Romain,
> I dont want the log4j.xml file to be placed in lib folder.Is there any
> configuration setting that I can use so that logging is generated by
> placing
> in conf folder itself?
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.
> n4.nabble.com/Log-files-are-not-generated-in-TOMEE-HOME-
> logs-folder-tp4681117p4681121.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: Log files are not generated in %TOMEE_HOME%\logs folder

[Romain Manni-Bucau]

Maybe check
http://tomee-openejb.979440.n4.nabble.com/openEJB-log4j-td4670622.html

Le 18 févr. 2017 12:00, "Dignesh"  a écrit :

> I have attached the log4j.jar present in the lib directory. Also attached
> the
> system.properties file
> system.properties
>  >
>
> log4j.jar
> 
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.
> n4.nabble.com/Log-files-are-not-generated-in-TOMEE-HOME-
> logs-folder-tp4681117p4681119.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: Log files are not generated in %TOMEE_HOME%\logs folder

[Romain Manni-Bucau]

Hi

Did you add the right log4j jars?

Also by default for log4j1, logging.properties will be loaded as a
log4j.properties. we have an openejb.log4j.external flag to use log4j.xml
if im not mistaken on the property name.


Le 18 févr. 2017 11:48, "Dignesh"  a écrit :

> Hi,
>
> I have deleted logging.properties file present in conf folder. I have added
> customised log4j.xml file in conf location, placed the log4j.xml file in
> the
> lib folder.
>
> I dont the catalina.*.log,host-manager.*.log,manager.*.log generated in
> the
> log folder.
>
> Is there any configuration which I am doing wrong.
>
> I have added the below setting in system.properties file
>
> openejb.log.factory =log4j
>
> below is my log4j.xml file attached. log4j_-_Copy.xml
> 
>
>
> can anyone please help me on were i am going wrong.
> Thank you,
> Dignesh
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.
> n4.nabble.com/Log-files-are-not-generated-in-TOMEE-HOME-
> logs-folder-tp4681117.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: javaee-api releases

[Romain Manni-Bucau]

Hi

2017-02-15 14:34 GMT+01:00 Mark Struberg :

> Hi folks!
>
> Just noticed that we did not release a javaee-api.jar with 7.0.2.
> That feels kind of wrong to me (personal opinion so far).
>
> Until now I just had a
>
> 
>   nnn
>
> in my pom and used this version for all the tomee artifacts.
> That doesn't work anymore for 7.0.2.
>
> Is there a reason we stopped bundling this?
>

we never did, javaee-api always has been another project.


> I mean we have an ongoing effort do document the geronimo-spec apis over
> in geronimo.
> So with every release the JavaDoc would become a tad better.
>
> Do we like to add this again?
>

we do each time we have a reason (change in API for instance)


>
> LieGrue,
> strub

Re: TomEE 7.02 , and JMS 2 Bug

[Romain Manni-Bucau]

we got some fixes on that, hopefully it fixed it as well, any hope you test
on 7.0.3-SNAPSHOT?


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2017-02-13 11:58 GMT+01:00 Yann BLAZART :

> It's on 7.0.2
>
> -----Original Message-
> From: Romain Manni-Bucau [mailto:rmannibu...@gmail.com]
> Sent: mercredi 8 février 2017 18:38
> To: dev@tomee.apache.org
> Subject: Re: TomEE 7.02 , and JMS 2 Bug
>
> Hi Yann,
>
> does it occur on master? not sure i see the path it can
>
>
> Romain Manni-Bucau
> @rmannibucau <https://twitter.com/rmannibucau> |  Blog <
> https://blog-rmannibucau.rhcloud.com> | Old Blog <
> http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau>
> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory <
> https://javaeefactory-rmannibucau.rhcloud.com>
>
> 2017-02-08 18:14 GMT+01:00 Yann BLAZART  bnpparibas.com
> >:
>
> > Hello, little bug in JMS2 for Tomee.
> >
> > When we use JMSContext and want to make a receiveNoWait.
> >
> > In JMSConsumerImpl, line 134 you do a wrapper around what is received.
> >
> > Then in line  136 you set the delivery time.
> >
> > But, if message is null, when no more messages are available, the
> > JMS2.wrap return null. So we got a NPE.
> >
> >
> > Regars.
> >
> >
> > This message and any attachments (the "message") is intended solely
> > for the intended addressees and is confidential.
> > If you receive this message in error,or are not the intended
> > recipient(s), please delete it and any copies from your systems and
> > immediately notify the sender. Any unauthorized view, use that does
> > not comply with its purpose, dissemination or disclosure, either whole
> > or partial, is prohibited. Since the internet cannot guarantee the
> > integrity of this message which may not be reliable, BNP PARIBAS (and
> > its subsidiaries) shall not be liable for the message if modified,
> > changed or falsified.
> > Do not print this message unless it is necessary,consider the
> environment.
> >
> > 
> > --
> >
> > Ce message et toutes les pieces jointes (ci-apres le "message") sont
> > etablis a l'intention exclusive de ses destinataires et sont
> > confidentiels.
> > Si vous recevez ce message par erreur ou s'il ne vous est pas destine,
> > merci de le detruire ainsi que toute copie de votre systeme et d'en
> > avertir immediatement l'expediteur. Toute lecture non autorisee, toute
> > utilisation de ce message qui n'est pas conforme a sa destination,
> > toute diffusion ou toute publication, totale ou partielle, est
> > interdite. L'Internet ne permettant pas d'assurer l'integrite de ce
> > message electronique susceptible d'alteration, BNP Paribas (et ses
> > filiales) decline(nt) toute responsabilite au titre de ce message dans
> > l'hypothese ou il aurait ete modifie, deforme ou falsifie.
> > N'imprimez ce message que si necessaire, pensez a l'environnement.
> >
>

Re: TomEE 7.02 , and JMS 2 Bug

[Romain Manni-Bucau]

Hi Yann,

does it occur on master? not sure i see the path it can


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2017-02-08 18:14 GMT+01:00 Yann BLAZART :

> Hello, little bug in JMS2 for Tomee.
>
> When we use JMSContext and want to make a receiveNoWait.
>
> In JMSConsumerImpl, line 134 you do a wrapper around what is received.
>
> Then in line  136 you set the delivery time.
>
> But, if message is null, when no more messages are available, the
> JMS2.wrap return null. So we got a NPE.
>
>
> Regars.
>
>
> This message and any attachments (the "message") is
> intended solely for the intended addressees and is confidential.
> If you receive this message in error,or are not the intended recipient(s),
> please delete it and any copies from your systems and immediately notify
> the sender. Any unauthorized view, use that does not comply with its
> purpose,
> dissemination or disclosure, either whole or partial, is prohibited. Since
> the internet
> cannot guarantee the integrity of this message which may not be reliable,
> BNP PARIBAS
> (and its subsidiaries) shall not be liable for the message if modified,
> changed or falsified.
> Do not print this message unless it is necessary,consider the environment.
>
> 
> --
>
> Ce message et toutes les pieces jointes (ci-apres le "message")
> sont etablis a l'intention exclusive de ses destinataires et sont
> confidentiels.
> Si vous recevez ce message par erreur ou s'il ne vous est pas destine,
> merci de le detruire ainsi que toute copie de votre systeme et d'en avertir
> immediatement l'expediteur. Toute lecture non autorisee, toute utilisation
> de
> ce message qui n'est pas conforme a sa destination, toute diffusion ou
> toute
> publication, totale ou partielle, est interdite. L'Internet ne permettant
> pas d'assurer
> l'integrite de ce message electronique susceptible d'alteration, BNP
> Paribas
> (et ses filiales) decline(nt) toute responsabilite au titre de ce message
> dans l'hypothese
> ou il aurait ete modifie, deforme ou falsifie.
> N'imprimez ce message que si necessaire, pensez a l'environnement.
>

Re: OpenEJB custom configuration factory & bval.in-container=true

[Romain Manni-Bucau]

2017-02-07 11:56 GMT+01:00 Svetlin Zarev :

> > Side note (find it funny): you complain this property is skipped if you
> use
> > another constructor but same applies to the auto deploy one ;)
>
> The auto deploy one (the no-arg constructor) sets this property :) While
> the others - do not. Which results in a very unpleasant surprise when using
> custom configuration factory.


well you hardcode it so still surprising for users having configured it ;)

anyway not the central piece of that thread - yet ;)


> So may idea was to make the behavior
> consistent among the different constructors. Also it's much easier to
> override or check the value of the property if it's in system.properties,
> rather than searching throughout the whole codebase. When I tried CDI
> enabled app on my tomee with custom configuration factory, the deployment
> started to fail because there were two BeanValidator classes and it was
> pure luck that I accidentally discovered that hidden property.
>
>
Hmm should fail cause Validator injection is ambiguous, the other issues
are not linked to that property but BValCdiFilter implementation which is
set by default whatever this system property is


> Svetlin
>
> 2017-02-07 11:41 GMT+02:00 Romain Manni-Bucau :
>
> > Hi
> >
> > 2017-02-07 10:31 GMT+01:00 Svetlin Zarev  com
> > >:
> >
> > > Hello,
> > >
> > > In *one* of the configuration factory constructors a system property is
> > > set:
> > >
> > > public ConfigurationFactory() {
> > > this(!shouldAutoDeploy());
> > > System.setProperty("bval.in-container", "true");
> > > }
> > >
> > > What do you think about moving this to system.properties ? The reason
> is
> > > that:
> > >
> >
> > well, not an option cause 80% of "tomee" usages are not in tomee and
> don't
> > have system.properties - but doesn't mean we can't move it, just that the
> > file will not work
> >
> >
> > > * it's really hidden and not obvious why it's there
> > >
> >
> > Was the most common piece of code executed early enough when added and
> also
> > a place you can override and change if you desire to keep default
> behavior
> > or have a custom one. We can surely make it part of SystemInstance but
> > override will be harder.
> >
> >
> > > * it's being set every time in case of vanilla tomee
> > >
> >
> > Was one of the goal, not sure I see what the issue is
> >
> >
> > > * it's not set when using custom configuration factory when you use one
> > of
> > > the other constructors (and this breaks CDI)
> > >
> >
> > Not set: was part of the goal to let the custom factory change that
> easily
> > but agree we can find a better place
> > Breaks CDI: depends the CDI config actually but by default yes cause
> > BValExtension will try to add a validator and validator factory but
> openejb
> > does it as well
> >
> >
> > > * IMO it's a good idea to have all global properties at one place,
> > instead
> > > of being scattered in the source
> > >
> >
> > Yes and no, there are multiple kind of properties:
> >
> > - global one ("enforced") like this one: not against aggregating them but
> > gain shouldn't be that big
> > - speific ones: this needs to be done per code area and not aggregated
> all
> > together (you will not put tomee properties in openejb code for instance)
> > - "in case ones": we have some of that kind where it is there just cause
> it
> > can break and it enables the user to make its app working even if default
> > is not desired. These ones are not all very official and I don't find it
> > that bad to hide them a bit cause we shouldn't encourage them
> >
> > So story short: we can aggregate several ones but we can't - I think -
> put
> > them all in a single SystemProperties class.
> >
> > Side note (find it funny): you complain this property is skipped if you
> use
> > another constructor but same applies to the auto deploy one ;)
> >
> > Finally note official properties are listed on
> > http://tomee.apache.org/admin/configuration/server.html
> >
> > If we miss a bit we can add them but this bval one is an internal one. At
> > some point we can even drop it from bval and just detect we run in tomee
> > and set it this way instead of using a system property - maybe better?
> >
> >
> > >
> > > Kind regards,
> > > Svetlin
> > >
> >
>

Re: OpenEJB custom configuration factory & bval.in-container=true

[Romain Manni-Bucau]

Hi

2017-02-07 10:31 GMT+01:00 Svetlin Zarev :

> Hello,
>
> In *one* of the configuration factory constructors a system property is
> set:
>
> public ConfigurationFactory() {
> this(!shouldAutoDeploy());
> System.setProperty("bval.in-container", "true");
> }
>
> What do you think about moving this to system.properties ? The reason is
> that:
>

well, not an option cause 80% of "tomee" usages are not in tomee and don't
have system.properties - but doesn't mean we can't move it, just that the
file will not work


> * it's really hidden and not obvious why it's there
>

Was the most common piece of code executed early enough when added and also
a place you can override and change if you desire to keep default behavior
or have a custom one. We can surely make it part of SystemInstance but
override will be harder.


> * it's being set every time in case of vanilla tomee
>

Was one of the goal, not sure I see what the issue is


> * it's not set when using custom configuration factory when you use one of
> the other constructors (and this breaks CDI)
>

Not set: was part of the goal to let the custom factory change that easily
but agree we can find a better place
Breaks CDI: depends the CDI config actually but by default yes cause
BValExtension will try to add a validator and validator factory but openejb
does it as well


> * IMO it's a good idea to have all global properties at one place, instead
> of being scattered in the source
>

Yes and no, there are multiple kind of properties:

- global one ("enforced") like this one: not against aggregating them but
gain shouldn't be that big
- speific ones: this needs to be done per code area and not aggregated all
together (you will not put tomee properties in openejb code for instance)
- "in case ones": we have some of that kind where it is there just cause it
can break and it enables the user to make its app working even if default
is not desired. These ones are not all very official and I don't find it
that bad to hide them a bit cause we shouldn't encourage them

So story short: we can aggregate several ones but we can't - I think - put
them all in a single SystemProperties class.

Side note (find it funny): you complain this property is skipped if you use
another constructor but same applies to the auto deploy one ;)

Finally note official properties are listed on
http://tomee.apache.org/admin/configuration/server.html

If we miss a bit we can add them but this bval one is an internal one. At
some point we can even drop it from bval and just detect we run in tomee
and set it this way instead of using a system property - maybe better?


>
> Kind regards,
> Svetlin
>

Re: Deploy MDB(topic) in non clustered way

[Romain Manni-Bucau]

Le 5 févr. 2017 11:06, "Dignesh"  a écrit :

So does it mean , there is a no way via a configuration were we can restrict
messages being replicated on all nodes. ?


You chose a topic so you requested to distribute the messages to all nodes
explicitely





And how would using another topic will solve the use case.?


If names are different you control the messages. This is more a design
issue i think



I haven't understood what selector is ?


This is a workaround for this kind of design issue specific to JMS. It acts
as a filter on messages. You get all messages but before being passed to
the mdb a selector (condition) is used to filter them.








--
View this message in context: http://tomee-openejb.979440.
n4.nabble.com/Deploy-MDB-topic-in-non-clustered-way-tp4681016p4681020.html
Sent from the TomEE Dev mailing list archive at Nabble.com.

Re: Deploy MDB(topic) in non clustered way

[Romain Manni-Bucau]

Hmm, why not using another queue/topic or selector?


Le 5 févr. 2017 10:32, "Dignesh"  a écrit :

> Below is the activation property element configured in my ejb-jar.xml file.
>
> 
> 
>
> destination config-property-name>
>
> MyTopic config-property-value>
> 
> 
>
> destinationType activation-config-property-name>
>
> javax.jms.Topic activation-config-property-value>
> 
> 
>
> clientId config-property-name>
>
> MyTopicMDB config-property-value>
> 
> 
>
> subscriptionName activation-config-property-name>
>
> MyTopicMDB_Scub activation-config-property-value>
> 
> 
>
> In cluster environment having 3 nodes, Each MDB deployed creates a single
> JMS connection. This is due to the unique deployement id(ClientID) we
> assign
> to the bean.
>
> Now my issue here is when I raise a JMS message, all the mdbs (Topic) in
> each nodes gets the message. I need to restrict the message to be delivered
> to single node.
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.
> n4.nabble.com/Deploy-MDB-topic-in-non-clustered-way-tp4681016p4681018.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: Deploy MDB(topic) in non clustered way

[Romain Manni-Bucau]

Hi

Not sure i get it. There is no link between deployment id of the ejb and
connection number.

The topic name (and type BTW) are activation properties you can configure
whatever EJB name you use.

Is that your case? N different MDB listening the same topic? Then forcing
the destination name and type should work


Le 5 févr. 2017 05:01, "Dignesh"  a écrit :

Hi,
I have a cluster set up with TomEE 7.0.2 with 3 nodes.
I have a MBD (MyTopic) deployed on all the 3 nodes.
What I have observed is Each MDB (MyTopic) that is deployed to a server
instance in cluster environment creates a single JMS connection. - This is
due to the unique deployement id we assign to the bean.So when a JMS message
is raised, all the MDB's deployed in each node receives the message.
So Is it possible to replicate the message on all nodes for some topics
which are deployed ?

I was able to do it by having same clientID assigned to the MDB in all
nodes. - is this is correct ? OR is there any cleaner way to acheive this.
With the above approach I am seeing the alreadyconnected exceptions in the
log.. can this be ignored . OR is there any better way to address this
usecase.

P.S. I dont want to use Queues :)

Thank you very much.




--
View this message in context: http://tomee-openejb.979440.
n4.nabble.com/Deploy-MDB-topic-in-non-clustered-way-tp4681016.html
Sent from the TomEE Dev mailing list archive at Nabble.com.

Re: Issue with "MDB topic"

[Romain Manni-Bucau]

Hi

what's the server is doing? did it see the connection? Do you have a full
client+server sample we can run to reproduce?

(you can inspire from
https://github.com/apache/tomee/tree/master/examples/client-resource-lookup-preview
maybe if you need help to setup a project)


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2017-02-01 12:48 GMT+01:00 Dignesh :

> Hi ,
>
> I am using the below client program to publish the messages. I am seeing
> the
> below error. Can some one please help me on this.
>
> Exception in thread "main" javax.jms.JMSException: Wire format negotiation
> timeout: peer did not send his wire format.
> at
> org.apache.activemq.util.JMSExceptionSupport.create(
> JMSExceptionSupport.java:72)
> at
> org.apache.activemq.ActiveMQConnection.syncSendPacket(
> ActiveMQConnection.java:1413)
> at
> org.apache.activemq.ActiveMQConnection.ensureConnectionInfoSent(
> ActiveMQConnection.java:1478)
> at
> org.apache.activemq.ActiveMQConnection.createSession(
> ActiveMQConnection.java:329)
> at client.InsertJMSMessageTopic.main(InsertJMSMessageTopic.
> java:30)
> Caused by: java.io.IOException: Wire format negotiation timeout: peer did
> not send his wire format.
> at
> org.apache.activemq.transport.WireFormatNegotiator.oneway(
> WireFormatNegotiator.java:99)
> at
> org.apache.activemq.transport.MutexTransport.oneway(
> MutexTransport.java:68)
> at
> org.apache.activemq.transport.ResponseCorrelator.asyncRequest(
> ResponseCorrelator.java:81)
> at
> org.apache.activemq.transport.ResponseCorrelator.request(
> ResponseCorrelator.java:86)
> at
> org.apache.activemq.ActiveMQConnection.syncSendPacket(
> ActiveMQConnection.java:1388)
> ... 3 more
>
> Thank you,
> Dignesh,
> InsertJMSMessageTopic.java
> <http://tomee-openejb.979440.n4.nabble.com/file/n4680992/
> InsertJMSMessageTopic.java>
>
>
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.
> n4.nabble.com/Issue-with-MDB-topic-tp4680992.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: Issue with TomEE startup

[Romain Manni-Bucau]

Hi

your dispatcher is a tomcat <= 8.0 interceptor, tomcat 8.5 doesn't provide
it anymore (see
https://tomcat.apache.org/tomcat-8.5-doc/config/cluster-interceptor.html)


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2017-01-27 14:53 GMT+01:00 Dignesh :

> Hi,
>
>
> I have configured my TomEE in cluster. Attached is my server.xml file. I am
> getting classnotfound exceptions in log. server.xml
> <http://tomee-openejb.979440.n4.nabble.com/file/n4680962/server.xml>
>
> 27-Jan-2017 19:16:31.087 SEVERE [main]
> sun.reflect.NativeMethodAccessorImpl.invoke Begin event threw exception
>  java.lang.ClassNotFoundException:
> org.apache.catalina.tribes.group.interceptors.MessageDispatch15Interceptor
> at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
> at
> org.apache.tomcat.util.digester.ObjectCreateRule.
> begin(ObjectCreateRule.java:116)
> at
> org.apache.tomcat.util.digester.Digester.startElement(Digester.java:1190)
> at
> com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(
> AbstractSAXParser.java:509)
> at
> com.sun.org.apache.xerces.internal.parsers.AbstractXMLDocumentParser.
> emptyElement(AbstractXMLDocumentParser.java:182)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl
> .scanStartElement(XMLDocumentFragmentScannerImpl.java:1342)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl
> $FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2770)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(
> XMLDocumentScannerImpl.java:606)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl
> .scanDocument(XMLDocumentFragmentScannerImpl.java:510)
> at
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(
> XML11Configuration.java:848)
> at
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(
> XML11Configuration.java:777)
> at
> com.sun.org.apache.xerces.internal.parsers.XMLParser.
> parse(XMLParser.java:141)
> at
> com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(
> AbstractSAXParser.java:1213)
> at
> com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(
> SAXParserImpl.java:649)
> at org.apache.tomcat.util.digester.Digester.parse(
> Digester.java:1458)
> at org.apache.catalina.startup.Catalina.load(Catalina.java:578)
> at org.apache.catalina.startup.Catalina.load(Catalina.java:629)
> 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)
>
> 27-Jan-2017 19:16:31.088 WARNING [main]
> sun.reflect.NativeMethodAccessorImpl.invoke Catalina.start using
> conf/server.xml: Error at (159, 114) :
> org.apache.catalina.tribes.group.interceptors.MessageDispatch15Interceptor
> 27-Jan-2017 19:16:31.094 SEVERE [main]
> sun.reflect.NativeMethodAccessorImpl.invoke Begin event threw exception
>  java.lang.ClassNotFoundException:
> org.apache.catalina.tribes.group.interceptors.MessageDispatch15Interceptor
> at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
> at
> org.apache.tomcat.util.digester.ObjectCreateRule.
> begin(ObjectCreateRule.java:116)
> at
> org.apache.

Re: hi, using OpenEJB & interested to contribute a little towards the docs?

[Romain Manni-Bucau]

Hi Thomas,

here are few pointers:

- http://tomee.apache.org/documentation.old.html is the old doc page
(hopefully pretty useless now or soon)
- testing portal is there
http://tomee.apache.org/developer/testing/index.html. You see to be in
http://tomee.apache.org/developer/testing/other/index.html case but other
ones can be interesting too depending your plans
- configuration portal is
http://tomee.apache.org/admin/configuration/index.html and I think you
mainly want to have a look to
http://tomee.apache.org/admin/configuration/resources.html. You can feel
like datasource properties are missing but if you read the high level
explanation + datasource part you will see you just need to refer to the
implementation we use (tomcat-jdbc or dbcp2) page for that. When
migrating/enhancing this page I got rid of datasource specific properties
which is not something tomee owns cause of that behavior but just
referenced where to find them up to date

Hope it helps



Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2017-01-27 2:31 GMT+01:00 Thomas Whitmore :

> Hi everybody,
>
> We're prototyping OpenEJB as an embedded container to support the portion
> of our unit-testing which needs EJB functionality. So far it seems a good
> clean component, working well for us. Nice quality of code under the
> covers, too.
>
> In particular one feature we like is  the ability to configure OpenEJB
> dynamically (Datasources etc) via the properties. Since we have datasource
> config varying between developer environments, and another primary place
> already exists for configuration,  it's nice not to need configuration
> duplicated (and developers to have to change it manually) to support the
> OpenEJB modality of running unit-tests.
>
> We use embedded container startup & restriction of which classpath roots
> to scan:
>
> -  properties.setProperty("openejb.deployments.classpath.include",
> "(.*moduleWithEjbs/target/classes/)");
>
> -  EJBContainer.createEJBContainer(properties);
> We also use property-driven configuration:  eg.
>
> -  properties.setProperty( "TransactionManager",
> "new://TransactionManager/");
>
> -  properties.setProperty( "java:/MyDatasource",
> "new://Resource/?type=java.sql.DataSource"+params);
>
> Since these two capabilities benefitted us but the areas not so well
> documented, I'd like to ask about potentially contributing a little
> documentation in the area 1) of how to startup an embedded OpenEJB
> container and 2) property-based configuration.
>
> There's also 3) the rather outstanding issue of the empty 'Documentation'
> page on the "new" TomEE site.  Does anybody have a list of what of the old
> doco is still valid/ and what's outdated? If a quick usable TOC could be
> put up, that would be far better than having just an empty page; and would
> enable 'Documentation' to be added to the site navbar (hard to find
> currently).
>
> I won't have a lot of time, but if there's some improvement that can be
> achieved in a few hours I'd like to consider it.
>
> Thoughts?
>
> Regards,
> Thomas
>
> __
> This email has been scanned by the Symantec Email Security.cloud service.
> For more information please visit http://www.symanteccloud.com
> __

Re: TomEE JMS messages not replicated across all the nodes in cluster

[Romain Manni-Bucau]

doc is http://activemq.apache.org/clustering.html

here is a sample using tomee uri:
https://github.com/apache/tomee/blob/master/container/openejb-core/src/test/java/org/apache/openejb/resource/activemq/ActiveMQ5FactoryTest.java#L55
if you go with the activemq.xml, activemq doc is up to date but you need to
add needed dependencies like spring etc in tomee/lib. Think our doc is no
more up to date for that (we rely on very old deprecated versions)


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2017-01-26 18:55 GMT+01:00 Dignesh :

> hello,
> Is it possible to provide an example or documentation reference so that i
> can give a try ?
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.
> n4.nabble.com/TomEE-JMS-messages-not-replicated-across-all-the-nodes-in-
> cluster-tp4680944p4680950.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: TomEE JMS messages not replicated across all the nodes in cluster

[Romain Manni-Bucau]

server.xml and context.xml are unrelated to AMQ, you need to either use the
broker url to setup the cluster (uri syntax is a bit tricky but it is
doable since 7.0.2 IIRC) or activemq.xml syntax (you need to add a few jar
to tomee lib for it to work).


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2017-01-26 18:48 GMT+01:00 Dignesh :

> Hello,
>
> I only modifed server.xml and context.xml files to form the 2 instances in
> cluster.
> Are there any additional configuration to be done to have activeMq
> clustersized ?
>
>
> Thank you,
> Dignesh,
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.
> n4.nabble.com/TomEE-JMS-messages-not-replicated-across-all-the-nodes-in-
> cluster-tp4680944p4680948.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: TomEE JMS messages not replicated across all the nodes in cluster

[Romain Manni-Bucau]

Hi

have a look on activemq configuration side. If you don't ensure AMQ
configuration is clusterized then you have 2 split instances


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2017-01-26 14:04 GMT+01:00 Dignesh :

> Hello,
>
> I am using 7.0.2 version of TomEE plus. I have configured two instances in
> a
> cluster.
> I am raising a JMS message(Destination is topic) in one node, and i want
> that the message to be replicated on both nodes.Currently the message is
> delivered only to the node which is raising the message. I want the message
> to be replicated across all the nodes.
> Should there be an additional configuration to be done to acheive this ?Or
> is it the default behavior.
>
> Thank you,
> Dignesh
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.
> n4.nabble.com/TomEE-JMS-messages-not-replicated-across-all-the-nodes-in-
> cluster-tp4680944.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: ClassNotFoundException: com.sun.el.ExpressionFactoryImpl in embedded Arquillian container

[Romain Manni-Bucau]

Hi

you used javax API, use org.apache.tomee:javaee-api or tomcat one or force
through the corresponding system property the implementation to use

The default is just not the one which is used in tomee cause of that
dependency.


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2017-01-18 3:29 GMT+01:00 drenjithr :

> Hi Ivan
>
> I am getting the same error. Can you please help me how you resolved this
> error?
> Caused by: javax.el.ELException: Provider com.sun.el.ExpressionFactoryImpl
> not found
> at javax.el.FactoryFinder.newInstance(FactoryFinder.java:101)
> at javax.el.FactoryFinder.find(FactoryFinder.java:197)
> at javax.el.ExpressionFactory.newInstance(ExpressionFactory.
> java:197)
> at javax.el.ExpressionFactory.newInstance(ExpressionFactory.
> java:168)
> at
> org.apache.jasper.runtime.JspApplicationContextImpl.(
> JspApplicationContextImpl.java:46)
> at
> org.apache.jasper.runtime.JspApplicationContextImpl.getInstance(
> JspApplicationContextImpl.java:76)
> at
> org.apache.jasper.runtime.JspFactoryImpl.getJspApplicationContext(
> JspFactoryImpl.java:217)
> at
> org.apache.openejb.cdi.OpenEJBLifecycle.setJspELFactory(
> OpenEJBLifecycle.java:420)
> at
> org.apache.openejb.cdi.OpenEJBLifecycle.initializeServletContext(
> OpenEJBLifecycle.java:387)
> at
> org.apache.tomee.catalina.TomcatWebAppBuilder.startInternal(
> TomcatWebAppBuilder.java:1464)
> at
> org.apache.tomee.catalina.TomcatWebAppBuilder.configureStart(
> TomcatWebAppBuilder.java:1124)
> at
> org.apache.tomee.catalina.GlobalListenerSupport.lifecycleEvent(
> GlobalListenerSupport.java:133)
> at
> org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(
> LifecycleBase.java:94)
> at
> org.apache.catalina.core.StandardContext.startInternal(
> StandardContext.java:5087)
> at org.apache.catalina.util.LifecycleBase.start(
> LifecycleBase.java:150)
> ... 97 more
> Caused by: java.lang.ClassNotFoundException:
> com.sun.el.ExpressionFactoryImpl
> at
> org.apache.catalina.loader.WebappClassLoaderBase.loadClass(
> WebappClassLoaderBase.java:1285)
>
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.n4.nabble.com/
> ClassNotFoundException-com-sun-el-ExpressionFactoryImpl-
> in-embedded-Arquillian-container-tp4679843p4680886.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: Collaboration (TOMEE-1998)

[Romain Manni-Bucau]

Hi Ivan,

sorry, didn't see your mail and your PR, only the JIRA ticket (not yet sure
why but let's blame the human between the computer and keyboard until we
identify something else)

The PR looks good with few notes:

- int -> integer: not needed
- count() doesn't need to return Response but can still return int (you
already fixed the text_plain issue)
- why adding eclipselink metadata since we run with openjpa?
- you mention jackson but we use johnzon ("typo" i guess)

Looks a lot but that's globally details, the only part you missed was the
string->int conversion (my impl is not the sexiest in term of js but does
the job).



Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2017-01-16 23:25 GMT+01:00 Ivan Junckes Filho :

> Hey guys, I didn't receive any feedback on the request. As I said I am very
> interested in contribute more to tomee, but not having a proper feedback is
> a bit discouraging.
>
> I spent a few hours with that PR so I would appreciate a lot if you guys
> could merge it.
>
> Thank you.
>
> On Wed, Jan 11, 2017 at 9:31 AM, Ivan Junckes Filho  >
> wrote:
>
> > Hi guys,
> >
> > I created a PR https://github.com/apache/tomee/pull/56, for an issue
> > with moviefun-rest example. The app was not working with tomee 7 and I
> was
> > able to fix it. Also created a ticket TOME-1998 to that PR.
> >
> > This morning I looked and saw there was a change to fix TOMEE-1998 and my
> > PR was not taken care of.
> > https://github.com/apache/tomee/commit/cd1e39e721db73269ab18b540fbe1d
> > f110e5cc0a
> >
> > This change broke my PR and it is not enough to solve all issues with
> > Tomee 7. I am trying to get engaged and collaborate more so would be nice
> > if my PR is considered for this task.
> >
> > Thank you.
> >
>

Re: JAX-RS deployment in TomEE

[Romain Manni-Bucau]

Hi

Tomee builds an implicit Application. You can customize the mapping with
@ApplicationPath or Application servlet mapping. Except the implicit part
all is standard and jaxrs doesnt require any web.xml config by itself.


Le 16 janv. 2017 13:04, "sudhish81"  a
écrit :

> I have a RESTful service running in IBM Websphere for which the web.xml,
> the
> Jersey servlet definition is given as below
> com.sun.jersey.spi.container.servlet.
> ServletContainer
>
> As I needed to migrate the service to TomEE, When I deployed the same
> application in TomEE server without having any servlet definitions in
> web.xml file, its working without any error. So my question is, how the
> REST
> resources like GET and POST are getting called without any servlet
> definitions in web.xml file. Does TomEE do this implicitly?
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.
> n4.nabble.com/JAX-RS-deployment-in-TomEE-tp4680881.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

snapshots are back

[Romain Manni-Bucau]

Hi guys,

you probably know we got some issue when our builds got migrated to the new
machine. The snapshot deployment is back (
https://issues.apache.org/jira/browse/INFRA-13116)

Thanks INFRA for your hard work!

Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

Fwd: svn commit: r1777288 - in /tomee/site/trunk: content/css/cardio.css content/documentation.html content/index.html generators/site-tomee-ng/src/main/jbake/templates/index.gsp

[Romain Manni-Bucau]

Hey Andy,

when selected "Embedded or distributed as you prefer." I took care to not
use "EE" or "Application Server" which are highly negative terms these
days, do you care to remove it, even rephrasing previous wording but trying
to focus on strength or usage?

Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

-- Forwarded message --
From: 
Date: 2017-01-04 12:54 GMT+01:00
Subject: svn commit: r1777288 - in /tomee/site/trunk:
content/css/cardio.css content/documentation.html content/index.html
generators/site-tomee-ng/src/main/jbake/templates/index.gsp
To: comm...@tomee.apache.org


Author: andygumbrecht
Date: Wed Jan  4 11:54:08 2017
New Revision: 1777288

URL: http://svn.apache.org/viewvc?rev=1777288&view=rev
Log:
Better position
English
Link to legacy doc

Modified:
tomee/site/trunk/content/css/cardio.css
tomee/site/trunk/content/documentation.html
tomee/site/trunk/content/index.html
tomee/site/trunk/generators/site-tomee-ng/src/main/jbake/
templates/index.gsp

Modified: tomee/site/trunk/content/css/cardio.css
URL: http://svn.apache.org/viewvc/tomee/site/trunk/content/css/
cardio.css?rev=1777288&r1=1777287&r2=1777288&view=diff

==
--- tomee/site/trunk/content/css/cardio.css (original)
+++ tomee/site/trunk/content/css/cardio.css Wed Jan  4 11:54:08 2017
@@ -120,7 +120,7 @@ header {

 header .table {
display: table;
-   height: 100%;
+   height: 50%;
 }

 header .container {
@@ -310,8 +310,8 @@ section {
 }

 .intro-tables {
-   top: -130px;
-   position: relative;
+   top: -630px;
+   position: inherit;
 }

 .intro-table {

Modified: tomee/site/trunk/content/documentation.html
URL: http://svn.apache.org/viewvc/tomee/site/trunk/content/
documentation.html?rev=1777288&r1=1777287&r2=1777288&view=diff

==
--- tomee/site/trunk/content/documentation.html (original)
+++ tomee/site/trunk/content/documentation.html Wed Jan  4 11:54:08 2017
@@ -100,7 +100,8 @@

 
 
-Coming soon!
+Coming soon! Please join the community to help us update this
section.
+You can find the old documentation
here, but please be warned that much of this is now outdated!
 
 


Modified: tomee/site/trunk/content/index.html
URL: http://svn.apache.org/viewvc/tomee/site/trunk/content/
index.html?rev=1777288&r1=1777287&r2=1777288&view=diff

==
--- tomee/site/trunk/content/index.html (original)
+++ tomee/site/trunk/content/index.html Wed Jan  4 11:54:08 2017
@@ -67,8 +67,8 @@



-   
Developer
-   Admin
+   
Developers
+   
Administrators

Advanced

Security

Examples
@@ -92,7 +92,7 @@
 Apache TomEE
 
 
-Embedded or
distributed as you prefer.
+The Embedded or Remote
EE Application Server
 |
 
 

Modified: tomee/site/trunk/generators/site-tomee-ng/src/main/jbake/
templates/index.gsp
URL: http://svn.apache.org/viewvc/tomee/site/trunk/generators/
site-tomee-ng/src/main/jbake/templates/index.gsp?rev=
1777288&r1=1777287&r2=1777288&view=diff

==
--- tomee/site/trunk/generators/site-tomee-ng/src/main/jbake/templates/index.gsp
(original)
+++ tomee/site/trunk/generators/site-tomee-ng/src/main/jbake/templates/index.gsp
Wed Jan  4 11:54:08 2017
@@ -10,7 +10,7 @@
 Apache TomEE
 
 
-Embedded or
distributed as you prefer.
+The Embedded or Remote
EE Application Server
 |
 
 

Re: Classloading issues integrating Jersey 2.16 and apache-tomee-plus-7.0.0

[Romain Manni-Bucau]

2017-01-03 10:20 GMT+01:00 Dignesh :

> Okay. I will remove the custom loader.
>
> A last question.
> As per the description in https://issues.apache.org/jira/browse/TOMEE-1851
> ,
> I should not see the issue of I add the below content in context.xml file
>
>
Not really. This only control the parent-first/last behavior for not
filtered classes. With jersey you likely need to force the loading of a set
of filtered classes. This is controllable with forceSkip property but I
think you can't set it from the configuration.

What I'd do:

1. test it in a plain webapp (no ear) and make it work with previously
mentionned configurations
1. bis. if you have issues with 1. please share a maven project as
mentionned with a tomee setup
2. move this configuration to ear, normally if you used global
configuration it should work too, if not try adding back the
WebAppFirstEarClassLoader

Note that 1. will let you identify which classes need a particular loading
(org.glassfish is likely just a part of the iceberg but actual classes are
- as mentionned - probably com.sun.x.

Until you do this work I fear you will just be in a try and fail process.
Once these classes are identified you can configure tomee to make it
working.


> 
>loaderClass="org.apache.tomee.catalina.WebAppFirstEarClassLoader"
> forceSkip="com.company.fromparent.,org.apache.deltaspike" />
> 
>
> But looks like it is not working. Is it something which is expected  ?
>
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.
> n4.nabble.com/Classloading-issues-integrating-Jersey-2-
> 16-and-apache-tomee-plus-7-0-0-tp4678794p4680850.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: Classloading issues integrating Jersey 2.16 and apache-tomee-plus-7.0.0

[Romain Manni-Bucau]

No remove this Loader which likely not do what you want (this loader class
is more an internal at the moment than something exposed)


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2017-01-03 10:05 GMT+01:00 Dignesh :

> Hi Romain,
>
> Thank you very much for quick response.
>
> openejb.classloader.forced-load - classes to load from the webapp first.
>
> So if I add the above property in the system.properties file, Is there a
> need to add the below content in context.xml of each webapp?
>
> 
>loaderClass="org.apache.tomee.catalina.WebAppFirstEarClassLoader"/>
> 
>
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.
> n4.nabble.com/Classloading-issues-integrating-Jersey-2-
> 16-and-apache-tomee-plus-7-0-0-tp4678794p4680848.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: BrokerXmlConfig property in resource element of tomee.xml file is not honoured.

[Romain Manni-Bucau]

Hi

do you care setting up a small maven project (an empty war is fine) with
tomee-maven-plugin configured the same way your instance is (same
additional libraries and config)? This will let us reproduce quickly
without guessing which part is wrong


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2017-01-03 8:33 GMT+01:00 Dignesh :

> I have added all the required spring jars required in the lib directory.
> And
> I also I tried specifying the complete path in the xml file. I still see
> the
> issue. Please let me know any other configurations needs to be double
> checked.
>
>
> Thank you.
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.
> n4.nabble.com/BrokerXmlConfig-property-in-resource-element-
> of-tomee-xml-file-is-not-honoured-tp4680645p4680845.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: Classloading issues integrating Jersey 2.16 and apache-tomee-plus-7.0.0

[Romain Manni-Bucau]

Hi Dignesh,

you don't need to write a custom loader, using
openejb.classloader.forced-[load|skip]=package1,package2 should be enough
(in conf/system.properties)

I'd use the packages org.glassfish,com.sun to start


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2017-01-03 8:26 GMT+01:00 Dignesh :

> Hi Romain,
>
> I am still seeing the issue on TomEE 7.0.2 version. Can you please guide me
> where I am going wrong.
>
> I have written a customclassloader which is placed in lib directory
>
> Below is my context.xml data
>
> 
>  loaderClass="org.apache.tomee.catalina.
> WebAppFirstEarClassLoader"/>
> 
>
> I have attached the two java files (customClassLoader)
> CustomTomEELoader.txt
> <http://tomee-openejb.979440.n4.nabble.com/file/n4680844/
> CustomTomEELoader.txt>
> CustomTomEEClassLoader.txt
> <http://tomee-openejb.979440.n4.nabble.com/file/n4680844/
> CustomTomEEClassLoader.txt>
>
> Thank you very much
>
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.
> n4.nabble.com/Classloading-issues-integrating-Jersey-2-
> 16-and-apache-tomee-plus-7-0-0-tp4678794p4680844.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: Legacy site

[Romain Manni-Bucau]

Le 21 déc. 2016 21:16, "agumbrecht"  a écrit :

That's a great suggestion Ivan, and maybe the first step would be to write
or
link that info on the front page.

I think we need to find some dates and commit to a documentation day or two
as a team, and not just leave it all to Romain. It's unlikely this could be
over the holiday period, or even in January, but would be nice to get some
community commitment organized together - We could all meet up on Google
Hangouts and support each other throughout the days work.

In no particular order I'd like to see:

--The legacy documentation linked on the front page until the new site
rocks:

TomEE Examples: http://tomee.apache.org/examples/index.html
TomEE Docs: http://tomee.apache.org/documentation.old.html


Rmb: dont like this option much since 50% of the data is wrong




--The pop-overs on the front page are annoying as hell as they take ages to
load and then the mouse needs to move to click - not intuitive.


Rmb: surely my english but i dont know what it is

--A step by step getting started tutorial from download to start page.


Rmb: good idea


--Links to good TomEE blogs - Absolutely anything we can find to link to.
Romain has many hidden treasures on his blog.

Rmb: i would avoid it and document as started by theme and not as in the
old site just randomly making impossible to find anything or to navigate


--A step by step guide for debugging in IDEA, Netbeans and Eclipse. The
changes in TomEE mean that several properties must be set to enable this, as
it no longer works out-of-the-box.


Rmb: it does afaik, think they fixed it, if not an issue to open


Also note Thomas from myfaces planned to work on the site organisation so
something to coordinate next year probably.

Site now being jbake/tomee (for sev) based it is easier to make the
rendering advanced and more people to contribute (no more perl ;))






-
--
Andy Gumbrecht

http://www.tomitribe.com
agumbre...@tomitribe.com
https://twitter.com/AndyGeeDe

TomEE treibt Tomitribe ! | http://tomee.apache.org
--
View this message in context: http://tomee-openejb.979440.
n4.nabble.com/Legacy-site-tp4680787p4680809.html
Sent from the TomEE Dev mailing list archive at Nabble.com.

Re: Legacy site

[Romain Manni-Bucau]

2016-12-19 15:19 GMT+01:00 agumbrecht :

> Sure, there is a lot of work required on the new site and I know that it's
> practically only you that has done any work on it. So well done for that!
>
> Everyone is extremely busy of late, so it's likely that it'll stay being a
> one man show for a while now, until we find more community at least. I just
> think that we've lost a lot of useful info from the old site that is now
> hard to find (other than keeping a local copy). The information that is
> there so far is great for current experienced users, but for a newbie
> there's not much to go on.
>
> It would be nice if the new site had a reference to the old documentation
> until it's more up to date.
>
> WDYT?
>
>
well after several months of inactivity and a site where half of the doc
was outdated or irrelevant I think it is better to have lost a small
accurate part. If you can list the parts you miss we can surely ensure it
tracked at least and we can add it.


>
>
> -
> --
> Andy Gumbrecht
>
> http://www.tomitribe.com
> agumbre...@tomitribe.com
> https://twitter.com/AndyGeeDe
>
> TomEE treibt Tomitribe ! | http://tomee.apache.org
> --
> View this message in context: http://tomee-openejb.979440.
> n4.nabble.com/Legacy-site-tp4680787p4680789.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: Legacy site

[Romain Manni-Bucau]

Hi Andy,

as mentionned it is still fully working - even if we don't have any
guarantee on it, only the index was replaced (we can surely remap it on
http://tomee.apache.org/index.old.html but it should be useless or means we
have to work on some content on the new website)


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2016-12-19 13:07 GMT+01:00 agumbrecht :

> Is the legacy documentation completely offline, or is there a link to it
> somewhere?
>
>
>
> -
> --
> Andy Gumbrecht
>
> http://www.tomitribe.com
> agumbre...@tomitribe.com
> https://twitter.com/AndyGeeDe
>
> TomEE treibt Tomitribe ! | http://tomee.apache.org
> --
> View this message in context: http://tomee-openejb.979440.
> n4.nabble.com/Legacy-site-tp4680787.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: where are TomEE snapshot repositories ?

[Romain Manni-Bucau]

version was not updated - will do now - and we got some errors it seems


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2016-12-14 14:02 GMT+01:00 TomeeUser2 :

> Thanks Romain. But I don't see snapshot builds there. Are they not
> available
> any more ?
>
> Regards,
> -Shan
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.
> n4.nabble.com/where-are-TomEE-snapshot-repositories-tp4680728p4680737.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: where are TomEE snapshot repositories ?

[Romain Manni-Bucau]

https://repository.apache.org

Le 13 déc. 2016 13:23, "TomeeUser2"  a écrit :

> Hi,
>
> I am not able to find TomEE snapshot repositories. Is the location changed
> ?
>
> Regards,
> -Shan
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.
> n4.nabble.com/where-are-TomEE-snapshot-repositories-tp4680728.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>

Re: authorization for ejbd/http client

[Romain Manni-Bucau]

Users rely on authorizatuon query param - stripped before actual query for
security reasons - to put the token.

Side note: also used for other token based solutions like oauth2 or
equivalent.


Le 9 déc. 2016 23:32, "David Blevins"  a écrit :

> http://www.tomitribe.com
>
> > On Dec 6, 2016, at 2:22 PM, Romain Manni-Bucau 
> wrote:
> >
> > Le 6 déc. 2016 23:15, "David Blevins"  a écrit
> :
> >
> >
> >> On Dec 5, 2016, at 2:54 PM, Romain Manni-Bucau 
> > wrote:
> >>
> >>> You may have a desktop app or some other scenario where on your trusted
> >>> network, users can log in and you don’t want identity statically
> > configured
> >>> on the server side.
> >>>
> >>>
> >> This is a feature we don't have today at all so quite out of scope of
> the
> >> current mail (this is a new feature client wide, not related to udp
> >> probably)
> >
> > We do have this exactly and I think is possibly a reason for the
> confusion.
> >
> > Here’s a thread from 2008, "Desktop app communicating with EJB"
> >
> > - http://tomee-openejb.979440.n4.nabble.com/Desktop-app-
> > communicating-with-EJB-td980332.html <http://tomee-openejb.979440.
> > n4.nabble.com/Desktop-app-communicating-with-EJB-td980332.html>
> >
> > Clients can login via the RemoteInitialContext parameters and have their
> > identity propagate with their remote calls.
> >
> > The only change is that the user/pass could get applied at the http layer
> > as well.
> >
> >
> > This is unrelated to my comment. Point was we can use it with multicast -
> > which is the only issue - cause outside of the multicasted info - the
> url.
> >
> >
> > Nothing we couldnt enhance but as explained this is also not needed and
> > your example doesnt show this is wrong.
>
> I’m quite lost.  Can you post a code snippet on how someone uses basic
> auth from the client side with httpd+ejbd?
>
> -David
>
>

Re: Unable to run jsf application that uses ejb and managed bean

[Romain Manni-Bucau]

hi (again ;))

can you paste the full startup log when you deploy it as a war?




Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2016-12-08 10:37 GMT+01:00 vsolanki :

> Hi , We want to migrate our application from weblogic to tomee . We are
> using
> jsf application that uses ejb and managed bean. When we run the deployment
> we gt below warning for our jsf backing beans .We do not even find out
> whether the application has been successfully deployed or not . Below are
> the stack trace of warnings .We are very thankful to you if you provide any
> suggestion.8-Dec-2016 14:58:18.810 WARNING [http-nio-8080-exec-10]
> org.apache.catalina.startup.OpenEJBContextConfig.getJsfClasses class
> 'com.nsf.ecap.web.business.autocert.SubmissionCorrespondenceBBean' was
> found
> but can't be loaded as a JSF class*08-Dec-2016 14:58:18.811 WARNING
> [http-nio-8080-exec-10]
> org.apache.catalina.startup.OpenEJBContextConfig.getJsfClasses class
> 'com.nsf.ecap.web.business.bbeans.EcapWizardBBean' was found but can't be
> loaded as a JSF class08-Dec-2016 14:58:18.811 WARNING
> [http-nio-8080-exec-10]
> org.apache.catalina.startup.OpenEJBContextConfig.getJsfClasses class
> 'com.nsf.ecap.web.business.supplierscorecard.
> SupplierScoreCardReportBulkBBean'
> was found but can't be loaded as a JSF class08-Dec-2016 14:58:18.812
> WARNING
> [http-nio-8080-exec-10]
> org.apache.catalina.startup.OpenEJBContextConfig.getJsfClasses class
> 'com.nsf.ecap.web.business.resourcemanagement.
> ResourceCalibTeamCalibrationBBean'
> was found but can't be loaded as a JSF class08-Dec-2016 14:58:18.812
> WARNING
> [http-nio-8080-exec-10]
> org.apache.catalina.startup.OpenEJBContextConfig.getJsfClasses class
> 'com.nsf.web.components.EcapPerformQuestion' was found but can't be loaded
> as a JSF class08-Dec-2016 14:58:18.813 WARNING [http-nio-8080-exec-10]
> org.apache.catalina.startup.OpenEJBContextConfig.getJsfClasses class
> 'com.nsf.ecap.web.business.login.LayoutBBean' was found but can't be
> loaded
> as a JSF class08-Dec-2016 14:58:18.813 WARNING [http-nio-8080-exec-10]
> org.apache.catalina.startup.OpenEJBContextConfig.getJsfClasses class
> 'com.nsf.ecap.web.base.search.util.UserSelectedTab' was found but can't be
> loaded as a JSF class08-Dec-2016 14:58:18.814 WARNING
> [http-nio-8080-exec-10]
> org.apache.catalina.startup.OpenEJBContextConfig.getJsfClasses class
> 'com.nsf.ecap.web.base.bbean.ApplicationBBean' was found but can't be
> loaded
> as a JSF class08-Dec-2016 14:58:18.818 INFO [http-nio-8080-exec-10]
> sun.reflect.DelegatingMethodAccessorImpl.invoke At least one JAR was
> scanned
> for TLDs yet contained no TLDs. Enable debug logging for this logger for a
> complete list of JARs that were scanned but no TLDs were found in them.
> Skipping unneeded JARs during scanning can improve startup time and JSP
> compilation time.08-Dec-2016 14:58:18.834 INFO [http-nio-8080-exec-10]
> org.apache.catalina.core.StandardContext.reload Reloading Context with
> name
> [/ecap] is completed*
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.
> n4.nabble.com/Unable-to-run-jsf-application-that-uses-ejb-
> and-managed-bean-tp4680703.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.

Re: JNDI name issue

[Romain Manni-Bucau]

Hi

What do you try to achieve? do you need to look up a MDB? not sure this is
supposed to work

Le 7 déc. 2016 14:30, "Hicham Yahiaoui"  a
écrit :

> Hello,
>
> I'm using TomEE for my developments and I encoutered the following issue.
>
> In my system.properties file I have these two lines :
>
> openejb.deploymentId.format = {appId}/{ejbJarId}/{ejbName}
> openejb.jndiname.format = {ejbName}
>
> This configuration works perfectly for EJBs that are annotated with
> @Stateless but it does not for the @MessageDriven one.
>
> For @Stateless it's take the ejbName as JNDI name but for @MessageDriven it
> takes the deploymentId as JNDI name.
>
> Is it normal or am I missing something?
>
> Best regards,
>
> --
>
> Hicham Yahiaoui | EdifiXio
> *Mobile France:* +33 (0)7 61 43 24 48 | *Email:*
> hicham.yahia...@edifixio.com
> *Address :* 123 rue Jules Guesde, 92300 Levallois-Perret
>

Re: JAXRS Endpoints issue when Java Security Manager Enabled

[Romain Manni-Bucau]

Yes, this is what I mentionned. I don't have a ready to use policy file but
this one likely doesn't allow much. What is surprising is you don't have an
error in the logs?

Depending your level of confidence you can debug tomee here
https://github.com/apache/tomee/blob/master/container/openejb-core/src/main/java/org/apache/openejb/config/AnnotationDeployer.java#L5707

My suspicion is the scanning doesn't have access to the classes to scan.


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2016-12-07 9:56 GMT+01:00 Nisala Niroshana Nanayakkara <
nisalanirosh...@gmail.com>:

> Hi Romain,
>
> Thanks for the quick response. I have given all permission in the policy
> file. But it did not work. When I enabled the security logs,
> I observed that classes inside WEB-INF/classes has given the read
> permission also. But the endpoints are not working. If I packed those
> classes into a jar and put it to WEB-INF/lib. Please find the policy code
> segment below. Please go through it and let me know if there any problems.
>
> grant {
>permission java.net.SocketPermission "*:1-65535", "connect,resolve";
>permission java.util.PropertyPermission "http.proxyHost", "read";
>permission java.util.PropertyPermission "http.nonProxyHosts", "read";
>permission java.util.PropertyPermission "adb.converterutil", "read";
>permission java.lang.RuntimePermission "setContextClassLoader";
>permission java.lang.management.ManagementPermission "control";
>permission java.lang.reflect.ReflectPermission "suppressAccessChecks";
>permission javax.management.MBeanServerPermission "*";
>permission javax.management.MBeanPermission "*", "*";
>permission java.lang.RuntimePermission "accessDeclaredMembers";
>permission java.util.PropertyPermission "*", "read";
>permission java.util.PropertyPermission "*", "read,write";
>   permission java.lang.RuntimePermission "getenv.*";
>permission java.lang.RuntimePermission "getClassLoader";
>permission java.lang.RuntimePermission
> "accessClassInPackage.org.apache.catalina.loader";
> };
>
> Thanks,
> Nisala
>
> On Wed, Dec 7, 2016 at 2:15 PM, Romain Manni-Bucau 
> wrote:
>
> > hi
> >
> > did you configure the security manager policy? If not maybe start from
> > giving it AllPermission to check it works and then try to configure it to
> > ensure openejb and cxf can do their work.
> >
> >
> > Romain Manni-Bucau
> > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > <https://blog-rmannibucau.rhcloud.com> | Old Blog
> > <http://rmannibucau.wordpress.com> | Github <https://github.com/
> > rmannibucau> |
> > LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
> > <https://javaeefactory-rmannibucau.rhcloud.com>
> >
> > 2016-12-07 9:43 GMT+01:00 Nisala Niroshana Nanayakkara <
> > nisalanirosh...@gmail.com>:
> >
> > > Hi,
> > >
> > > I am trying to deploy javaee web app which contains some classes inside
> > the
> > > WEB-INF/classes directory. These classes exposes some JAX-RS enpoints.
> > Once
> > > I enabled the java security manager, those endpoints are not working
> > (404 -
> > > Not found error). It was working as expected when I disabled the java
> > > security manager. I tried to pack these classes inside WEB-INF/classes
> > > directory into a jar and put it in the WEB-INF/lib directory. Then the
> > > above mentioned issue is resolved and working as expected. Is there any
> > > special configuration to resolve this issue ? Can you provide your kind
> > > input about this matter.
> > >
> > > Thanks,
> > > Nisala
> > >
> > > --
> > >
> > > *Best Regards,Nisala Niroshana Nanayakkara,*
> > > *Bsc. Eng Undergraduate | Department of Computer Science & Engineering
> |
> > > University of Moratuwa | Sri Lanka*
> > > *Director | Leo Club of University of Moratuwa.*
> > >
> > > *Mobile | +94717600022*
> > >
> >
>
>
>
> --
>
> *Best Regards,Nisala Niroshana Nanayakkara,*
> *Bsc. Eng Undergraduate | Department of Computer Science & Engineering |
> University of Moratuwa | Sri Lanka*
> *Director | Leo Club of University of Moratuwa.*
>
> *Mobile | +94717600022*
>

Re: JAXRS Endpoints issue when Java Security Manager Enabled

[Romain Manni-Bucau]

hi

did you configure the security manager policy? If not maybe start from
giving it AllPermission to check it works and then try to configure it to
ensure openejb and cxf can do their work.


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2016-12-07 9:43 GMT+01:00 Nisala Niroshana Nanayakkara <
nisalanirosh...@gmail.com>:

> Hi,
>
> I am trying to deploy javaee web app which contains some classes inside the
> WEB-INF/classes directory. These classes exposes some JAX-RS enpoints. Once
> I enabled the java security manager, those endpoints are not working (404 -
> Not found error). It was working as expected when I disabled the java
> security manager. I tried to pack these classes inside WEB-INF/classes
> directory into a jar and put it in the WEB-INF/lib directory. Then the
> above mentioned issue is resolved and working as expected. Is there any
> special configuration to resolve this issue ? Can you provide your kind
> input about this matter.
>
> Thanks,
> Nisala
>
> --
>
> *Best Regards,Nisala Niroshana Nanayakkara,*
> *Bsc. Eng Undergraduate | Department of Computer Science & Engineering |
> University of Moratuwa | Sri Lanka*
> *Director | Leo Club of University of Moratuwa.*
>
> *Mobile | +94717600022*
>

Re: authorization for ejbd/http client

[Romain Manni-Bucau]

Le 6 déc. 2016 23:15, "David Blevins"  a écrit :


> On Dec 5, 2016, at 2:54 PM, Romain Manni-Bucau 
wrote:
>
>> You may have a desktop app or some other scenario where on your trusted
>> network, users can log in and you don’t want identity statically
configured
>> on the server side.
>>
>>
> This is a feature we don't have today at all so quite out of scope of the
> current mail (this is a new feature client wide, not related to udp
> probably)

We do have this exactly and I think is possibly a reason for the confusion.

Here’s a thread from 2008, "Desktop app communicating with EJB"

 - http://tomee-openejb.979440.n4.nabble.com/Desktop-app-
communicating-with-EJB-td980332.html <http://tomee-openejb.979440.
n4.nabble.com/Desktop-app-communicating-with-EJB-td980332.html>

Clients can login via the RemoteInitialContext parameters and have their
identity propagate with their remote calls.

The only change is that the user/pass could get applied at the http layer
as well.


This is unrelated to my comment. Point was we can use it with multicast -
which is the only issue - cause outside of the multicasted info - the url.


Nothing we couldnt enhance but as explained this is also not needed and
your example doesnt show this is wrong.



-David

Re: Commit deletion

[Romain Manni-Bucau]

Infra can for sure, locally it is not there anymore - that said as
mentionned, here we sadly lost some commits but no "head" code.


Le 6 déc. 2016 07:19, "Jean-Louis Monteiro"  a
écrit :

You mean locally or on the server?
I was wondering if Infra could help on this or not.

JLouis

--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com

On Mon, Dec 5, 2016 at 7:39 PM, Shahim Essaid  wrote:

> Is using the git log files under .git/logs/* not an option for finding the
> needed SHAs?  Git keeps all SHA changes for any branch in these files for
> some time (I think 30 days by default) so that the objects are not garbage
> collected. Any SHA in these files still counts as a reference to the git
> commits and they should be available on the machine where the changes
where
> made.
>
> Shahim
>
> On Mon, Dec 5, 2016 at 10:14 AM, Romain Manni-Bucau [via TomEE & OpenEJB]
<
> ml-node+s979440n4680676...@n4.nabble.com> wrote:
>
> > if you have the old history you can cherry pick it but guess we want to
> > enforce the consistency with master instead of ensure 1.7 and 7.x forks
-
> > was actually one of the goal of the initial commit.
> >
> >
> > Romain Manni-Bucau
> > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > <https://blog-rmannibucau.rhcloud.com> | Old Blog
> > <http://rmannibucau.wordpress.com> | Github <https://github.com/
> > rmannibucau> |
> > LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
> > <https://javaeefactory-rmannibucau.rhcloud.com>
> >
> > 2016-12-05 19:26 GMT+01:00 David Blevins <[hidden email]
> > <http:///user/SendEmail.jtp?type=node&node=4680676&i=0>>:
> >
> > > Is there a way to get the commit back?
> > >
> > >
> > > --
> > > David Blevins
> > > http://twitter.com/dblevins
> > > http://www.tomitribe.com
> > >
> > > > On Dec 5, 2016, at 5:13 AM, Romain Manni-Bucau <[hidden email]
> > <http:///user/SendEmail.jtp?type=node&node=4680676&i=1>>
> > > wrote:
> > > >
> > > > +1
> > > >
> > > > note that if you have the history you can still get back the commits
> > from
> > > > their hash (but for this one i lost them and JL didnt have them but
> > > wanted
> > > > to fix 1.7.x branch asap)
> > > >
> > > >
> > > > Romain Manni-Bucau
> > > > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > > > <https://blog-rmannibucau.rhcloud.com> | Old Blog
> > > > <http://rmannibucau.wordpress.com> | Github <https://github.com/
> > > rmannibucau> |
> > > > LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
> > > > <https://javaeefactory-rmannibucau.rhcloud.com>
> > > >
> > > > 2016-12-05 14:06 GMT+01:00 Jonathan Gallimore <
> > > [hidden email] <http:///user/SendEmail.jtp?
> type=node&node=4680676&i=2>>
> > > > :
> > > >
> > > >> Raising this to the top level, as opposed to being inside another
> > > thread...
> > > >>
> > > >> We had have a git reset --hard HEAD^X issued against the
tomee-1.7.x
> > > >> branch. The upshot is that although the commits in question are in
> > the
> > > >> repository somewhere, they no longer show up in the history for
that
> > > >> branch.
> > > >>
> > > >> This appears to be a fix for a completely unintentional merge from
> > > master,
> > > >> but I think we should avoid resetting heads or deleting commits
> > through
> > > any
> > > >> other means in the future.
> > > >>
> > > >> For reference, the discussion about this is here:
> > > >> http://tomee-openejb.979440.n4.nabble.com/today-s-git-
> > > >> commits-noise-td4680661.html
> > > >>
> > > >> Jon
> > > >>
> > >
> > >
> >
> >
> > --
> > If you reply to this email, your message will be added to the discussion
> > below:
> > http://tomee-openejb.979440.n4.nabble.com/Commit-deletion-
> > tp4680672p4680676.html
> > To start a new topic under TomEE Dev, email
ml-node+s979440n982480h66@n4.
> > nabble.com
> > To unsubscribe from TomEE Dev, click here
> > <http://tomee-openejb.979440.n4.nabble.com/template/
> NamlServlet.jtp?macro=unsubscribe_by_code&node=982480&code=
> c2hhaGltQGVzc2FpZC5jb218OTgyNDgwfDg2MDQwMTM5NA==>
> > .
> > NAML
> > <http://tomee-openejb.979440.n4.nabble.com/template/
> NamlServlet.jtp?macro=macro_viewer&id=instant_html%
> 21nabble%3Aemail.naml&base=nabble.naml.namespaces.
> BasicNamespace-nabble.view.web.template.NabbleNamespace-
> nabble.view.web.template.NodeNamespace&breadcrumbs=
> notify_subscribers%21nabble%3Aemail.naml-instant_emails%
> 21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
> >
>
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.
> n4.nabble.com/Commit-deletion-tp4680672p4680678.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.

Re: authorization for ejbd/http client

[Romain Manni-Bucau]

2016-12-05 23:48 GMT+01:00 David Blevins :

> > On Dec 5, 2016, at 10:29 AM, Romain Manni-Bucau 
> wrote:
> >
> > 2016-12-05 19:24 GMT+01:00 David Blevins :
> >
> >>
> >>> On Dec 5, 2016, at 4:21 AM, Romain Manni-Bucau 
> >> wrote:
> >>>
> >>> Concretely the proposal can be:
> >>>
> >>> p.setProperty(Context.INITIAL_CONTEXT_FACTORY,
> >> RemoteInitialContextFactory.
> >>> class.getName());
> >>> p.setProperty(Context.PROVIDER_URL, ejbUrl + "?authype=basic");
> >>> p.setProperty(Context.PRINCIPAL, "tomee");
> >>> p.setProperty(Context.CREDENTIAL, "password”);
> >>
> >> This would work.
> >>
> >>
> >>> That said it doesnt help for multicast since you will loose the
> >> credentials
> >>> where current solution works.
> >>
> >> From my perspective this is desired.
> >>
> >>
> > Can you detail that? What is the case where you would not secure by
> network
> > the cluster and not have a security hole (= what's the case where this
> > additional security layer is justified)?
>
> Let’s say you did have a closed and trusted network.  There still might be
> the use case where you have different clients on that network and want them
> to have their own identities.
>
>
We support it so not sure what your comment was about then


> You may have a desktop app or some other scenario where on your trusted
> network, users can log in and you don’t want identity statically configured
> on the server side.
>
>
This is a feature we don't have today at all so quite out of scope of the
current mail (this is a new feature client wide, not related to udp
probably)


> >> For those that may not understand the reference.  Effectively the
> >> multicast/multipoint code collects all the server URIs, aggregates them
> >> together and broadcasts them to all the clients.  Putting the login
> >> credentials in the URL the server broadcasts effectively broadcasts
> client
> >> information to all the clients, which would mean:
> >>
> >> - client identity and credentials would be configured on the server
> >> - all clients would share the same identity and credentials
> >> - credentials would be freely given to anyone who connects to
> >> multicast/multipoint
> >>
> >> The above `authype=basic` compromise does allow the credentials to be
> part
> >> of the client configuration, which is great.  It allows the same
> >> credentials the client sends over the ejbd protocol to also be sent over
> >> the HTTP layer.  The client would simply be logging in twice, once at
> the
> >> http level and once at the ejbd level.
> >>
> >>
> > Before going with this: how do you login if you don't have credential
> since
> > the multicast only share the url?
>
> Currently, users login via the InitialContext properties as in your hybrid
> proposal.
>
> p.setProperty(Context.PRINCIPAL, "tomee”);
> p.setProperty(Context.CREDENTIAL, "password”);
>
> Those login properties are sent in the EJBd protocol after connecting via
> the URL.  This currently does work with multicast(udp)/multipoint(tcp).
> It’s not perfect, but it functions and the net result is via ejbd or ejbds,
> the client can chose its identity when talking with a single server or a
> cluster.
>
>
This is something else, ejbd authentication vs container authentication.
Basic is the last one and is inherited then by the servlet integration
mecanism. I don't think you can/should compare both since they have to work
differently. That said this feature is still there until you use multiX
which doesnt have these properties.


> It’s not perfect, I’d have designed the identity tracking differently
> knowing what I know now.  But the basic idea is the client has to prove
> itself and the server will not give it the credentials.
>
> The change would be these also get used to do basic auth when layering the
> ejbd protocol over http allowing the tomcat http connector to be locked
> down and when we do that we continue to let the client chose the identity.
>

Already doable as explained so one of us miss something but can't yet
determine if it is me or you.


>
> > any global config is not acceptable there
> > - it would break the fact a single node can register multiple times.
>
> Not sure I followed this.  Both multicast(udp)/multipoint(tcp) filter out
> duplicates, but I think I’m missing the intent.
>
>
MultiX doesnt have the context hashtable so lack the identity to use.


>
> Hope any of the above is useful.
>
>
> -David
>
>

Re: authorization for ejbd/http client

[Romain Manni-Bucau]

2016-12-05 19:24 GMT+01:00 David Blevins :

>
> > On Dec 5, 2016, at 4:21 AM, Romain Manni-Bucau 
> wrote:
> >
> > Concretely the proposal can be:
> >
> > p.setProperty(Context.INITIAL_CONTEXT_FACTORY,
> RemoteInitialContextFactory.
> > class.getName());
> > p.setProperty(Context.PROVIDER_URL, ejbUrl + "?authype=basic");
> > p.setProperty(Context.PRINCIPAL, "tomee");
> > p.setProperty(Context.CREDENTIAL, "password”);
>
> This would work.
>
>
> > That said it doesnt help for multicast since you will loose the
> credentials
> > where current solution works.
>
> From my perspective this is desired.
>
>
Can you detail that? What is the case where you would not secure by network
the cluster and not have a security hole (= what's the case where this
additional security layer is justified)?


> For those that may not understand the reference.  Effectively the
> multicast/multipoint code collects all the server URIs, aggregates them
> together and broadcasts them to all the clients.  Putting the login
> credentials in the URL the server broadcasts effectively broadcasts client
> information to all the clients, which would mean:
>
>  - client identity and credentials would be configured on the server
>  - all clients would share the same identity and credentials
>  - credentials would be freely given to anyone who connects to
> multicast/multipoint
>
> The above `authype=basic` compromise does allow the credentials to be part
> of the client configuration, which is great.  It allows the same
> credentials the client sends over the ejbd protocol to also be sent over
> the HTTP layer.  The client would simply be logging in twice, once at the
> http level and once at the ejbd level.
>
>
Before going with this: how do you login if you don't have credential since
the multicast only share the url? any global config is not acceptable there
- it would break the fact a single node can register multiple times.


>
> -David
>
>

Re: Commit deletion

[Romain Manni-Bucau]

if you have the old history you can cherry pick it but guess we want to
enforce the consistency with master instead of ensure 1.7 and 7.x forks -
was actually one of the goal of the initial commit.


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2016-12-05 19:26 GMT+01:00 David Blevins :

> Is there a way to get the commit back?
>
>
> --
> David Blevins
> http://twitter.com/dblevins
> http://www.tomitribe.com
>
> > On Dec 5, 2016, at 5:13 AM, Romain Manni-Bucau 
> wrote:
> >
> > +1
> >
> > note that if you have the history you can still get back the commits from
> > their hash (but for this one i lost them and JL didnt have them but
> wanted
> > to fix 1.7.x branch asap)
> >
> >
> > Romain Manni-Bucau
> > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > <https://blog-rmannibucau.rhcloud.com> | Old Blog
> > <http://rmannibucau.wordpress.com> | Github <https://github.com/
> rmannibucau> |
> > LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
> > <https://javaeefactory-rmannibucau.rhcloud.com>
> >
> > 2016-12-05 14:06 GMT+01:00 Jonathan Gallimore <
> jonathan.gallim...@gmail.com>
> > :
> >
> >> Raising this to the top level, as opposed to being inside another
> thread...
> >>
> >> We had have a git reset --hard HEAD^X issued against the tomee-1.7.x
> >> branch. The upshot is that although the commits in question are in the
> >> repository somewhere, they no longer show up in the history for that
> >> branch.
> >>
> >> This appears to be a fix for a completely unintentional merge from
> master,
> >> but I think we should avoid resetting heads or deleting commits through
> any
> >> other means in the future.
> >>
> >> For reference, the discussion about this is here:
> >> http://tomee-openejb.979440.n4.nabble.com/today-s-git-
> >> commits-noise-td4680661.html
> >>
> >> Jon
> >>
>
>

Re: Commit deletion

[Romain Manni-Bucau]

+1

note that if you have the history you can still get back the commits from
their hash (but for this one i lost them and JL didnt have them but wanted
to fix 1.7.x branch asap)


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2016-12-05 14:06 GMT+01:00 Jonathan Gallimore 
:

> Raising this to the top level, as opposed to being inside another thread...
>
> We had have a git reset --hard HEAD^X issued against the tomee-1.7.x
> branch. The upshot is that although the commits in question are in the
> repository somewhere, they no longer show up in the history for that
> branch.
>
> This appears to be a fix for a completely unintentional merge from master,
> but I think we should avoid resetting heads or deleting commits through any
> other means in the future.
>
> For reference, the discussion about this is here:
> http://tomee-openejb.979440.n4.nabble.com/today-s-git-
> commits-noise-td4680661.html
>
> Jon
>

Re: authorization for ejbd/http client

[Romain Manni-Bucau]

2016-12-05 12:56 GMT+01:00 Jonathan Gallimore 
:

> On Mon, Dec 5, 2016 at 11:17 AM, Romain Manni-Bucau  >
> wrote:
>
> > Hi guys,
> >
> > Just a quite summary of last fixes we worked on with Jonathan regarding
> the
> > security for ejbd/http client:
> >
> > - we already have authorization parameter in the provider url for months
> > (years now?). This was not removed from the url so the user needed to
> > exclude some url from the access log if it was a security concern, this
> is
> > now done/safe
> >
>
> Awesome!
>
>
> > - we added basic.username and basic.password as shortcut for basic auth
> > which are just alimenting authorization header
> >
>
> Also awesome, thank you.
>
>
> > - we can now customize the authorization header (authorizationHeader
> param)
> >
> > All there url query parameters are stipped before doing the actual http
> > request for the reason mentionned in the first point.
> >
> > Another nice feature is the ability to cipher the properties passed to
> the
> > initial context either in a custom manner giving the context a
> > JNDIContext.Decipher implementation or relying on tomee ciphering (like
> for
> > resources) if your client is in tomee.
> >
>
> Great - I think that is really useful.
>
>
> >
> > David pointed out if you mix it with multicast you will pass in clear the
> > url value between instances. I think it is good enough cause multicast is
> > not that used and only safe in a secured (firewalled) DMZ anyway. Worse
> > case we could cipher the urls as well in the multicasting.
> >
>
> I hadn't appreciated the multicast issue, but I have worked in environments
> where that wouldn't be ok, unless the cipher used wasn't publicly
> available.
>
>
Assuming you don't use basic then it is still not ok by design so think it
is 1-1 there, no?


> One additional point that hasn't been mentioned above is: I feel that the
> ability to specify properties like so:
>
> final Properties p = new Properties();
> p.setProperty(Context.INITIAL_CONTEXT_FACTORY,
> RemoteInitialContextFactory.class.getName());
> p.setProperty(Context.PROVIDER_URL, ejbUrl);
> p.setProperty("tomee.ejb.authentication.basic.login", "tomee");
> p.setProperty("tomee.ejb.authentication.basic.password", "password");
> final InitialContext context = new InitialContext(p);
>
> is more user friendly and not necessarily at-odds with the above. The
> feedback is that this isn't portable, which I don't fully understand, but I
> do appreciate that it needs a bunch of different properties for different
> auth schemes and isn't infinitely flexible. Would be interested in people's
> thoughts.
>
>
Maybe there is a compromise which can work: reuse standard
principal/credential properties and set the header computation in the url.
Overall point is the client properties are rarely - never - well outsourced
and you most of the time only have the Context.* extracted as a
configuration when you need to switch between containers - speaking from
experience since technically you can extract properties.

Concretely the proposal can be:

p.setProperty(Context.INITIAL_CONTEXT_FACTORY, RemoteInitialContextFactory.
class.getName());
p.setProperty(Context.PROVIDER_URL, ejbUrl + "?authype=basic");
p.setProperty(Context.PRINCIPAL, "tomee");
p.setProperty(Context.CREDENTIAL, "password");


That said it doesnt help for multicast since you will loose the credentials
where current solution works.



> Cheers
>
> Jon
>

Re: today's git commits noise

[Romain Manni-Bucau]

2016-12-05 12:34 GMT+01:00 Jonathan Gallimore 
:

> Ok, so effectively head of tomee-1.7.x got shifted back a number of commits
> (git reset --hard HEAD^X, or something similar, right?). So those commits
> are still there "somewhere" but not visible within tomee-1.7.x. Got it. A
> revert may have given us a bit of a clearer view in the history as to what
> happened, but I understand why this route was taken. If the commits are
> still there somewhere, then I suspect that is ok. Generally I'd hope this
> would be a rare exception and we'd normally do a revert (sounds like that
> is the case).
>
>
yep


> Jon
>
> On Mon, Dec 5, 2016 at 11:09 AM, Romain Manni-Bucau  >
> wrote:
>
> > 2016-12-05 12:06 GMT+01:00 Jonathan Gallimore <
> > jonathan.gallim...@gmail.com>
> > :
> >
> > > No issue with the "noise", but thanks for heads up.
> > >
> > > One question - did we *delete* history? There's certainly commits I did
> > > after September 16th but before December 4th which are no-where to be
> > seen
> > > here. I didn't even know you could do that. Irrespective of whatever
> > issues
> > > there are with what I committed, should we ever do that? I'd have
> > thought a
> > > revert would be better.
> > >
> > >
> > My script kind of overwrite the 1.7 with 7.x history so revert was not
> > enough. JL pushed back the 1.7 branch until the history he got which was
> > the one i wanted to start from.
> >
> >
> > > Jon
> > >
> > > On Sat, Dec 3, 2016 at 5:02 PM, Romain Manni-Bucau <
> > rmannibu...@gmail.com>
> > > wrote:
> > >
> > > > Hi guys,
> > > >
> > > > sorry for the noise on commit list but messed up a git script (to
> merge
> > > > features from master) and lost part of 1.7.x. JL helped me to revert
> it
> > > and
> > > > fix it so we should be as expected now.
> > > >
> > > > Romain Manni-Bucau
> > > > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > > > <https://blog-rmannibucau.rhcloud.com> | Old Blog
> > > > <http://rmannibucau.wordpress.com> | Github <https://github.com/
> > > > rmannibucau> |
> > > > LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
> > > > <https://javaeefactory-rmannibucau.rhcloud.com>
> > > >
> > >
> >
>

authorization for ejbd/http client

[Romain Manni-Bucau]

Hi guys,

Just a quite summary of last fixes we worked on with Jonathan regarding the
security for ejbd/http client:

- we already have authorization parameter in the provider url for months
(years now?). This was not removed from the url so the user needed to
exclude some url from the access log if it was a security concern, this is
now done/safe
- we added basic.username and basic.password as shortcut for basic auth
which are just alimenting authorization header
- we can now customize the authorization header (authorizationHeader param)

All there url query parameters are stipped before doing the actual http
request for the reason mentionned in the first point.

Another nice feature is the ability to cipher the properties passed to the
initial context either in a custom manner giving the context a
JNDIContext.Decipher implementation or relying on tomee ciphering (like for
resources) if your client is in tomee.

David pointed out if you mix it with multicast you will pass in clear the
url value between instances. I think it is good enough cause multicast is
not that used and only safe in a secured (firewalled) DMZ anyway. Worse
case we could cipher the urls as well in the multicasting.

wdyt?

Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

Re: today's git commits noise

[Romain Manni-Bucau]

2016-12-05 12:06 GMT+01:00 Jonathan Gallimore 
:

> No issue with the "noise", but thanks for heads up.
>
> One question - did we *delete* history? There's certainly commits I did
> after September 16th but before December 4th which are no-where to be seen
> here. I didn't even know you could do that. Irrespective of whatever issues
> there are with what I committed, should we ever do that? I'd have thought a
> revert would be better.
>
>
My script kind of overwrite the 1.7 with 7.x history so revert was not
enough. JL pushed back the 1.7 branch until the history he got which was
the one i wanted to start from.


> Jon
>
> On Sat, Dec 3, 2016 at 5:02 PM, Romain Manni-Bucau 
> wrote:
>
> > Hi guys,
> >
> > sorry for the noise on commit list but messed up a git script (to merge
> > features from master) and lost part of 1.7.x. JL helped me to revert it
> and
> > fix it so we should be as expected now.
> >
> > Romain Manni-Bucau
> > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > <https://blog-rmannibucau.rhcloud.com> | Old Blog
> > <http://rmannibucau.wordpress.com> | Github <https://github.com/
> > rmannibucau> |
> > LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
> > <https://javaeefactory-rmannibucau.rhcloud.com>
> >
>

Re: reworking the website?

[Romain Manni-Bucau]

ok, will do now


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2016-12-04 8:46 GMT+01:00 agumbre...@tomitribe.com :

> +1
>
> agumbre...@tomitribe.com
> http://www.tomitribe.com
>
> Sent from my mobile device.
>
> - Reply message -
> From: "Jean-Louis Monteiro" 
> To: "dev@tomee.apache.org" 
> Subject: reworking the website?
> Date: Sat, Dec 3, 2016 18:20
>
> No I'm fine with that
>
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
> On Fri, Dec 2, 2016 at 11:04 PM, Romain Manni-Bucau  >
> wrote:
>
> > Hey guys
> >
> > Any objection to make ng the main (/) site? We can still enhance it later
> > but rhink it is already clearer and updatblz by anyone compared to
> current
> > one.
> >
> > Le 5 sept. 2016 22:21, "Romain Manni-Bucau"  a
> > écrit :
> >
> > > Le 5 sept. 2016 21:20, "David Blevins"  a
> > écrit :
> > > >
> > > > Looking great!
> > > >
> > > > I’d definitely be “pro” grouping.
> > >
> > > Was thinking to a convention on sample names for that (split on -?)
> > >
> > > >
> > > > Note on the Wall of fame, I think it’d be great to list everyone.
> > Maybe
> > > two sections “Most Recent” and “All time”.
> > > >
> > >
> > > First impl used github a bit like example page but data were not that
> > > accurate and rendering suffered from it so used a manual list thinking
> > > comitters and contributors can PR themself ( see https://github.com/
> > > rmannibucau/site-tomee-ng/blob/master/src/main/jbake/
> content/community/
> > > contributors.adoc )
> > >
> > > > --
> > > > David Blevins
> > > > http://twitter.com/dblevins
> > > > http://www.tomitribe.com
> > > >
> > > > > On Sep 2, 2016, at 10:18 AM, Romain Manni-Bucau <
> > rmannibu...@gmail.com>
> > > wrote:
> > > > >
> > > > > added a basic example section:
> > > > > http://tomee.apache.org/ng/examples/index.html
> > > > >
> > > > > feel free to hack anything you want there like tagging or whatever
> > but
> > > > > basic feature is there; Idea was to provide a search box instead of
> > > > > organizing the example to let them be browsable more efficiently.
> > > Doesn't
> > > > > prevent to organize them later but we need to find a convention
> then
> > > (page
> > > > > is generated)
> > > > >
> > > > >
> > > > > Romain Manni-Bucau
> > > > > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > > > > <https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
> > > > > <http://rmannibucau.wordpress.com> | Github <https://github.com/
> > > rmannibucau> |
> > > > > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
> > > > > <http://www.tomitribe.com> | JavaEE Factory
> > > > > <https://javaeefactory-rmannibucau.rhcloud.com>
> > > > >
> > > > > 2016-04-12 7:47 GMT+02:00 Romain Manni-Bucau <
> rmannibu...@gmail.com
> > >:
> > > > >
> > > > >> Hi Chris
> > > > >>
> > > > >> Le 12 avr. 2016 02:33, "Chris Owens" <
> ctag+open...@chris-owens.com>
> > a
> > > > >> écrit :
> > > > >>>
> > > > >>> Speaking as a reasonably-well-informed user of TomEE, who has
> been
> > > into
> > > > >> the
> > > > >>> code, but who is still very much an outsider, I would say that
> > > > >> documentation
> > > > >>> is probably the biggest obstacle to wider uptake. It's a project
> I
> > > would
> > > > >> be
> > > > >>> happy to work on. I'm willing to put the work in to do some
> serious
> > > > >> writing.
> > > > >>>
> > > > >>> Before we talk about documentation workflow, git

today's git commits noise

[Romain Manni-Bucau]

Hi guys,

sorry for the noise on commit list but messed up a git script (to merge
features from master) and lost part of 1.7.x. JL helped me to revert it and
fix it so we should be as expected now.

Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

Re: reworking the website?

[Romain Manni-Bucau]

Hey guys

Any objection to make ng the main (/) site? We can still enhance it later
but rhink it is already clearer and updatblz by anyone compared to current
one.

Le 5 sept. 2016 22:21, "Romain Manni-Bucau"  a
écrit :

> Le 5 sept. 2016 21:20, "David Blevins"  a écrit :
> >
> > Looking great!
> >
> > I’d definitely be “pro” grouping.
>
> Was thinking to a convention on sample names for that (split on -?)
>
> >
> > Note on the Wall of fame, I think it’d be great to list everyone.  Maybe
> two sections “Most Recent” and “All time”.
> >
>
> First impl used github a bit like example page but data were not that
> accurate and rendering suffered from it so used a manual list thinking
> comitters and contributors can PR themself ( see https://github.com/
> rmannibucau/site-tomee-ng/blob/master/src/main/jbake/content/community/
> contributors.adoc )
>
> > --
> > David Blevins
> > http://twitter.com/dblevins
> > http://www.tomitribe.com
> >
> > > On Sep 2, 2016, at 10:18 AM, Romain Manni-Bucau 
> wrote:
> > >
> > > added a basic example section:
> > > http://tomee.apache.org/ng/examples/index.html
> > >
> > > feel free to hack anything you want there like tagging or whatever but
> > > basic feature is there; Idea was to provide a search box instead of
> > > organizing the example to let them be browsable more efficiently.
> Doesn't
> > > prevent to organize them later but we need to find a convention then
> (page
> > > is generated)
> > >
> > >
> > > Romain Manni-Bucau
> > > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > > <https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog
> > > <http://rmannibucau.wordpress.com> | Github <https://github.com/
> rmannibucau> |
> > > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
> > > <http://www.tomitribe.com> | JavaEE Factory
> > > <https://javaeefactory-rmannibucau.rhcloud.com>
> > >
> > > 2016-04-12 7:47 GMT+02:00 Romain Manni-Bucau :
> > >
> > >> Hi Chris
> > >>
> > >> Le 12 avr. 2016 02:33, "Chris Owens"  a
> > >> écrit :
> > >>>
> > >>> Speaking as a reasonably-well-informed user of TomEE, who has been
> into
> > >> the
> > >>> code, but who is still very much an outsider, I would say that
> > >> documentation
> > >>> is probably the biggest obstacle to wider uptake. It's a project I
> would
> > >> be
> > >>> happy to work on. I'm willing to put the work in to do some serious
> > >> writing.
> > >>>
> > >>> Before we talk about documentation workflow, git vs other models,
> CMSes,
> > >>> etc., I think there are some much more basic questions to address:
> > >>>
> > >>> -- Who is the intended audience for each major portion of the
> > >> documentation?
> > >>>
> > >>
> > >> I d say people not able to go to code and in that category 2
> > >> subcategories: admin and dev.
> > >>
> > >>> -- For TomEE Components that are not owned by this project (e.g.,
> Tomcat,
> > >>> cxf, JMS, etc.), how shall our documentation interact with that
> > >> component's
> > >>> "native" documentation? By reference? By duplication? Other?
> > >>>
> > >>
> > >> Reference + enrichment when needed. Really against duplication.
> > >>
> > >>> -- What are the major reference topics that need to be covered? (For
> > >>> example, Contexts, Classloaders, Configuration, Testing, Embedded,
> etc)?
> > >>>
> > >>
> > >> Idea was to start with some basics and add info depending the list
> > >> questions.
> > >>
> > >>> -- What are the major tutorial or "how-to" threads that need to be
> > >> covered?
> > >>>
> > >>>
> > >>
> > >> Same there. Should also probably consider rework very hard examples to
> > >> make them useful and more explicit (arquillian website is a great
> example
> > >> there).
> > >>
> > >>>
> > >>>
> > >>>
> > >>> --
> > >>> View this message in context: http://tomee-openejb.979440.
> > >> n4.nabble.com/reworking-the-website-tp4677918p4678116.html
> > >>> Sent from the TomEE Dev mailing list archive at Nabble.com.
> > >>
> >
>