Turbine webapp issues

Discussion:

Jeffery Painter

2017-12-13 15:42:32 UTC

Hi Georg,

A couple things I have noticed and these updates are in my sample
turbine-flux app on github.

When creating a new project from the archetype (using the Maven wizard
in eclipse), I have seen this issue pop up, and I have been fixing it
manually for my projects. Just wondering if this is something we can
address in the archetype itself if you agree.

By default, the web.xml definition throws an error in Eclipse:

*Referenced file contains errors
(http://www.oracle.com/webfolder/technetwork/jsc/xml/ns/javaee/web-app_2_5.xsd).
*

I had updated my web.xml with this version instead (and it works with
Tomcat 8.5.x as my local server runtime environment).

Java EE 7 Schema (April 30, 2013)
http://www.oracle.com/webfolder/technetwork/jsc/xml/ns/javaee/index.html

<web-app xmlns="http://xmlns.jcp.org/xml/ns/javaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee
http://xmlns.jcp.org/xml/ns/javaee/web-app_3_1.xsd"
version="3.1"
metadata-complete="true">

The next issue I had was with Tomcat and getting JNDI to initialize. I
created a META-INF/context.xml with the following definition:

<?xml version='1.0' encoding='utf-8'?>
<Context>
    <WatchedResource>WEB-INF/web.xml</WatchedResource>
<WatchedResource>${catalina.base}/conf/web.xml</WatchedResource>
    <Resource name="jdbc/turbine" global="jdbc/turbine"
auth="Container" type="javax.sql.DataSource"
        driverClassName="com.mysql.jdbc.Driver"
        url="jdbc:mysql://localhost:3306/turbine"
        username="db_user" password="db_password"
        maxTotal="100" maxIdle="20" minIdle="5" maxWaitMillis="10000"/>
</Context>

And that seems to clear that up so it starts immediately within
Eclipse/Tomcat configuration. Otherwise, out of the box, the user gets
the following exception:

Horrible Exception: org.apache.turbine.services.InstantiationException: Service AvalonComponentService failed to initialize

If you agree with these changes, I am happy to commit them to the
Turbine webapp archetype.

--
Jeffery

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-***@turbine.apache.org
For additional commands, e-mail: dev-***@turbine.apache.org

Georg Kallidis

2017-12-13 16:25:49 UTC

Permalink

If we change to Servlet 3.1 Tomcat 8 is required, cft.
https://tomcat.apache.org/whichversion.html.
We may update to 3.1 after this release is done (Turbine 4.1), as we still
support Java 6, which Tomcat 8 stops to do.
May be the following URL - valid in in Tomcat 6 and 7 - is sufficient:
http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd. Does Eclipse throw an
error with this?
Otherwise please go ahead, thanks!
Best regards, Georg

Von: Jeffery Painter <***@jivecast.com>
An: Turbine Developers List <***@turbine.apache.org>
Datum: 13.12.2017 16:42
Betreff: Turbine webapp issues

Hi Georg,

A couple things I have noticed and these updates are in my sample
turbine-flux app on github.

When creating a new project from the archetype (using the Maven wizard
in eclipse), I have seen this issue pop up, and I have been fixing it
manually for my projects. Just wondering if this is something we can
address in the archetype itself if you agree.

By default, the web.xml definition throws an error in Eclipse:

*Referenced file contains errors
(
http://www.oracle.com/webfolder/technetwork/jsc/xml/ns/javaee/web-app_2_5.xsd
).
*

I had updated my web.xml with this version instead (and it works with
Tomcat 8.5.x as my local server runtime environment).

Java EE 7 Schema (April 30, 2013)
http://www.oracle.com/webfolder/technetwork/jsc/xml/ns/javaee/index.html

<web-app xmlns="http://xmlns.jcp.org/xml/ns/javaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee
http://xmlns.jcp.org/xml/ns/javaee/web-app_3_1.xsd"
version="3.1"
metadata-complete="true">

The next issue I had was with Tomcat and getting JNDI to initialize. I
created a META-INF/context.xml with the following definition:

<?xml version='1.0' encoding='utf-8'?>
<Context>
<WatchedResource>WEB-INF/web.xml</WatchedResource>
<WatchedResource>${catalina.base}/conf/web.xml</WatchedResource>
<Resource name="jdbc/turbine" global="jdbc/turbine"
auth="Container" type="javax.sql.DataSource"
driverClassName="com.mysql.jdbc.Driver"
url="jdbc:mysql://localhost:3306/turbine"
username="db_user" password="db_password"
maxTotal="100" maxIdle="20" minIdle="5" maxWaitMillis="10000"/>
</Context>

And that seems to clear that up so it starts immediately within
Eclipse/Tomcat configuration. Otherwise, out of the box, the user gets
the following exception:

Horrible Exception: org.apache.turbine.services.InstantiationException:
Service AvalonComponentService failed to initialize

If you agree with these changes, I am happy to commit them to the
Turbine webapp archetype.

--
Jeffery

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-***@turbine.apache.org
For additional commands, e-mail: dev-***@turbine.apache.org

Jeffery Painter

2017-12-13 17:45:02 UTC

Permalink

That worked and I have submitted my updates to the svn server. Just one
more issue, and this is probably platform related.

In the docs/sample-mysql-data/_turbine-security-data.sql file, the table
names for insert into TURBINE_PERMISSION, TURBINE_ROLE, etc are all in
lower case. At least on my linux machine, this results in the INSERT
statements failing since the tables were created in UPPER case.

Do you mind if I go ahead and update those as well? I imagine you may
have different results if working on windows machines.

--
Jeff

Post by Georg Kallidis
If we change to Servlet 3.1 Tomcat 8 is required, cft.
https://tomcat.apache.org/whichversion.html.
We may update to 3.1 after this release is done (Turbine 4.1), as we still
support Java 6, which Tomcat 8 stops to do.
http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd. Does Eclipse throw an
error with this?
Otherwise please go ahead, thanks!
Best regards, Georg
Datum: 13.12.2017 16:42
Betreff: Turbine webapp issues
Hi Georg,
A couple things I have noticed and these updates are in my sample
turbine-flux app on github.
When creating a new project from the archetype (using the Maven wizard
in eclipse), I have seen this issue pop up, and I have been fixing it
manually for my projects. Just wondering if this is something we can
address in the archetype itself if you agree.
*Referenced file contains errors
(
http://www.oracle.com/webfolder/technetwork/jsc/xml/ns/javaee/web-app_2_5.xsd
).
*
I had updated my web.xml with this version instead (and it works with
Tomcat 8.5.x as my local server runtime environment).
Java EE 7 Schema (April 30, 2013)
http://www.oracle.com/webfolder/technetwork/jsc/xml/ns/javaee/index.html
<web-app xmlns="http://xmlns.jcp.org/xml/ns/javaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee
http://xmlns.jcp.org/xml/ns/javaee/web-app_3_1.xsd"
version="3.1"
metadata-complete="true">
The next issue I had was with Tomcat and getting JNDI to initialize. I
<?xml version='1.0' encoding='utf-8'?>
<Context>
<WatchedResource>WEB-INF/web.xml</WatchedResource>
<WatchedResource>${catalina.base}/conf/web.xml</WatchedResource>
<Resource name="jdbc/turbine" global="jdbc/turbine"
auth="Container" type="javax.sql.DataSource"
driverClassName="com.mysql.jdbc.Driver"
url="jdbc:mysql://localhost:3306/turbine"
username="db_user" password="db_password"
maxTotal="100" maxIdle="20" minIdle="5" maxWaitMillis="10000"/>
</Context>
And that seems to clear that up so it starts immediately within
Eclipse/Tomcat configuration. Otherwise, out of the box, the user gets
Service AvalonComponentService failed to initialize
If you agree with these changes, I am happy to commit them to the
Turbine webapp archetype.
--
Jeffery
---------------------------------------------------------------------

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-***@turbine.apache.org
For additional commands, e-mail: dev-***@turbine.apache.org

Georg Kallidis

2017-12-14 14:41:11 UTC

Permalink

that's true, I was unaware of it. We should make this consistent, of
course. Thanks!

I Žve now updated the Turbine webapp due to needed changes in Fulcrum
Security API (optionally lazy loading group and role).

-Georg

Von: Jeffery Painter <***@jivecast.com>
An: ***@turbine.apache.org
Datum: 13.12.2017 18:45
Betreff: Re: Turbine webapp issues

That worked and I have submitted my updates to the svn server. Just one
more issue, and this is probably platform related.

In the docs/sample-mysql-data/_turbine-security-data.sql file, the table
names for insert into TURBINE_PERMISSION, TURBINE_ROLE, etc are all in
lower case. At least on my linux machine, this results in the INSERT
statements failing since the tables were created in UPPER case.

Do you mind if I go ahead and update those as well? I imagine you may
have different results if working on windows machines.

--
Jeff

http://www.oracle.com/webfolder/technetwork/jsc/xml/ns/javaee/web-app_2_5.xsd

Post by Georg Kallidis
).
*
I had updated my web.xml with this version instead (and it works with
Tomcat 8.5.x as my local server runtime environment).
Java EE 7 Schema (April 30, 2013)
http://www.oracle.com/webfolder/technetwork/jsc/xml/ns/javaee/index.html
<web-app xmlns="http://xmlns.jcp.org/xml/ns/javaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee
http://xmlns.jcp.org/xml/ns/javaee/web-app_3_1.xsd"
version="3.1"
metadata-complete="true">
The next issue I had was with Tomcat and getting JNDI to initialize. I
<?xml version='1.0' encoding='utf-8'?>
<Context>
<WatchedResource>WEB-INF/web.xml</WatchedResource>
<WatchedResource>${catalina.base}/conf/web.xml</WatchedResource>
<Resource name="jdbc/turbine" global="jdbc/turbine"
auth="Container" type="javax.sql.DataSource"
driverClassName="com.mysql.jdbc.Driver"
url="jdbc:mysql://localhost:3306/turbine"
username="db_user" password="db_password"
maxTotal="100" maxIdle="20" minIdle="5"

