Skip to main content

java.lang.NoSuchMethodError: org.jdesktop.swingx.util.PaintUtils.loadCompatibleImage(Ljava/io/InputStream;)Ljava/awt/image/BufferedImage;

21 replies [Last post]
Anonymous

Hello.

After many many months, yesterday I tried to upgrade my dependencies to
SwingLabs stuff. I previously used SwingX 0.9.4 and SwingX-WS
2008-12-07. Now I upgraded to SwingX 1.0 and SwingX-WS 2009-06-14 (since
the former was released at the beginning of June, it seemed a good
match). But I'm getting this exception:

[INFO] Failed to load a tile at url:
http://a1.ortho.tiles.virtualearth.net/tiles/a2101031.jpeg?g=1
[INFO] java.lang.NoSuchMethodError:
org.jdesktop.swingx.util.PaintUtils.loadCompatibleImage(Ljava/io/InputStream;)Ljava/awt/image/BufferedImage;
[INFO] at
org.jdesktop.swingx.mapviewer.AbstractTileFactory$TileRunner.run(AbstractTileFactory.java:308)
[INFO] at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
[INFO] at
java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
[INFO] at java.util.concurrent.FutureTask.run(FutureTask.java:138)
[INFO] at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[INFO] at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[INFO] at java.lang.Thread.run(Thread.java:637)

Any hint?

PS Can you confirm that there's no Maven repository for SwingX-WS? Any
plan to publish it?

--
Fabrizio Giudici - Java Architect, Project Manager
Tidalwave s.a.s. - "We make Java work. Everywhere."
weblogs.java.net/blog/fabriziogiudici - www.tidalwave.it/people
Fabrizio.Giudici@tidalwave.it

---------------------------------------------------------------------
To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
For additional commands, e-mail: jdnc-help@jdnc.dev.java.net

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
gr4pe
Offline
Joined: 2012-01-31
Points: 0

Looks like using SwingX 0.9.4 is still the only working solution...

Fabrizio Giudici

Joshua Marinacci wrote:
> My experience with maven is that it sucks to set up, but once it's
> working it works. Thus I have no interest in mavenizing the project
> myself, but once mavenized I'd be happy to use it. :)
>
I could volunteer for mavenizing SwingX-WS (after a deeper analysis of
the project structure). My point is political, I mean it's part of
SwingX and any decision to go that way should be a global decision of
the community.

--
Fabrizio Giudici - Java Architect, Project Manager
Tidalwave s.a.s. - "We make Java work. Everywhere."
weblogs.java.net/blog/fabriziogiudici - www.tidalwave.it/people
Fabrizio.Giudici@tidalwave.it

---------------------------------------------------------------------
To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
For additional commands, e-mail: jdnc-help@jdnc.dev.java.net

kschaefe
Offline
Joined: 2006-06-08
Points: 0

Jan was planning on Mavenizing SwingX once we moved to 1.6. I don't know the latest, but the preliminary pom files exist in the SwingX repo. He is using them in the Maven-backed Hudson build on swinglabs.org. I haven't looked at them, so I don't know what the exact state of Mavenization is.

Karl

Joshua Marinacci

My experience with maven is that it sucks to set up, but once it's
working it works. Thus I have no interest in mavenizing the project
myself, but once mavenized I'd be happy to use it. :)

-j
On Nov 5, 2009, at 10:05 AM, Fabrizio Giudici wrote:

> Joshua Marinacci wrote:
> > I'm going to guess that you
> updated the build scripts with NetBeans
>
> > and it requested some new version of JUnit. The immediate solution
> is
>
> > to revert. Are you sure the diff below is your entire change? -j On
>
> > Oct 28, 2009, at 10:48 PM, Fabrizio Giudici wrote:
>
>
> I hate to say that - but after a few days a new build was triggered
> on Hudson and was ok. I hate to see that a thing started working
> without and explicit fix, but that's life. BTW, yes, I realized I
> updated the build scripts. Which BTW seems to be a bit messy... what
> point is the discussion at about Mavenizing SwingX? :-)
>
> --
> Fabrizio Giudici - Java Architect, Project Manager
> Tidalwave s.a.s. - "We make Java work. Everywhere."
> weblogs.java.net/blog/fabriziogiudici - www.tidalwave.it/people
> Fabrizio.Giudici@tidalwave.it
>

