We don't manage your jars, we just give you an initial start.
Updating the jars and apropriate config files you have is the way to update to
a new version of any framework (not just Seam ;)
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4183148#4183148
Reply
This isn't about 'Managing my Jars', it's all about managing jars referenced by
plugins and referenced runtimes.
Again:
The project was pointing to the jboss-seam.jar of the original seam runtime
after it was generated using the tools. Is was not possible to fix it without
actually removing the
The config file from eclipse was the workbench.xml.
I have an ear, ejb and my war projects which were generated using the eclipse
seam project tool. the ejb and war have their dynamically generated web app
libraries classpath entries. these pointed to the jboss-seam.jar in the seam
runtime fold
which workbench.xml are you editing ? What is the full path to it ?
There should be *zero* reason to adjust this file.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4183169#4183169
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode
I found entries like this:
and
As I said, I was getting desperate and looking for any 'possible'
cause/solution. I don't even know if this made a difference.
I do not make a habit of editing such files; but as I have previously said, I
could not get the reference to jboss-seam.jar file t
Those two entries is just the cache/memory for the workbench of you opening
SeamFilter.class and ExceptionFilter.class in the editor area so it would open
these when you restart eclipse.
These have nothing to do with your projects understanding on whic libs it is
using.
View the original post
do you have any idea then as to where this 'ghost' reference was stored?
I searched through all project files(incl hidden and system) to find any
containing the incorrect path and found none either in my workspace or the
eclipse application folders. Does the seam plugin store information anywher
no jboss wasn't running.
I actually did the runtime firts thing before anything else this morning.
I really searched everywhere I could think of to see where it came from.
It wasn't added as library, user library or any other manual means of attaching
jars to the project. It was refernced dyna
what exactly did you find in that workbench.xml ?
Nothing of this should be related to you updating the jars?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4183191#4183191
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p
I was stuck for solutions so i did a file search for all files in my workspace
that contained the path entry I wanted to get rid of and found it in the
workbench.xml situated in [path to
workspace]\'.metadata\.plugins\org.eclipse.ui.workbench'. I changed the entries
to the new path and that was
As I understand it, workbench.xml only is in charge of recording which files,
views, editors, etc are open upon startup, or which ones were opened upon
close.
Basically, the workbench.xml is just saying "the file opened is x, and it is
found in jar y".
If you open your workspace, close *all
hmmmwe try to avoid create projects that points "deeply" into the
plugins/runtimes - exactly to avoid this issue.
If we do that that is a bug.
Which classpath container points to a jboss-seam.jar not inside your project ?
Which config files are you talking about ?
View the original post :
could it be that something was holding on to the old jars ? i.e. a running
jboss's classloader ?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4183242#4183242
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4183242
_
13 matches
Mail list logo