maxWaitMillis="10000"/>

Post by Georg Kallidis
</Context>
And that seems to clear that up so it starts immediately within
Eclipse/Tomcat configuration. Otherwise, out of the box, the user gets
Service AvalonComponentService failed to initialize
If you agree with these changes, I am happy to commit them to the
Turbine webapp archetype.
--
Jeffery
---------------------------------------------------------------------

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-***@turbine.apache.org
For additional commands, e-mail: dev-***@turbine.apache.org

Jeffery Painter

2017-12-14 18:18:37 UTC

Permalink

I made the update Georg. I am leaving Saturday for vacation and will be
out for a couple of weeks. I was going to write up a nice detailed
tutorial to help new users get started building a Turbine webapp from
this archetype. It will give me something to do over the break that
doesn't require coding. haha!

I hope we could use it on the main turbine web site as it is lacking I
think in solid direction about how to really get started.

I am also thinking of proposing a talk at the Open Source 101 workshop
in February around Turbine, and I would like to develop it further for
ApacheCon next year possibly. It has been a long time since Turbine was
featured at ApacheCon as far as I can tell.

http://opensource101.com/call-for-speakers/

Let me know your thoughts and if there is anything else I can do. Happy
holidays to anyone else listening to this list :-)

--
Jeff

Post by Georg Kallidis
that's true, I was unaware of it. We should make this consistent, of
course. Thanks!
I ´ve now updated the Turbine webapp due to needed changes in Fulcrum
Security API (optionally lazy loading group and role).
-Georg
Datum: 13.12.2017 18:45
Betreff: Re: Turbine webapp issues
That worked and I have submitted my updates to the svn server. Just one
more issue, and this is probably platform related.
In the docs/sample-mysql-data/_turbine-security-data.sql file, the table
names for insert into TURBINE_PERMISSION, TURBINE_ROLE, etc are all in
lower case. At least on my linux machine, this results in the INSERT
statements failing since the tables were created in UPPER case.
Do you mind if I go ahead and update those as well? I imagine you may
have different results if working on windows machines.
--
Jeff

