Nevermind. Turns out another conflict triggered the class loader issue. The sharedlib feature is working as advertised...it +is+ included in the tomcat deployment plan.ScottOn 8/15/06,
Scott Anderson [EMAIL PROTECTED] wrote:
I have encountered the same problem as Sunil did in my attempts
Given...config-A which has no parent configurationconfig-B and config-C which both have config-A as their parentweb-app which has config-C as its parent and imports config-Bconfig-B defines a GBean that is used by the web-app
When I do the following...redeploy config-B which also stops
On 10/5/05, Ivan S. Dubrov [EMAIL PROTECTED] wrote:
Hello,
My hack was a little cleaner. I was adding the jar containing my
custom login modules as a dependancy to first j2ee-server-plan.xml but
since the j2ee-security-plan.xml was established I have had to move
the dependancy for my
If I add my login module classes into the geronimo-security-1.0-M5.jar
(very dirty hack, of course :) ), it works. So I have some misunderstanding
with the class loading, I think.
My hack was a little cleaner. I was adding the jar containing my
custom login modules as a dependancy to first
I am trying to deploy a custom JAAS LoginModule that I had working
using the login-config xml-reference in my deployment plan before I
updated to a later geronimo codebase that included the addition of the
JaasLoginService reference. I decided to try to bypass the
xml-reference route after
How do I determine if the build is known to be broken?
I recently did a new source checkout, found it did not build, and
tried to go back to my old working build to then find that I
apparently overwrote my old open-ejb binary in my attempts to get the
latest build running. My old working
On Jul 11, 2005, at 2:13 PM, Jacek Laskowski wrote:
Scott Anderson wrote:
Where is it posted? I don't see it on the home page, downloads
page, or the wiki.
http://cvs.apache.org/dist/geronimo/unstable/1.0-M4-QA/. Would you
add a note on wiki?
Done.
It does appear my problem
Also I'm normally on irc all day so if you want realtime help just connect to #geronimo on the freenode.net.-dainOn Jun 6, 2005, at 10:59 PM, Scott Anderson wrote: You could look at this as an application service that would enable blogging and podcasting applications.Alternately, you could look
.
Scott
On Jun 6, 2005, at 9:26 PM, Dain Sundstrom wrote:
On Jun 5, 2005, at 5:25 PM, Scott Anderson wrote:
I would be interested in a standard RSS Syndication/Aggregation
Service getting included with a future Geronimo distribution. In
my mind this service would make it easy for developers
I would be interested in a standard RSS Syndication/Aggregation
Service getting included with a future Geronimo distribution. In my
mind this service would make it easy for developers and content
providers to...
1) serve up dynamically generated RSS feeds
2) subscribe to remote feeds with
David Jencks wrote:
isn't this because 80 is a privileged port and you have to be root to
use it?
Yep. Slipped my mind.
I am far from being a sysadmin but I thought the usual practice was
to set up your firewall to forward to port 8080.
I'd rather not put myself into the position of having to
Jeremy Boynes wrote:
[...]
It looks like the least intrusive route that
I could provide documentation for would be to get Geronimo working with
Apache using mod_jk.
That should work - you should just need to change the listener to use
AJP and then configure HTTPD as usual.
By
I did a...
maven m:clean
maven m:clean-repo
svn update
maven
...and...
BUILD FAILED
File..
/Users/scott/.maven/cache/maven-multiproject-plugin-1.3.1/plugin.jelly
Element... maven:reactor
Line.. 217
Column 9
Unable to obtain goal [default] --
, Scott Anderson wrote:
I did a...
maven m:clean
maven m:clean-repo
svn update
maven
...and...
BUILD FAILED
File..
/Users/scott/.maven/cache/maven-multiproject-plugin-1.3.1/plugin.jelly
Element... maven:reactor
Line.. 217
Column 9
Unable to obtain goal [default] --
/Users/scott
David Jencks wrote:
In my first attempt I noticed that Jetty was
ignoring
the context name I had specified in
META-INF/context.xml and used the name of the war
file
instead.
We ignore all jetty-specific deployment info.
It turns out that this is a Tomcat specific mechanism
for specifying
15 matches
Mail list logo
