Re: Why unusedProperty warning?

Fixed thanks. -- View this message in context: http://tomee-openejb.979440.n4.nabble.com/Why-unusedProperty-warning-tp4679516p4679523.html Sent from the TomEE Users mailing list archive at Nabble.com.

Re: Why unusedProperty warning?

error is: JdbcDriver = org.mariadb.jdbc.MariaDbDataSource if you set a datasource and not a driver then the datasource is created with all properties as well as the poll so the not matching one are logged (it litterally mixes/merges 2 resources creation in one) just use org.mariadb.jdbc.Driver in

Re: Why unusedProperty warning?

http://pastebin.com/KuCzeFSY -- View this message in context: http://tomee-openejb.979440.n4.nabble.com/Why-unusedProperty-warning-tp4679516p4679521.html Sent from the TomEE Users mailing list archive at Nabble.com.

Re: Why unusedProperty warning?

means that with this declaration you shouldn't get that much warnings, in particular 5 first are always supported whatever jdbc pool you use would be interesting if you can share on a pastebin or gist the actual tomee.xml file Romain Manni-Bucau @rmannibucau |

Re: Why unusedProperty warning?

Sorry I am so dumb, but I don't know what is meant by "should be fixed". I got the keywords from TomEE documentation here . JdbcDriver = org.mariadb.jdbc.MariaDbDataSource JdbcUrl = jdbc:mysql://localhost:3306/aforumsdb UserName = aforums Passw

Re: Why unusedProperty warning?

Hi Looks like you configure a tomee datasource setting a custom class-name. If so warnings are accurate and config should be fixed. Le 27 juil. 2016 22:17, "paulhr" a écrit : > Just getting started. Noticed during a reboot just after adding a MariaDB > resource I am getting these warnings. Ar

Re: 7.0.2-SNAPSHOT artifacts + maven

It's working now, thanks 2016-07-26 19:12 GMT-03:00 Romain Manni-Bucau : > m2e or settings.xml setup > > -U should log what it tries to resolves and fails > > cleaning your m2 repo folder org/apache/tomee/tomee-embedded can help too > > > Romain Manni-Bucau > @rmannibucau

Why unusedProperty warning?

Just getting started. Noticed during a reboot just after adding a MariaDB resource I am getting these warnings. Are the safe to ignore? Why am I getting them? I have not deployed the app yet that needs the MariaDB. Jul 27, 2016 4:08:56 PM org.apache.openejb.assembler.classic.Assembler createRe

Re: tomcat-demo error with a MariaDB addition to tomee.xml

Caused by... Caused by: java.sql.SQLException: url parsing error : '//' is not present in the url jdbc:mysql:localhost:3306/usqueforumsdb In the Tomee documentation https://tomee.apache.org/Configuring-in-tomee.html the example is missing the "//" between the "mysql:" and the "localhost" -- Vi

tomcat-demo error with a MariaDB addition to tomee.xml

I added a JDBC resource to my tomee.xml file, added a MariaDB JAR file (mariadb-java-client-1.4.6.jar), and now I am getting error about the tomcat-demo web app. = tomee.xml = JdbcDriver org.mariadb.jdbc.MariaDbDataSource JdbcUrl jdbc:mysql:

Re: Default webapp deployment

Why not using resources.xml? this one will work Romain Manni-Bucau @rmannibucau | Blog | Old Wordpress Blog | Github | LinkedIn

Re: Default webapp deployment