Post by Georg Kallidis
If we change to Servlet 3.1 Tomcat 8 is required, cft.
https://tomcat.apache.org/whichversion.html.
We may update to 3.1 after this release is done (Turbine 4.1), as we

still

Post by Georg Kallidis
support Java 6, which Tomcat 8 stops to do.
http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd. Does Eclipse throw an
error with this?
Otherwise please go ahead, thanks!
Best regards, Georg
Datum: 13.12.2017 16:42
Betreff: Turbine webapp issues
Hi Georg,
A couple things I have noticed and these updates are in my sample
turbine-flux app on github.
When creating a new project from the archetype (using the Maven wizard
in eclipse), I have seen this issue pop up, and I have been fixing it
manually for my projects. Just wondering if this is something we can
address in the archetype itself if you agree.
*Referenced file contains errors
(

http://www.oracle.com/webfolder/technetwork/jsc/xml/ns/javaee/web-app_2_5.xsd

maxWaitMillis="10000"/>

---------------------------------------------------------------------

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-***@turbine.apache.org
For additional commands, e-mail: dev-***@turbine.apache.org

Georg Kallidis

2017-12-15 14:24:29 UTC

Permalink

Hi Jeff,
happy holidays! I support, what you are aiming to, tutorial and workshop
at any rate. Just as a hint, may be the Turbine Wiki
https://wiki.apache.org/turbine is of any use in preparation any of these?
I propose the ongoingrelease process would then take place in January..
Considering a live session, I'll bet, that one of the first questions to
be answered would be, what the future of Turbine is about.
Answering this seems not quite easy at the moment, as we have to elaborate
it more, besides that we targeting Java 8, and may be Servlet 3.1. At the
moment comes into my mind:
- Using Tamaya as configuration? (cft.
https://wiki.apache.org/turbine/Turbine5):
https://tamaya.incubator.apache.org/start.html
- Vaadin integration, which you mentioned earlier and may be more on the
frontend side, but including a real shift in the bigger picture.
- Another thing I could think of is Clojure (and ClojureScript). Clojure
is with its functional approach quite different even in building using
leiningen than Java OO - but it compiles to Java and ClojureScript is
another big option may be in combination with vue,
https://github.com/Gonzih/glue. Thomas already did one step to functional
immutability e.g. in class
o.a.fulcrum.security.model.turbine.TurbineAccessControlListImpl ;-)! I
think Clj might be of use, as a router or just as a component (some
Velocity/Compojure/Ring code does already exist on GitHub). This might
also be a hackathon theme. So, keep inspired!
Best regards, Georg

Von: Jeffery Painter <***@jivecast.com>
An: ***@turbine.apache.org
Datum: 14.12.2017 19:18
Betreff: Re: Turbine webapp issues

I made the update Georg. I am leaving Saturday for vacation and will be
out for a couple of weeks. I was going to write up a nice detailed
tutorial to help new users get started building a Turbine webapp from
this archetype. It will give me something to do over the break that
doesn't require coding. haha!

I hope we could use it on the main turbine web site as it is lacking I
think in solid direction about how to really get started.

I am also thinking of proposing a talk at the Open Source 101 workshop
in February around Turbine, and I would like to develop it further for
ApacheCon next year possibly. It has been a long time since Turbine was
featured at ApacheCon as far as I can tell.

http://opensource101.com/call-for-speakers/

Let me know your thoughts and if there is anything else I can do. Happy
holidays to anyone else listening to this list :-)