[att1.html]

Fabrizio Giudici

Joshua Marinacci wrote:
> My experience with maven is that it sucks to set up, but once it's
> working it works. Thus I have no interest in mavenizing the project
> myself, but once mavenized I'd be happy to use it. :)
>
I could volunteer for mavenizing SwingX-WS (after a deeper analysis of
the project structure). My point is political, I mean it's part of
SwingX and any decision to go that way should be a global decision of
the community.

--
Fabrizio Giudici - Java Architect, Project Manager
Tidalwave s.a.s. - "We make Java work. Everywhere."
weblogs.java.net/blog/fabriziogiudici - www.tidalwave.it/people
Fabrizio.Giudici@tidalwave.it

---------------------------------------------------------------------
To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
For additional commands, e-mail: jdnc-help@jdnc.dev.java.net

Fabrizio Giudici

Joshua Marinacci wrote:
> I'm going to guess that you updated the build scripts with NetBeans
> and it requested some new version of JUnit. The immediate solution is
> to revert. Are you sure the diff below is your entire change? -j On
> Oct 28, 2009, at 10:48 PM, Fabrizio Giudici wrote:

I hate to say that - but after a few days a new build was triggered on
Hudson and was ok. I hate to see that a thing started working without
and explicit fix, but that's life. BTW, yes, I realized I updated the
build scripts. Which BTW seems to be a bit messy... what point is the
discussion at about Mavenizing SwingX? :-)

--
Fabrizio Giudici - Java Architect, Project Manager
Tidalwave s.a.s. - "We make Java work. Everywhere."
weblogs.java.net/blog/fabriziogiudici - www.tidalwave.it/people
Fabrizio.Giudici@tidalwave.it

[att1.html]

Joshua Marinacci

My experience with maven is that it sucks to set up, but once it's
working it works. Thus I have no interest in mavenizing the project
myself, but once mavenized I'd be happy to use it. :)

-j
On Nov 5, 2009, at 10:05 AM, Fabrizio Giudici wrote:

> Joshua Marinacci wrote:
> > I'm going to guess that you
> updated the build scripts with NetBeans
>
> > and it requested some new version of JUnit. The immediate solution
> is
>
> > to revert. Are you sure the diff below is your entire change? -j On
>
> > Oct 28, 2009, at 10:48 PM, Fabrizio Giudici wrote:
>
>
> I hate to say that - but after a few days a new build was triggered
> on Hudson and was ok. I hate to see that a thing started working
> without and explicit fix, but that's life. BTW, yes, I realized I
> updated the build scripts. Which BTW seems to be a bit messy... what
> point is the discussion at about Mavenizing SwingX? :-)
>
> --
> Fabrizio Giudici - Java Architect, Project Manager
> Tidalwave s.a.s. - "We make Java work. Everywhere."
> weblogs.java.net/blog/fabriziogiudici - www.tidalwave.it/people
> Fabrizio.Giudici@tidalwave.it
>

[att1.html]

Joshua Marinacci

I'm going to guess that you updated the build scripts with NetBeans
and it requested some new version of JUnit. The immediate solution is
to revert. Are you sure the diff below is your entire change?
-j
On Oct 28, 2009, at 10:48 PM, Fabrizio Giudici wrote:

> Joshua Marinacci wrote:
>> you are approved now.
>
> Updated the dependency to SwingX 1.0, applied the patch (that error
> was the only compilation problem) and committed. The fix resolves
> the issue with my application.
>
> Unfortunately, I see that the build broke in Hudson.
>
>
> BUILD FAILED
> /.hudson/jobs/SwingX-WS Continuous Build/workspace/trunk/swinglabs-
> build-impl.xml:153: Problem: failed to create task or type junit
> Cause: the class
> org.apache.tools.ant.taskdefs.optional.junit.JUnitTask was not found.
> This looks like one of Ant's optional components.
> Action: Check that the appropriate optional JAR exists in
> -/usr/lib
> -/root/.ant/lib
> -a directory added on the command line with the -lib argument
>
> Do not panic, this is a common problem.
> The commonest cause is a missing JAR.
>
> This is not a bug; it is a configuration problem
>
>
>
> I know what the error means, but I don't understand how my change
> triggered it. This is the diff for project.properties
>
> [Mistral:SwingLabs/SwingX-WS/swingx-ws] fritz% svn diff -r 304
> nbproject/project.properties
> Index: nbproject/project.properties
> ===================================================================
> --- nbproject/project.properties (revision 304)
> +++ nbproject/project.properties (working copy)
> @@ -5,6 +5,7 @@
> build.dir=build
> build.generated.dir=${build.dir}/generated
> build.classes.dir=${build.dir}/classes
> +build.generated.sources.dir=${build.dir}/generated-sources
> build.test.classes.dir=${build.dir}/test/classes
> build.test.results.dir=${build.dir}/test/results
> # This directory is removed when the project is cleaned:
> @@ -12,6 +13,8 @@
> dist.jar=${dist.dir}/swingx-ws.jar
> dist.javadoc.dir=${dist.dir}/javadoc
> +excludes=
> +includes=**
> ########################h##################################
> # Source and test directories #
> ##########################################################
> @@ -31,8 +34,8 @@
> file.reference.jtidy-r7.jar=lib/optional/jtidy-r7.jar
> file.reference.rome-0.8.jar=lib/optional/rome-0.8.jar
> file.reference.swing-worker.jar=lib/cobundle/swing-worker.jar
> -file.reference.swingx-bean.jar=lib/cobundle/swingx-bean.jar
> -file.reference.swingx.jar=lib/cobundle/swingx.jar
> +file.reference.swingx-beaninfo-1.0.jar=lib/cobundle/swingx-
> beaninfo-1.0.jar
> +file.reference.swingx-1.0.jar=lib/cobundle/swingx-1.0.jar
> file.reference.xercesImpl.jar=lib/optional/xercesImpl.jar
> ##########################################################
> @@ -46,8 +49,8 @@
> ${file.reference.rome-0.8.jar}:\
> ${file.reference.jdom.jar}:\
> ${file.reference.swing-worker.jar}:\
> - ${file.reference.swingx-bean.jar}:\
> - ${file.reference.swingx.jar}:\
> + ${file.reference.swingx-beaninfo-1.0.jar}:\
> + ${file.reference.swingx-1.0.jar}:\
> ${file.reference.commons-httpclient-3.0.1.jar}:\
> ${file.reference.commons-codec-1.3.jar}:\
> ${file.reference.commons-logging-1.1.jar}:\
>
>
> --
> Fabrizio Giudici - Java Architect, Project Manager
> Tidalwave s.a.s. - "We make Java work. Everywhere."
> weblogs.java.net/blog/fabriziogiudici - www.tidalwave.it/people
> Fabrizio.Giudici@tidalwave.it
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
> For additional commands, e-mail: jdnc-help@jdnc.dev.java.net
>

---------------------------------------------------------------------
To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
For additional commands, e-mail: jdnc-help@jdnc.dev.java.net

cganoe
Offline
Joined: 2009-09-05
Points: 0

Fabrizio Giudici wrote:
> Can this be summarized as swingx-ws not being managed
> at all? :-) I
> wonder how weekly builds are made if they shouldn't
> compile at all (I
> suppose they are compiled against old SwingX).

From what I'd seen, the swingx-ws weekly builds had been failing for some time. I assume you were able to get a swingx-ws build that works with swingx 1.0? If not, I built one months ago that I use.

> If it turns out that swingx is unmaintained, I wonder
> whether it doesn't
> make sense to drop some parts, such various Yahoo!
> service support, that
> presumably aren't been much used (I presumed they
> were needed at the
> beginning for the demos), and focus on components
> such the map viewer
> which AFAIK is getting some success (only yesterday
> yet another customer
> asked me about how to render maps on a Swing app).
> The JXMapViewer and
> related stuff could be spun off, put in the SwingX
> incubator and then
> eventually merged.

I'd be glad to work with you on spinning off the JXMapViewer stuff.

Joshua Marinacci

you are approved now.
On Oct 28, 2009, at 7:55 AM, Fabrizio Giudici wrote:

> jdnc-interest@javadesktop.org wrote:
>> to pour oil into the fire of confusion:
>>
>> - there had not been any changes to _swingx-ws_ in several years,
>> implication being that its version of swingx is several years old,
>> that is severely outdated (relative to SwingX)
>> - there had been api changes in _swingx_ between that outdated
>> version and SwingX1.0. As you noticed (and read in the issue
>> tracker of swingx-ws - you did, didn't you ) one of those api
>> changes broke code in swingx-ws
>> - there had been major api changes between SwingX1.0 and current
>> head (soon-to-be SwingX1.6), most but not all due to switching to
>> jdk6 as target
>> - locally updating the swingx version used by your local swingx-ws
>> requires to patch your local swingx-ws (or request dev role in
>> swingx-ws and do it there - users of swingx-ws will be delighted :-)
>>
> Can this be summarized as swingx-ws not being managed at all? :-) I
> wonder how weekly builds are made if they shouldn't compile at all
> (I suppose they are compiled against old SwingX).
>
> In any case, yes, please somebody give me commit rights (applied for
> them). I can't manage yet another FLOSS project, as I'm saturated,
> but it's ok for me to patch things that I discover aren't working.
>
> If it turns out that swingx is unmaintained, I wonder whether it
> doesn't make sense to drop some parts, such various Yahoo! service
> support, that presumably aren't been much used (I presumed they were
> needed at the beginning for the demos), and focus on components such
> the map viewer which AFAIK is getting some success (only yesterday
> yet another customer asked me about how to render maps on a Swing
> app). The JXMapViewer and related stuff could be spun off, put in
> the SwingX incubator and then eventually merged.
>
> --
> Fabrizio Giudici - Java Architect, Project Manager
> Tidalwave s.a.s. - "We make Java work. Everywhere."
> weblogs.java.net/blog/fabriziogiudici - www.tidalwave.it/people
> Fabrizio.Giudici@tidalwave.it
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
> For additional commands, e-mail: jdnc-help@jdnc.dev.java.net
>

---------------------------------------------------------------------
To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
For additional commands, e-mail: jdnc-help@jdnc.dev.java.net

Fabrizio Giudici

Joshua Marinacci wrote:
> you are approved now.

Updated the dependency to SwingX 1.0, applied the patch (that error was
the only compilation problem) and committed. The fix resolves the issue
with my application.

Unfortunately, I see that the build broke in Hudson.

BUILD FAILED
/.hudson/jobs/SwingX-WS Continuous
Build/workspace/trunk/swinglabs-build-impl.xml:153: Problem: failed to
create task or type junit
Cause: the class org.apache.tools.ant.taskdefs.optional.junit.JUnitTask
was not found.
This looks like one of Ant's optional components.
Action: Check that the appropriate optional JAR exists in
-/usr/lib
-/root/.ant/lib
-a directory added on the command line with the -lib argument

Do not panic, this is a common problem.
The commonest cause is a missing JAR.

This is not a bug; it is a configuration problem

I know what the error means, but I don't understand how my change
triggered it. This is the diff for project.properties

[Mistral:SwingLabs/SwingX-WS/swingx-ws] fritz% svn diff -r 304
nbproject/project.properties
Index: nbproject/project.properties
===================================================================
--- nbproject/project.properties (revision 304)
+++ nbproject/project.properties (working copy)
@@ -5,6 +5,7 @@
build.dir=build
build.generated.dir=${build.dir}/generated
build.classes.dir=${build.dir}/classes
+build.generated.sources.dir=${build.dir}/generated-sources
build.test.classes.dir=${build.dir}/test/classes
build.test.results.dir=${build.dir}/test/results
# This directory is removed when the project is cleaned:
@@ -12,6 +13,8 @@
dist.jar=${dist.dir}/swingx-ws.jar
dist.javadoc.dir=${dist.dir}/javadoc