On 25/07/16 19:12, Romain Manni-Bucau wrote: Hi Fabien, The alternative is to define it in conf/context.xml (and put it outside of the managed folder (webapps/ per default) or deactivate the auto deployment of webapps/ on the host. Thanks Romain, This works except for the postgresql database d

Re: secure the tomee/ejb path

Hi, easiest is IMHO to create physically a tomee webapp (= folder) with the ServerServlet defined (http://tomee.apache.org/ejbd-transport.html) and define the webapp security you want in web.xml. It also needs to extend HttpConnectionFactory ( https://github.com/apache/tomee/blob/master/server/ope

secure the tomee/ejb path

Hi to all! when deploy an application who have remote interfaces accesible from remote ('http://localhost:8080/tomee/ejb'), the access to a potential attacker is freely guaranteed. How can I protect access even with a simple BASIC authentication? It is possible, how can I access the remote envir

Re: warning during datasource configuration - SOLVED

2016-07-27 16:51 GMT+02:00 Edoardo Panfili : > Il 27/07/16 07:19, Romain Manni-Bucau ha scritto: > >> Yes, (tomee/openejb is the same project): you got the replaced instance so >> lookup happens too late to get tomcat instance. >> > Very minimal working configurations: > > The below $webapp/META-I

Re: warning during datasource configuration - SOLVED

Il 27/07/16 07:19, Romain Manni-Bucau ha scritto: Yes, (tomee/openejb is the same project): you got the replaced instance so lookup happens too late to get tomcat instance. Very minimal working configurations: The below $webapp/META-INF/context.xml configuration works with no warnings sing

Re: EJB application works in TomEE Plus but not TomEE webprofile

if system.properties config is the same and deployment too then there is no particular reason it should fail. are you able to reproduce it using tomee-maven-plugin in a jar plugin and switching tomeeClassifier value? If so can you share a small sample on github? Romain Manni-Bucau @rmannibucau <

Re: EJB application works in TomEE Plus but not TomEE webprofile

Thank you for the response. Our code is not using jaxws or jms, here is the code- just doing a jndi lookup: /StringBuilder url = new StringBuilder("global/hq_calendarEjb/"); url.append(isLiferaySpecificService?"Liferay":"").append(ejbInterfaceClass.getSimpleName()).append("Bean!").append(ejbInterf

Re: Migrate TomEE 1.7.x to 7.x : Java to JSON Issue

That's because cxf JSONProvider depends on jettison and this class is in the container. You can try to add in conf/system.properties: openejb.forced-load=org.apache.cxf.jaxrs.provider.json.JSONProvider to try to enforce it to be loaded from the webapp Romain Manni-Bucau @rmannibucau

Re: Migrate TomEE 1.7.x to 7.x : Java to JSON Issue

It's work ! Merci ! I configure openejb-jar.xml : http://www.openejb.org/openejb-jar/1.1"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://www.openejb.org/openejb-jar/1.1";> cxf.jaxrs.providers = org.apache.cxf.jaxrs.provider.json.JSO

Re: EJB application works in TomEE Plus but not TomEE webprofile

Hi If you use jaxws or jms, it is not part of webprofile so "expected". Le 27 juil. 2016 13:36, "sweiss77" a écrit : > I have an EJB application that is packaged as a JAR file. It works fine > when > deployed to TomEE Plus (to the apps directory) but does not work when > deployed to TomEE webpr

Re: Migrate TomEE 1.7.x to 7.x : Java to JSON Issue

Hi Julien Le 27 juil. 2016 13:36, "JulienB" a écrit : > > > I encounter a problem around Apache Johnzon to convert a Java object to > Json. > I have two class A and B having a relation bi-directionnal. > With TomEE 1.7.x and XML annotations (like @XmlInverseReference or > @XmlElement), no problem

Migrate TomEE 1.7.x to 7.x : Java to JSON Issue

I encounter a problem around Apache Johnzon to convert a Java object to Json. I have two class A and B having a relation bi-directionnal. With TomEE 1.7.x and XML annotations (like @XmlInverseReference or @XmlElement), no problem. On TomEE 7.x, Apache Johnzon loops between two instance for object

EJB application works in TomEE Plus but not TomEE webprofile

I have an EJB application that is packaged as a JAR file. It works fine when deployed to TomEE Plus (to the apps directory) but does not work when deployed to TomEE webprofile. Is it possible that this is because I am connecting to the session beans via http (port 8080) and the web profile version