Problem with Spring 3.1.3 about dellroad-stuff HOT 14 CLOSED

dellroad-stuff 1.0.571 is built against Spring 3.1.x, so I'm not sure what your 
problem is. What makes you think it requires 3.0.6?

Please provide more details, e.g., a stack trace.

Hi, thanks for fast replay.

I attached part of screen from eclipse with dependencies. When I don't define 
explicitly spring dependencies maven downloads both 3.0.6 and 3.1.3 version.

When I removed PropertyPlaceholderConfigurer  from Spring xml configuration 
file I managed to run my app. 
Please look at similar problem at that site 
http://stackoverflow.com/questions/8500708/spring-3-1-entitymanagerfactory-java-
lang-nosuchfielderror-null-error/8500741#8500741

This is some problem with maven. I don't use maven and so unfortunately I can't 
offer much help.

In this case, I have no idea where the spring 3.0.x dependency is coming from, 
but I know it's not coming from dellroad-stuff itself. Maven is adding that 
dependency somehow, possibly from some other module you are using?

The dellroad-stuff dependencies are properly defined in Ivy Roundup. If you 
want to use ivy, then you might try using the IvyDE plug-in for Eclipse with 
Ivy Roundup.

Otherwise, you may need to tell maven that you have an explicit dependency on 
spring 3.1.x. This is probably a much simpler solution.

Let me know what you find out.

Well, I already declared dependencies explicitly (spring-context, 
spring-aspects, and spring-web to version 3.1.3) - see attached picture.
That didn't helped. 

I think I'll have to download sources and try to build it for myself.

Pan,

This is not a build-time problem. The dellroad-stuff JAR was built with spring 
3.1.x, I assure you. This is not a problem that can be fixed by doing anything 
with dellroad-stuff, including re-building it.

This is a problem on your end somehow, having to do with Maven and Eclipse. For 
example, is there some other module that is pulling in spring 3.0.x? Maybe 
dellroad-stuff appears in a stack trace when you happen to see the problem 
occur at runtime, but that's just a coincidence.

I wish you would stop blaming dellroad-stuff (and giving the add-on low 
ratings). You need to track down the *real* cause of the problem.

Here is pom.xml from you library. Pleas look at dependencies versions

<?xml version="1.0" encoding="utf-8"?>

<!--
     Note: this file is constructed by hand (I don't use maven).
     If you see any problems please email archie at dellroad.org.
-->

<!-- $Id: pom.xml 176 2011-10-31 15:18:03Z archie.cobbs $ -->
<project xmlns="http://maven.apache.org/POM/4.0.0"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
    <modelVersion>4.0.0</modelVersion>
    <groupId>org.dellroad</groupId>
    <artifactId>dellroad-stuff-vaadin</artifactId>
    <version>1.0.571</version>
    <name>Spring Stuff</name>
    <url>http://dellroad-stuff.googlecode.com/</url>

    <licenses>
        <license>
            <name>Apache 2</name>
            <url>http://www.apache.org/licenses/LICENSE-2.0.txt</url>
            <distribution>repo</distribution>
        </license>
    </licenses>

    <issueManagement>
        <system>Google Code</system>
        <url>http://code.google.com/p/dellroad-stuff/issues</url>
    </issueManagement>

    <scm>
        <connection>scm:svn:http://dellroad-stuff.googlecode.com/svn/trunk</connection>
        <developerConnection>scm:svn:https://dellroad-stuff.googlecode.com/svn/trunk</developerConnection>
        <url>http://dellroad-stuff.googlecode.com/svn/trunk</url>
    </scm>

    <dependencies>
        <dependency>
            <groupId>org.slf4j</groupId>
            <artifactId>slf4j-api</artifactId>
            <version>1.6.3</version>
        </dependency>
        <dependency>
            <groupId>javax.servlet</groupId>
            <artifactId>javax.servlet-api</artifactId>
            <version>3.0.1</version>
        </dependency>
        <dependency>
            <groupId>org.springframework</groupId>
            <artifactId>spring-context</artifactId>
            <version>3.0.6.RELEASE</version>
        </dependency>
        <dependency>
            <groupId>org.springframework</groupId>
            <artifactId>spring-aspects</artifactId>
            <version>3.0.6.RELEASE</version>
        </dependency>
        <dependency>
            <groupId>org.springframework</groupId>
            <artifactId>spring-web</artifactId>
            <version>3.0.6.RELEASE</version>
        </dependency>
    </dependencies>
</project>

That's not my POM file! I don't know where that POM file came from!

Someone else has stuck those dependencies in there.

The one I use and publish is clearly visible in maven central:

  http://search.maven.org/remotecontent?filepath=org/dellroad/dellroad-stuff/1.0.571/dellroad-stuff-1.0.571.pom

As you can see, there are no dependencies in that file.

My POM file intentionally does not contain any dependency information because I 
don't use maven and don't maintain any maven dependencies.

I would be interested to find out how those dependencies got in there... but it 
wasn't me!!

Wow! That's strange. I'll check that lib. 

My version of your lib comes form 
<repository>
   <id>vaadin-addons</id>
   <url>http://maven.vaadin.com/vaadin-addons</url>
</repository>

I took it from https://vaadin.com/directory#addon/spring-stuff site.

I downloaded your lib from maven.org repository and it does not have any 
dependencies as you told me. 

I will do some testes and provide feedback to you.

Changing library to that one you specified solved my problem. I can use:

<context:property-placeholder location="**/mysql.properties" />

on the other hand this not substitute tokes in Spring xml config files.  

Invalid bean definition with name 'dataSource' defined in URL 
[jar:file:/C:/Users/Zupa/.m2/repository/pl/inteca/otto/cp-datamodel/0.0.1-SNAPSH
OT/cp-datamodel-0.0.1-SNAPSHOT.jar!/datasourceContext.xml]: Could not resolve 
placeholder 'app.jdbc.driverClassName' in string value 
"${app.jdbc.driverClassName}"

But this could be caused by something else. I have multimodul project, Spring 
and Hibernate in one module compiled to cp-datamodel.jar
and cp-view.war where I have Vaadin app. From Vaadin app, using your lib I 
initialize Spring and Hibernate context defined in cp-datamodel.jar. Maybe 
thare is something wrong with that design (but when i don't use 
property-placeholder application works fine). If you have interest I could put 
part of my project online so you can look at it.


Anyway thanks for your help. I'll will change my rate of your lib on vaadin 
site right now ;-)

Argh, now I see... This is indeed my mistake!

There are two separate POM files that are used for the normal build vs. the 
Vaadin add-on, and the latter POM is the broken one.

I never even look at it so I completely forgot that it existed. I'll fix this 
POM file and update the add-on.

In the mean time use the normal JAR to avoid the problem.

Thanks and my apologies!

Fixed in r588. Thanks!

Hi Pan,

Version 1.0.594 of the Vaadin add-on is now available and should fix this 
problem.

If you try it out let me know whether it avoids the problem you were seeing 
before.

Thanks.

Thanks, it didn't helped, though. Tokens are still not substituted.

Sorry, I meant that this new version should fix the maven dependency problem 
with Spring 3.0.x.

Regarding the token substitution problem, I think the problem is your 
location="**/mysql.properties". I'm not sure that the "location" attribute 
accepts a pattern string like that.

Try specifying your files explicitly, separated by commas.

Doc:

  http://static.springsource.org/spring/docs/3.1.x/spring-framework-reference/html/beans.html#beans-factory-placeholderconfigurer