> Hi Ashish,
>
> FYI : OOTB (but some config files for port mostly) I have not to
> comment these containers to debug/run in Eclipse.
>
> Jacques
> PS: this is also a test email as none as reached the ML recently
>
> From: "Ashish Vijaywargiya" <
[hidden email]>
>> Thanks Bob for your comment on this - Now I am able to run OFBiz inside
>> eclipse once again ;o).
>>
>> --
>> Ashish
>>
>> On Wed, Aug 26, 2009 at 3:15 AM, Bob Morley <
[hidden email]>
>> wrote:
>>
>>>
>>> I reverted back to trunk (except for my entityengine change and
>>> postgres
>>> jar)
>>> and I have a similar problem. It appears the .classpath issues have
>>> been
>>> resolved, but at start-up it attempts to start the vfs and webslinger
>>> containers. I hacked my ofbiz-components.xml to comment out these
>>> containers and away I went.
>>>
>>> This is an Eclipse only problem and I suspect if you compile and
>>> setup to
>>> run in eclipse (by running directly against the ofbiz.jar) it may work.
>>> What I do is use the default classpath and add the config directory
>>> to the
>>> classpath so I can run in Eclipse debug-mode and get some hot-swapping
>>> capabilities.
>>>
>>> Here are the two lines I comment out --
>>> <!--
>>> <container name="commons-vfs-container"
>>> class="org.ofbiz.commons.vfs.CommonsVfsContainer"/>
>>> <container name="webslinger-container"
>>> class="org.ofbiz.webslinger.WebslingerContainer"/>
>>> -->
>>>
>>> - Bob
>>>
>>>
>>> Jacques Le Roux-2 wrote:
>>> >
>>> > Has this problem been solved ? It seems to work for me.
>>> >
>>> > Jacques
>>> >
>>> > From: "Bob Morley" <
[hidden email]>
>>> >>
>>> >> Same problem for me; here is what I have determined ...
>>> >>
>>> >> - The root cause of the problem is that the classpath that
>>> Eclipse uses
>>> >> at
>>> >> runtime contains mutiple definitions of the same
>>> vfs-providers.xml file.
>>> >> The exception below indicates that multiple providers were
>>> registered
>>> for
>>> >> "ofbiz-home" for example.
>>> >>
>>> >> - If you remove vfs-providers.xml for your workspace and execute you
>>> will
>>> >> get a different variation of this exception (but this one related to
>>> >> "thick"
>>> >> or something like that). I exploded the webslinger-20090630- ...
>>> jar
>>> and
>>> >> it
>>> >> indeed had an vfs-providers.xml file that contained a definition for
>>> that
>>> >> scheme (in fact there were two). Not sure if it was this
>>> instance of
>>> the
>>> >> file or somewhere in my classpath the xml providers file has been
>>> >> included
>>> >> again.
>>> >>
>>> >> At this point I elected just to run without webslinger (since it
>>> is not
>>> >> something I am using right now). Since this is starting up
>>> containers,
>>> >> the
>>> >> easiest thing was for me to comment out the commons-vfs-container
>>> and
>>> >> webslinger-container. I do not understand the entire impact of
>>> this,
>>> but
>>> >> at
>>> >> least I could run ofbiz and start debugging through Eclipse again.
>>> >>
>>> >> Perhaps a webslinger expert could weigh in on a way to avoid this
>>> problem
>>> >> in
>>> >> Eclipse?
>>> >>
>>> >>
>>> >> Ashish Vijaywargiya-4 wrote:
>>> >>>
>>> >>> In past I was able to run OFBiz inside Eclipse.
>>> >>> I tried to start OFBiz from Start.java file with Debug as --> Java
>>> >>> Application option in Eclipse.
>>> >>> But now a days I am getting following error.
>>> >>>
>>> >>> Caused by: org.apache.commons.vfs.FileSystemException: Multiple
>>> >>> providers
>>> >>> registered for URL scheme "ofbiz-home".
>>> >>>
>>> >>
>>> >> --
>>> >> View this message in context:
>>> >>
>>>
http://www.nabble.com/Unable-to-run-OFBiz-from-Eclipse-due-to-loading-VFS-configuration.-tp24349920p24751393.html
>>>
>>> >> Sent from the OFBiz - User mailing list archive at Nabble.com.
>>> >>
>>> >
>>> >
>>> >
>>>
>>> --
>>> View this message in context:
>>>
http://www.nabble.com/Unable-to-run-OFBiz-from-Eclipse-due-to-loading-VFS-configuration.-tp24349920p25142707.html
>>>
>>> Sent from the OFBiz - User mailing list archive at Nabble.com.
>>>
>>>
>>