#: Kola Oyedeji changed the world a bit at a time by saying on 10/11/2005 5:18
PM :#
Alex
Hi, I've installed the same setup @work - this time I installed Jboss
on a drive without a space in a directory path. I'm not sure if this
should be added somewhere as a known issue?
On windows boxes it could be common for directory paths with spaces -
not sure if this is considered a bug?
Well I'm up and running, thanks.
Kola
I have tried this evening JBOSS 4.0.3 with both scenarios, and it worked correctly. Looks like it is
a bug in 4.0.2 where FileURLConnection uses an encoded path (so it looks for something%20else
instead of something else).
hth,
./alex
--
.w( the_mindstorm )p.
On 10/11/05, Alexandru Popescu <[email protected]> wrote:
#: Kola Oyedeji changed the world a bit at a time by saying on 10/11/2005 1:03
PM :#
> Thanks for the reply,
>
> No, I unzipped it and then deployed it.
>
Thanks for the info. Later today I will try to investigate this issue.
I will get back to you when I will have something (hopefully).
./alex
--
.w( the_mindstorm )p.
> On 10/11/05, Alexandru Popescu <[email protected]> wrote:
>> #: Kola Oyedeji changed the world a bit at a time by saying on 10/11/2005
1:10 AM :#
>> > Well this is great timing for me François-Léonard, as I am having
>> > exactly the same problem. Almost exactly the same setup - infact my
>> > directory path on windows is even the same - this is what is in my
>> > log:
>> >
>> > ERROR info.magnolia.cms.beans.config.ContentRepository 10.10.2005
>> > 22:52:14 --
C:\Program%20Files\jboss-4.0.2\server\default\.\deploy\magnoliaAuthor.war\WEB-INF\config\repositories.xml
>> > java.io.FileNotFoundException:
>> >
C:\Program%20Files\jboss-4.0.2\server\default\.\deploy\magnoliaAuthor.war\WEB-INF\config\repositories.xml
>> > at
org.jboss.net.protocol.file.FileURLConnection.connect(FileURLConnection.java:80)
>> > at
org.jboss.net.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:89)
>> > at
org.apache.xerces.impl.XMLEntityManager.setupCurrentEntity(Unknown Source)
>> > at
org.apache.xerces.impl.XMLVersionDetector.determineDocVersion(Unknown
>> > Source)
>> >
>> > I have noted that the path above
>> >
>> >
C:\Program%20Files\jboss-4.0.2\server\default\deploy\magnoliaAuthor.war\WEB-INF\config\repositories.xml
>> >
>> > Does not work but...
>> >
>> > C:\Program
Files\jboss-4.0.2\server\default\deploy\magnoliaAuthor.war\WEB-INF\config\repositories.xml
>> >
>> > Does, so as suggested it appears it is a problem with the spaces in
>> > the path. Before I unistall JBoss and re-install is there any other
>> > workaround perhaps?
>> >
>> > Thanks
>> >
>> >
>>
>> Hi!
>>
>> I was wondering if the magnolia.war in the aboves paths is still a war, or
if it was already
>> exploded in a subdirectory?
>>
>> ./alex
>> --
>> .w( the_mindstorm )p.
>>
>> >
>> > On 10/6/05, François-Léonard Gilbert <[email protected]> wrote:
>> >> I changed the memory pool settings and tried to bootstrap Magnolia 2.1
>> >> again. This time, I changed the memory settings to "-Xms512m
>> >> -Xmx764m".
>> >>
>> >> JBoss went up without a hitch in 25 seconds, but the /magnoliaAuthor
>> >> URI still gives the dreaded 403 error.
>> >>
>> >> Here are the relevent log messages from the JBoss log:
>> >> -----
>> >> 2005-10-06 10:44:49,668 INFO [STDOUT] Initializing Log4J
>> >> 2005-10-06 10:44:49,678 INFO [STDOUT] Setting the magnolia root
>> >> system property: [magnolia.author.root] to [C:\Program
>> >> Files\jboss-4.0.2\server\default\.\deploy\magnoliaAuthor.war\]
>> >> 2005-10-06 10:44:49,678 INFO [STDOUT] Initializing Log4J from
>> >> [WEB-INF/config/log4j.xml]
>> >> 2005-10-06 10:44:49,758 INFO [STDOUT] INFO
>> >> info.magnolia.cms.beans.config.ConfigLoader
>> >> ConfigLoader.java(<init>:66) 06.10.2005 10:44:49 Assuming paths
>> >> relative to C:\Program
>> >> Files\jboss-4.0.2\server\default\.\deploy\magnoliaAuthor.war
>> >> 2005-10-06 10:44:49,848 INFO [STDOUT]
>> >> ---------------------------------------------
>> >> 2005-10-06 10:44:49,848 INFO [STDOUT] MAGNOLIA LICENSE
>> >> 2005-10-06 10:44:49,848 INFO [STDOUT]
>> >> ---------------------------------------------
>> >> 2005-10-06 10:44:49,858 INFO [STDOUT] Version number : 2.1
>> >> 2005-10-06 10:44:49,858 INFO [STDOUT] Build : 1454 September 5.
2005
>> >> 2005-10-06 10:44:49,858 INFO [STDOUT] Provider : obinary ltd
>> >> ([EMAIL PROTECTED])
>> >> 2005-10-06 10:44:49,858 INFO [STDOUT] INFO
>> >> info.magnolia.cms.beans.config.ConfigLoader
>> >> ConfigLoader.java(load:102) 06.10.2005 10:44:49 Init content
>> >> repositories
>> >> 2005-10-06 10:44:49,868 INFO [STDOUT] INFO
>> >> info.magnolia.cms.beans.config.ContentRepository
>> >> ContentRepository.java(init:171) 06.10.2005 10:44:49 System : loading
>> >> JCR
>> >> 2005-10-06 10:44:49,878 INFO [STDOUT] ERROR
>> >> info.magnolia.cms.beans.config.ContentRepository
>> >> ContentRepository.java(init:179) 06.10.2005 10:44:49
>> >>
C:\Program%20Files\jboss-4.0.2\server\default\.\deploy\magnoliaAuthor.war\WEB-INF\config\repositories.xml
>> >> java.io.FileNotFoundException:
>> >>
C:\Program%20Files\jboss-4.0.2\server\default\.\deploy\magnoliaAuthor.war\WEB-INF\config\repositories.xml
>> >> -------
>> >>
>> >> I think this problem can be resolved in one of 2 ways:
>> >> 1) JBoss needs config work to report the right root directory (without
the /./)
>> >> 2) Magnolia has to do a sanity check on the application root, then
correct it.
>> >>
>> >> Well, that's the time I had today for this. Hope you can make
>> >> something out of this!
>> >>
>> >> François-Léonard Gilbert
>> >>
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