+excludes=
+includes=**
########################h##################################
# Source and test directories #
##########################################################
@@ -31,8 +34,8 @@
file.reference.jtidy-r7.jar=lib/optional/jtidy-r7.jar
file.reference.rome-0.8.jar=lib/optional/rome-0.8.jar
file.reference.swing-worker.jar=lib/cobundle/swing-worker.jar
-file.reference.swingx-bean.jar=lib/cobundle/swingx-bean.jar
-file.reference.swingx.jar=lib/cobundle/swingx.jar
+file.reference.swingx-beaninfo-1.0.jar=lib/cobundle/swingx-beaninfo-1.0.jar
+file.reference.swingx-1.0.jar=lib/cobundle/swingx-1.0.jar
file.reference.xercesImpl.jar=lib/optional/xercesImpl.jar

##########################################################
@@ -46,8 +49,8 @@
${file.reference.rome-0.8.jar}:\
${file.reference.jdom.jar}:\
${file.reference.swing-worker.jar}:\
- ${file.reference.swingx-bean.jar}:\
- ${file.reference.swingx.jar}:\
+ ${file.reference.swingx-beaninfo-1.0.jar}:\
+ ${file.reference.swingx-1.0.jar}:\
${file.reference.commons-httpclient-3.0.1.jar}:\
${file.reference.commons-codec-1.3.jar}:\
${file.reference.commons-logging-1.1.jar}:\

--
Fabrizio Giudici - Java Architect, Project Manager
Tidalwave s.a.s. - "We make Java work. Everywhere."
weblogs.java.net/blog/fabriziogiudici - www.tidalwave.it/people
Fabrizio.Giudici@tidalwave.it

---------------------------------------------------------------------
To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
For additional commands, e-mail: jdnc-help@jdnc.dev.java.net

Joshua Marinacci

I'm going to guess that you updated the build scripts with NetBeans
and it requested some new version of JUnit. The immediate solution is
to revert. Are you sure the diff below is your entire change?
-j
On Oct 28, 2009, at 10:48 PM, Fabrizio Giudici wrote:

> Joshua Marinacci wrote:
>> you are approved now.
>
> Updated the dependency to SwingX 1.0, applied the patch (that error
> was the only compilation problem) and committed. The fix resolves
> the issue with my application.
>
> Unfortunately, I see that the build broke in Hudson.
>
>
> BUILD FAILED
> /.hudson/jobs/SwingX-WS Continuous Build/workspace/trunk/swinglabs-
> build-impl.xml:153: Problem: failed to create task or type junit
> Cause: the class
> org.apache.tools.ant.taskdefs.optional.junit.JUnitTask was not found.
> This looks like one of Ant's optional components.
> Action: Check that the appropriate optional JAR exists in
> -/usr/lib
> -/root/.ant/lib
> -a directory added on the command line with the -lib argument
>
> Do not panic, this is a common problem.
> The commonest cause is a missing JAR.
>
> This is not a bug; it is a configuration problem
>
>
>
> I know what the error means, but I don't understand how my change
> triggered it. This is the diff for project.properties
>
> [Mistral:SwingLabs/SwingX-WS/swingx-ws] fritz% svn diff -r 304
> nbproject/project.properties
> Index: nbproject/project.properties
> ===================================================================
> --- nbproject/project.properties (revision 304)
> +++ nbproject/project.properties (working copy)
> @@ -5,6 +5,7 @@
> build.dir=build
> build.generated.dir=${build.dir}/generated
> build.classes.dir=${build.dir}/classes
> +build.generated.sources.dir=${build.dir}/generated-sources
> build.test.classes.dir=${build.dir}/test/classes
> build.test.results.dir=${build.dir}/test/results
> # This directory is removed when the project is cleaned:
> @@ -12,6 +13,8 @@
> dist.jar=${dist.dir}/swingx-ws.jar
> dist.javadoc.dir=${dist.dir}/javadoc
> +excludes=
> +includes=**
> ########################h##################################
> # Source and test directories #
> ##########################################################
> @@ -31,8 +34,8 @@
> file.reference.jtidy-r7.jar=lib/optional/jtidy-r7.jar
> file.reference.rome-0.8.jar=lib/optional/rome-0.8.jar
> file.reference.swing-worker.jar=lib/cobundle/swing-worker.jar
> -file.reference.swingx-bean.jar=lib/cobundle/swingx-bean.jar
> -file.reference.swingx.jar=lib/cobundle/swingx.jar
> +file.reference.swingx-beaninfo-1.0.jar=lib/cobundle/swingx-
> beaninfo-1.0.jar
> +file.reference.swingx-1.0.jar=lib/cobundle/swingx-1.0.jar
> file.reference.xercesImpl.jar=lib/optional/xercesImpl.jar
> ##########################################################
> @@ -46,8 +49,8 @@
> ${file.reference.rome-0.8.jar}:\
> ${file.reference.jdom.jar}:\
> ${file.reference.swing-worker.jar}:\
> - ${file.reference.swingx-bean.jar}:\
> - ${file.reference.swingx.jar}:\
> + ${file.reference.swingx-beaninfo-1.0.jar}:\
> + ${file.reference.swingx-1.0.jar}:\
> ${file.reference.commons-httpclient-3.0.1.jar}:\
> ${file.reference.commons-codec-1.3.jar}:\
> ${file.reference.commons-logging-1.1.jar}:\
>
>
> --
> Fabrizio Giudici - Java Architect, Project Manager
> Tidalwave s.a.s. - "We make Java work. Everywhere."
> weblogs.java.net/blog/fabriziogiudici - www.tidalwave.it/people
> Fabrizio.Giudici@tidalwave.it
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
> For additional commands, e-mail: jdnc-help@jdnc.dev.java.net
>