--
Jeff

Post by Georg Kallidis
that's true, I was unaware of it. We should make this consistent, of
course. Thanks!
I Žve now updated the Turbine webapp due to needed changes in Fulcrum
Security API (optionally lazy loading group and role).
-Georg
Datum: 13.12.2017 18:45
Betreff: Re: Turbine webapp issues
That worked and I have submitted my updates to the svn server. Just one
more issue, and this is probably platform related.
In the docs/sample-mysql-data/_turbine-security-data.sql file, the table
names for insert into TURBINE_PERMISSION, TURBINE_ROLE, etc are all in
lower case. At least on my linux machine, this results in the INSERT
statements failing since the tables were created in UPPER case.
Do you mind if I go ahead and update those as well? I imagine you may
have different results if working on windows machines.
--
Jeff

Post by Georg Kallidis
If we change to Servlet 3.1 Tomcat 8 is required, cft.
https://tomcat.apache.org/whichversion.html.
We may update to 3.1 after this release is done (Turbine 4.1), as we

still

http://www.oracle.com/webfolder/technetwork/jsc/xml/ns/javaee/web-app_2_5.xsd

Post by Georg Kallidis

Post by Georg Kallidis
).
*
I had updated my web.xml with this version instead (and it works with
Tomcat 8.5.x as my local server runtime environment).
Java EE 7 Schema (April 30, 2013)

http://www.oracle.com/webfolder/technetwork/jsc/xml/ns/javaee/index.html

Post by Georg Kallidis

Post by Georg Kallidis
<web-app xmlns="http://xmlns.jcp.org/xml/ns/javaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee
http://xmlns.jcp.org/xml/ns/javaee/web-app_3_1.xsd"
version="3.1"
metadata-complete="true">
The next issue I had was with Tomcat and getting JNDI to initialize. I
<?xml version='1.0' encoding='utf-8'?>
<Context>
<WatchedResource>WEB-INF/web.xml</WatchedResource>
<WatchedResource>${catalina.base}/conf/web.xml</WatchedResource>
<Resource name="jdbc/turbine" global="jdbc/turbine"
auth="Container" type="javax.sql.DataSource"
driverClassName="com.mysql.jdbc.Driver"
url="jdbc:mysql://localhost:3306/turbine"
username="db_user" password="db_password"
maxTotal="100" maxIdle="20" minIdle="5"

maxWaitMillis="10000"/>

---------------------------------------------------------------------

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-***@turbine.apache.org
For additional commands, e-mail: dev-***@turbine.apache.org