---------------------------------------------------------------------
To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
For additional commands, e-mail: jdnc-help@jdnc.dev.java.net

Fabrizio Giudici

Joshua Marinacci wrote:
> I'm going to guess that you updated the build scripts with NetBeans
> and it requested some new version of JUnit. The immediate solution is
> to revert. Are you sure the diff below is your entire change? -j On
> Oct 28, 2009, at 10:48 PM, Fabrizio Giudici wrote:

I hate to say that - but after a few days a new build was triggered on
Hudson and was ok. I hate to see that a thing started working without
and explicit fix, but that's life. BTW, yes, I realized I updated the
build scripts. Which BTW seems to be a bit messy... what point is the
discussion at about Mavenizing SwingX? :-)

--
Fabrizio Giudici - Java Architect, Project Manager
Tidalwave s.a.s. - "We make Java work. Everywhere."
weblogs.java.net/blog/fabriziogiudici - www.tidalwave.it/people
Fabrizio.Giudici@tidalwave.it

[att1.html]

Fabrizio Giudici

jdnc-interest@javadesktop.org wrote:
> We had two classes that did basically the same thing with some of the same methods. I collapsed some of those methods, but did not get to complete that clean up. The "new" method is:
>
> org.jdesktop.swingx.graphics.GraphicsUtilities.loadCompatibleImage
>
Maybe it has already been fixed in newer builds of SwingX-WS? Remember,
I'm using one from June. Maybe I just need to use the latest? I suppose
after SwingX 1.0 there haven't been relevant changes in the public API.

--
Fabrizio Giudici - Java Architect, Project Manager
Tidalwave s.a.s. - "We make Java work. Everywhere."
weblogs.java.net/blog/fabriziogiudici - www.tidalwave.it/people
Fabrizio.Giudici@tidalwave.it

---------------------------------------------------------------------
To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
For additional commands, e-mail: jdnc-help@jdnc.dev.java.net

kleopatra
Offline
Joined: 2003-06-11
Points: 0

to pour oil into the fire of confusion:

- there had not been any changes to _swingx-ws_ in several years, implication being that its version of swingx is several years old, that is severely outdated (relative to SwingX)
- there had been api changes in _swingx_ between that outdated version and SwingX1.0. As you noticed (and read in the issue tracker of swingx-ws - you did, didn't you ) one of those api changes broke code in swingx-ws
- there had been major api changes between SwingX1.0 and current head (soon-to-be SwingX1.6), most but not all due to switching to jdk6 as target
- locally updating the swingx version used by your local swingx-ws requires to patch your local swingx-ws (or request dev role in swingx-ws and do it there - users of swingx-ws will be delighted :-)

HTH
Jeanette

Fabrizio Giudici

jdnc-interest@javadesktop.org wrote:
> to pour oil into the fire of confusion:
>
> - there had not been any changes to _swingx-ws_ in several years, implication being that its version of swingx is several years old, that is severely outdated (relative to SwingX)
> - there had been api changes in _swingx_ between that outdated version and SwingX1.0. As you noticed (and read in the issue tracker of swingx-ws - you did, didn't you ) one of those api changes broke code in swingx-ws
> - there had been major api changes between SwingX1.0 and current head (soon-to-be SwingX1.6), most but not all due to switching to jdk6 as target
> - locally updating the swingx version used by your local swingx-ws requires to patch your local swingx-ws (or request dev role in swingx-ws and do it there - users of swingx-ws will be delighted :-)
>
Can this be summarized as swingx-ws not being managed at all? :-) I
wonder how weekly builds are made if they shouldn't compile at all (I
suppose they are compiled against old SwingX).

In any case, yes, please somebody give me commit rights (applied for
them). I can't manage yet another FLOSS project, as I'm saturated, but
it's ok for me to patch things that I discover aren't working.

If it turns out that swingx is unmaintained, I wonder whether it doesn't
make sense to drop some parts, such various Yahoo! service support, that
presumably aren't been much used (I presumed they were needed at the
beginning for the demos), and focus on components such the map viewer
which AFAIK is getting some success (only yesterday yet another customer
asked me about how to render maps on a Swing app). The JXMapViewer and
related stuff could be spun off, put in the SwingX incubator and then
eventually merged.

--
Fabrizio Giudici - Java Architect, Project Manager
Tidalwave s.a.s. - "We make Java work. Everywhere."
weblogs.java.net/blog/fabriziogiudici - www.tidalwave.it/people
Fabrizio.Giudici@tidalwave.it

---------------------------------------------------------------------
To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
For additional commands, e-mail: jdnc-help@jdnc.dev.java.net

Fabrizio Giudici

Fabrizio Giudici wrote:

> If it turns out that swingx is unmaintained, I wonder whether it

I meant swingx-WS of course.

--
Fabrizio Giudici - Java Architect, Project Manager
Tidalwave s.a.s. - "We make Java work. Everywhere."
weblogs.java.net/blog/fabriziogiudici - www.tidalwave.it/people
Fabrizio.Giudici@tidalwave.it

[att1.html]

kschaefe
Offline
Joined: 2006-06-08
Points: 0

We had two classes that did basically the same thing with some of the same methods. I collapsed some of those methods, but did not get to complete that clean up. The "new" method is:

org.jdesktop.swingx.graphics.GraphicsUtilities.loadCompatibleImage

Karl

Fabrizio Giudici

jdnc-interest@javadesktop.org wrote:
> We had two classes that did basically the same thing with some of the same methods. I collapsed some of those methods, but did not get to complete that clean up. The "new" method is:
>
> org.jdesktop.swingx.graphics.GraphicsUtilities.loadCompatibleImage
>
Maybe it has already been fixed in newer builds of SwingX-WS? Remember,
I'm using one from June. Maybe I just need to use the latest? I suppose
after SwingX 1.0 there haven't been relevant changes in the public API.

--
Fabrizio Giudici - Java Architect, Project Manager
Tidalwave s.a.s. - "We make Java work. Everywhere."
weblogs.java.net/blog/fabriziogiudici - www.tidalwave.it/people
Fabrizio.Giudici@tidalwave.it

---------------------------------------------------------------------
To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
For additional commands, e-mail: jdnc-help@jdnc.dev.java.net

kleopatra
Offline
Joined: 2003-06-11
Points: 0

Fabrizio,

that's a known issue: the method moved, don't recall where exactly - details are in the issuetracker (the only incompatibility so far noted). Ehem ... it's on my list to update to SwingX1.0, but nothing more. Hmm ... if you'd request a developer role I would grant it and you could do it yourself (trying to delegate, as always )

Cheers
Jeanette

kleopatra
Offline
Joined: 2003-06-11
Points: 0

> Fabrizio,
>
> ... if you'd request a developer role I would grant
> it and you could do it yourself (trying to delegate,
> as always )
>

wrong - just noticed that I'm not owner of swingx-ws so can't grant anything. Nevertheless, I'm sure you'll get it from the owners :-)

CU
Jeanette