Officer
JBoss Group, LLC
On Thursday, July 10, 2003, at 07:27 PM, Jan Bartel wrote:
I have made the changes as agreed:
+ both war deployer and ejb deployer to examine ejb-link first for
both ejb-ref and ejb-local-ref.
+ war deployer to have a switch LenientEjbLink
/jboss/test/web/test/ WebIntegrationUnitTestCase.java
OK, I will integrate my test cases into these.
cheers,
Jan
Scott Stark
Chief Technology Officer
JBoss Group, LLC
On Thursday, July 10, 2003, at 07:27 PM, Jan Bartel wrote:
I have made
I have made the changes as agreed:
+ both war deployer and ejb deployer to examine ejb-link first for
both ejb-ref and ejb-local-ref.
+ war deployer to have a switch LenientEjbLink allowing
misconfigured ejb-links to be ignored for backward
compatibility. This is set to false by default,
and the ejb-link contains a name that cannot be resolved).
May I please have my cvs write access back so I can commit?
thanks
Jan
Scott M Stark wrote:
Ok, then I agree with adding the ejb-local-ref support.
--
/
* Jan Bartel [EMAIL PROTECTED]
* Associate
need to be able to specify the target's
local-jndi-name.
Yup, I agree.
Jan
/
* Jan Bartel [EMAIL PROTECTED]
* Associate
* Core Developers Network LLC
* http://www.coredevelopers.net
.
If these changes are acceptable, I am almost ready to commit them, but
it appears I no longer have CVS write access?? Can I get it back again
to commit these changes?
thanks
Jan
--
/
* Jan Bartel [EMAIL PROTECTED]
* Associate
* Core Developers Network LLC
Reply in-line.
Adrian Brock wrote:
On Mon, 2003-07-07 at 07:38, Jan Bartel wrote:
Hi
There appear to be a couple of anomalies in the handling of bean
references (ie ejb-ref and ejb-local-ref) elements of the web.xml and
ejb-jar.xml descriptors.
Firstly, the war deployer and the ejb deployer
Fred,
I am forwarding your bug report to the Jetty support list where it
will receive more attention.
regards,
Jan
Original Message
Subject: [JBoss-dev] Jetty addListener/removeListener exception
Date: Tue, 21 Jan 2003 12:12:33 -0500
From: Fred Hartman [EMAIL PROTECTED]
Haydar,
Please I need some support with Jboss-Jetty any of the new versions.
This email should really have gone to one of the JBoss user forums,
not this list as it is only for development issues with JBoss.
Slap on the wrist having been administered, lets see if we can help...
I tried to
Yes.
Jason Dillon wrote:
been integrated into 3.0?
--jason
___
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
Scott,
Where do you suggest that we store the credential of the principal to be
associated with the run-as role? In the jboss-web.xml file? I assume
it would be necessary for Jetty set up *both* the (new) principal and
its credential to enable the normal ejb authentication and authorization
I added two beans to test the run-as identity propagation and
deployed a sample ear to the j2ee1.3_01 reference implementation and
setup the CallerBean to invoke the CalleeBean with the ejb-jar.xml
descriptor shown below. The ri behavior differs in 2 ways from our
current
was thinking of it).
Any comments Greg/Scott/Jules?
Jan
Luke Taylor wrote:
Jan Bartel wrote:
The intention being to create a new principal, based on the old,
with a role added. The new principle is associated with the request
while it is within the run-as servlet. The popRole call ends
Forwarding this to the group.
Jan
Original Message
Subject: run-as servlet directive and JBoss
Date: Mon, 06 May 2002 20:06:41 +0100
From: Jan Bartel [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
CC: Greg Wilkins [EMAIL PROTECTED], Jules Gosnell [EMAIL PROTECTED]
Scott,
We've been
Comments are inline.
Our default optimization of ejb calls through the remote interface
is not working with the servlet 2.3 container class loading model
[...]
We can deal with this by either
1. ignore the servlet 2.3 class loading model, which is what
Jetty does by default
Sounds good,
User: janb
Date: 02/03/22 02:19:09
Modified:jetty/src/main/org/jboss/jetty Jetty.java
Log:
Set both Principal and Credential to null when finished handling a request.
Revision ChangesPath
1.44 +4 -3 contrib/jetty/src/main/org/jboss/jetty/Jetty.java
OK chaps, I'm going to have a shot at providing a solution to this.
I think what is happening is that Jetty is only setting the Principal
to null after it is finished handling a request, rather than both the
Principal *and* the Credential. Therefore, when no user has been
authenticated, both
User: janb
Date: 02/03/21 04:12:36
Modified:jetty/src/main/org/jboss/jetty/security JBossUserRealm.java
Log:
Fixed authentication problem: _password was member of JBossUserRealm instead
of JBossUserPrincipal, meaning everyone in the realm was using the same
password.
I have checked in a fix for this problem, but I am afraid I am unable to
test the fix at the moment. Could someone retest and let me know if the
fix is solid?
You will need to update
$JBOSSHOME/jetty/src/main/org/jboss/jetty/security/JBossSecurityRealm.java
Thanks
Jan
Hi,
I noticed a
Ignacio,
(I'm cross posting this to jboss-dev and jetty-discuss)
I think your current problem has in fact always been a problem with
your webapp, but it has just been unmasked by a modification to the
thread authentication stuff we did recently. What we did was to ensure
that when a
when it can be run packed,
but a
shag for
AbstractWebContainer to have to cache it's own local copies of every
njar
hooked
into it's classloader hierarchy.
Catch you tomorrow,
Jules
Jan Bartel wrote:
Actually, the njar protocol handler doesn't unpack the contents to
a
temp location
know about the njar problem - that was the next on the list.
I'm not sure whether a public accessor has been added to allow you to convert
njar-file (all the nested jars are unpacked into tmp and an index
maintained), but there were plans afoot.
Jules
Jan Bartel wrote:
Jules
Try:
Set name=KeystoreSystemProperty name=jboss.server.home.dir
//keystore/Set
jboss.server.home.dir points to $JBOSS-HOME/server/default and is
prepended onto the value of the Keystore property, ie the above would
be $JBOSS-HOME/server/default/keystore
Jan
Steven Jardine wrote:
I am
Jules Gosnell wrote:
Aha !
So I guess I have a couple of options :
1. hope that the njar folks will take pity on me, unpack the first
level and let
me dereference it
2. take my own local copy of any njars I need in Jasper's classpath.
Actually, you've got one more.
Jules,
I can see the javax.servlet.jar on the JSP classpath returned from
AbstractWebContainer.getClassLoaderURLs - what jboss
version are you using? Caveat: I haven't refreshed my tree in the
last 3 days or so, so maybe there has been a recent change ...
Jan
Jules Gosnell wrote:
I am
in the first place. Or have I misunderstood where
your question comes from ?
Jan
Jan Bartel wrote:
Jules,
I can see the javax.servlet.jar on the JSP classpath returned from
AbstractWebContainer.getClassLoaderURLs - what jboss
version are you using? Caveat: I haven't refreshed my tree
I guess the code was that
if( ... extractWars || !isDirectory(...)) {
Jar.extractblablabla
}
which should maybe better be extractWars !isDirectory(...)
Thanks much,
CGJ
-Ursprüngliche Nachricht-
Von: Jan Bartel [mailto:[EMAIL PROTECTED
User: janb
Date: 02/03/11 04:14:54
Added: jetty/src/main/org/mortbay/util Loader.java
Log:
New file.
Revision ChangesPath
1.1 contrib/jetty/src/main/org/mortbay/util/Loader.java
Index: Loader.java
User: janb
Date: 02/03/11 04:17:45
Added: jetty/src/main/org/mortbay/util StringBufferWriter.java
Log:
First checkin
Revision ChangesPath
1.1 contrib/jetty/src/main/org/mortbay/util/StringBufferWriter.java
Index: StringBufferWriter.java
User: janb
Date: 02/03/11 04:17:44
Added: jetty/src/main/org/mortbay/http/handler
ContentEncodingHandler.java
Log:
First checkin
Revision ChangesPath
1.1
Whoops,
Little fast on the commit trigger there ... should be all in CVS now.
Sorry for the inconvenience,
Jan
[EMAIL PROTECTED] wrote:
Bugs item #528449, was opened at 2002-03-11 11:32
You can respond by visiting:
The njar:file:jetty-plugin.sar^/org.mortbay.jetty.jar is going to be
a problem for the JSP classpath.
Either:
(1) jars inside sars need to be extracted by the JBoss deployer
(2) we forget sar format for Jetty and put all mortbay jars into
jboss.homelib
I assume that since JBoss is working
The njar:file:jetty-plugin.sar^/org.mortbay.jetty.jar is going to be
a problem for the JSP classpath.
Either:
(1) jars inside sars need to be extracted by the JBoss deployer
(2) we forget sar format for Jetty and put all mortbay jars into
jboss.homelib
I assume that since JBoss is working
Sorry if this is a re-post, having mail trouble ...
*However* there still seems to me to be a problem with JSPs in general:
ie, any JSP that has to be compiled that refers to a class (such as an
ejb) that is found by an njar:file:^/blah.jar URL won't be able
to be compiled?!
The
Actually, it is exactly the internally unpacked tmp files from njar that
is needed! What jasper wants on the class path are path references to
classes/jars rather than URL references to them.
How hard would it be to get the njar stuff to return the path to the
unpacked files?
Jan
David
Let's consider bang for buck, or effort for reward: how much effort is
it going to be for JBoss to provide a real path for items in an njar
format (ie really making their AbstractWebContainer
getCompileClasspath() method *really* return a compilable classpath
rather than a bunch of URLs) versus
Jules,
I figure that I can put together a very naive version fairly painlessly. Less
painfully, in fact, than having to continually explain the problem on various
lists/fora and provide a stream of half hearted attempts at a proper Jasper
integration. Furthermore, if it works, it gives
Christoph,
From a cursory inspection of the Axis code, it should work as it is (ie
by creating and populating a directory on the fly). The underlying Jetty
instance certainly supports deployment of directories, as well as
deployment of wars etc. So long as the AbstractWebContainer method
Christoph,
I've had a closer look at the Jetty code propmpted by your question, and
I've found a bug in the deployment which will throw an exception if
extractWars is true it is a directory that is being deployed.
Fix is coming.
Is your question motivated by having tried a deployment and
User: janb
Date: 02/03/03 17:38:55
Modified:jetty/src/main/org/mortbay MANIFEST.MF
Log:
Update Jetty version (mainly for fix to force creation of a mortbay context class
loader for all webapps).
Revision ChangesPath
1.4 +1 -1
User: janb
Date: 02/03/03 17:38:52
Modified:jetty/src/main/javax/servlet/http LocalStrings_es.properties
Log:
Update Jetty version (mainly for fix to force creation of a mortbay context class
loader for all webapps).
Revision ChangesPath
1.5 +0 -0
User: janb
Date: 02/03/03 17:38:58
Modified:jetty/src/main/org/mortbay/jetty/win32 Service.java
Log:
Update Jetty version (mainly for fix to force creation of a mortbay context class
loader for all webapps).
Revision ChangesPath
1.5 +0 -0
User: janb
Date: 02/03/03 17:38:52
Modified:jetty/src/main/org/apache/jasper CommandLineContext.java
EmbededServletOptions.java JasperException.java
JspC.java JspCompilationContext.java
JspEngineContext.java
User: janb
Date: 02/03/03 17:38:54
Modified:jetty/src/main/org/apache/jasper/resources
messages.properties messages_es.properties
messages_ja.properties
Log:
Update Jetty version (mainly for fix to force creation of a mortbay
User: janb
Date: 02/03/03 17:38:57
Modified:jetty/src/main/org/mortbay/http/jmx HttpContextMBean.java
HttpListenerMBean.java HttpServerMBean.java
NCSARequestLogMBean.java SocketListenerMBean.java
Log:
Update Jetty version (mainly
User: janb
Date: 02/03/03 17:38:57
Modified:jetty/src/main/org/mortbay/jetty/servlet
AbstractSessionManager.java Dispatcher.java
FilterHandler.java FilterHolder.java
HashSessionManager.java Holder.java
User: janb
Date: 02/03/03 17:38:55
Modified:jetty/src/main/org/mortbay/html Applet.java Block.java
Break.java Comment.java Composite.java
CompositeFactory.java DefList.java Element.java
Font.java Form.java
User: janb
Date: 02/03/03 17:38:56
Modified:jetty/src/main/org/mortbay/http ChunkableInputStream.java
ChunkableOutputStream.java ContextLoader.java
HashUserRealm.java HttpConnection.java
HttpContext.java
User: janb
Date: 02/03/03 17:39:00
Modified:jetty/src/main/org/mortbay/xml XmlConfiguration.java
XmlParser.java configure_1_0.dtd configure_1_1.dtd
configure_1_2.dtd
Log:
Update Jetty version (mainly for fix to force creation of a
User: janb
Date: 02/03/03 20:31:07
Modified:jetty/src/main/org/jboss/jetty
JBossWebApplicationContext.java
Log:
Ahem. Let's try that update again.
Revision ChangesPath
1.31 +2 -2
wrote:
I don't understand how this is the cause of the ClassCastException?
Can you explain that please.
--jason
Jan Bartel wrote:
Jason,
Okay, I'm not perplexed anymore! :-) Jetty expects to find at least
either a WEB-INF/classes directory, or a WEB-INF/lib (with at least one
Jason,
Can you please post some more details on your exact scenario, viz:
+ is this a hot redeploy of Jetty, especially is it a hot redeploy
when some webapps were already deployed?
+ have you modified your jetty jboss-service.xml file to include a
webapp (long shot, but I have to ask)?
David Jencks wrote:
I didn't try but I think you can stop and start the ejb's in an ejb module
with the org.jboss.ejb.EjbModule mbean I added a few days ago. When you
stop an ejb, the (ejb method call) invocations throw an exception, so it's
pretty well stopped. That was one of my
Scott/Marc,
When the Jetty context class loader delegates to it's parent class loader,
it expects the parent to throw a ClassNotFoundException if it can't load
the class, in which case
it then loads it itself. It appears that the quickest fix is for Jetty
to catch both exceptions from the
User: janb
Date: 02/02/26 19:14:49
Modified:jetty/src/main/org/jboss/jetty Jetty.java
Log:
Ensured security info attached with ThreadLocals is removed after a request has been
processed.
Revision ChangesPath
1.42 +32 -2
I think the problems you are experiencing are most probably as a result
of the recent changes to the JBoss MainDeployer etc (although without a
log trace it is difficult to be positive). I've tested redeployment with
Jetty without the latest MainDeployer changes and it is fine.
If you want to
User: janb
Date: 02/02/23 21:08:29
Modified:jetty/src/resources/jetty-plugin/META-INF jboss-service.xml
Log:
Added support for choice of Servlet2.3 or Java2 compliance for class loading
delegation.
Revision ChangesPath
1.21 +10 -3
User: janb
Date: 02/02/23 21:08:29
Modified:jetty/src/main/org/jboss/jetty
JBossWebApplicationContext.java Jetty.java
JettyService.java JettyServiceMBean.java
Log:
Added support for choice of Servlet2.3 or Java2 compliance for
User: janb
Date: 02/02/23 21:35:14
Modified:jetty/src/main/javax/servlet/http LocalStrings_es.properties
Log:
Updated to latest Jetty version: Jetty_4_0_B2
Revision ChangesPath
1.4 +0 -0
User: janb
Date: 02/02/23 21:35:15
Modified:jetty/src/main/org/apache/jasper CommandLineContext.java
EmbededServletOptions.java JasperException.java
JspC.java JspCompilationContext.java
JspEngineContext.java
User: janb
Date: 02/02/23 21:35:16
Modified:jetty/src/main/org/apache/jasper/parser ParserUtils.java
TreeNode.java
Log:
Updated to latest Jetty version: Jetty_4_0_B2
Revision ChangesPath
1.4 +0 -0
User: janb
Date: 02/02/23 21:35:16
Modified:jetty/src/main/org/apache/jasper/compiler
BeanEndGenerator.java BeanGenerator.java
BeanRepository.java CharDataGenerator.java
ClassDeclarationPhase.java
User: janb
Date: 02/02/23 21:35:16
Modified:jetty/src/main/org/apache/jasper/resources
messages.properties messages_es.properties
messages_ja.properties
Log:
Updated to latest Jetty version: Jetty_4_0_B2
Revision Changes
User: janb
Date: 02/02/23 21:35:16
Modified:jetty/src/main/org/apache/jasper/runtime JspException.java
JspFactoryImpl.java JspRuntimeLibrary.java
JspWriterImpl.java PageContextImpl.java
User: janb
Date: 02/02/23 21:35:16
Modified:jetty/src/main/org/apache/jasper/servlet ServletEngine.java
TomcatServletEngine.java
Log:
Updated to latest Jetty version: Jetty_4_0_B2
Revision ChangesPath
1.4 +0 -0
User: janb
Date: 02/02/23 21:35:17
Modified:jetty/src/main/org/apache/jasper/util SimplePool.java
StringManager.java
Log:
Updated to latest Jetty version: Jetty_4_0_B2
Revision ChangesPath
1.4 +0 -0
User: janb
Date: 02/02/23 21:35:17
Modified:jetty/src/main/org/mortbay/html Applet.java Block.java
Break.java Comment.java Composite.java
CompositeFactory.java DefList.java Element.java
Font.java Form.java
User: janb
Date: 02/02/23 21:35:18
Modified:jetty/src/main/org/mortbay/http ChunkableInputStream.java
ChunkableOutputStream.java ContextLoader.java
HashUserRealm.java HttpConnection.java
HttpContext.java
User: janb
Date: 02/02/23 21:35:18
Modified:jetty/src/main/org/mortbay/http/handler DumpHandler.java
NotFoundHandler.java NullHandler.java
ProxyHandler.java ResourceHandler.java
SecurityHandler.java
Log:
User: janb
Date: 02/02/23 21:35:19
Modified:jetty/src/main/org/mortbay/jetty Server.java
Log:
Updated to latest Jetty version: Jetty_4_0_B2
Revision ChangesPath
1.4 +0 -0 contrib/jetty/src/main/org/mortbay/jetty/Server.java
Index: Server.java
User: janb
Date: 02/02/23 21:35:19
Modified:jetty/src/main/org/mortbay/jetty/jmx Main.java
ServerMBean.java
Log:
Updated to latest Jetty version: Jetty_4_0_B2
Revision ChangesPath
1.4 +0 -0
User: janb
Date: 02/02/23 21:35:18
Modified:jetty/src/main/org/mortbay/http/jmx HttpContextMBean.java
HttpListenerMBean.java HttpServerMBean.java
NCSARequestLogMBean.java SocketListenerMBean.java
Log:
Updated to latest Jetty
User: janb
Date: 02/02/23 21:35:19
Modified:jetty/src/main/org/mortbay/jetty/servlet/jmx
ServletHttpContextMBean.java
WebApplicationMBean.java
Log:
Updated to latest Jetty version: Jetty_4_0_B2
Revision ChangesPath
1.3
User: janb
Date: 02/02/23 21:35:19
Modified:jetty/src/main/org/mortbay/jetty/servlet
AbstractSessionManager.java Dispatcher.java
FilterHandler.java FilterHolder.java
HashSessionManager.java Holder.java
User: janb
Date: 02/02/23 21:35:19
Modified:jetty/src/main/org/mortbay/jetty/win32 Service.java
Log:
Updated to latest Jetty version: Jetty_4_0_B2
Revision ChangesPath
1.4 +0 -0 contrib/jetty/src/main/org/mortbay/jetty/win32/Service.java
Index:
User: janb
Date: 02/02/23 21:35:20
Modified:jetty/src/main/org/mortbay/servlet AdminServlet.java
CGI.java Debug.java Dump.java Forward.java
MultiPartRequest.java MultiPartResponse.java
NotFoundServlet.java
User: janb
Date: 02/02/23 21:35:21
Modified:jetty/src/main/org/mortbay/util B64Code.java
BadResource.java BlockingQueue.java
ByteArrayISO8859Writer.java
ByteArrayOutputStream2.java
User: janb
Date: 02/02/23 21:35:21
Modified:jetty/src/main/org/mortbay/util/jmx CodeMBean.java
LifeCycleMBean.java LogMBean.java LogSinkMBean.java
Main.java ModelMBeanImpl.java
OutputStreamLogSinkMBean.java
User: janb
Date: 02/02/23 21:35:21
Modified:jetty/src/main/org/mortbay/xml XmlConfiguration.java
XmlParser.java configure_1_0.dtd configure_1_1.dtd
configure_1_2.dtd
Log:
Updated to latest Jetty version: Jetty_4_0_B2
Revision
Scott,
This is fine. All Jetty needs is a definite policy from JBoss - either
load all the classes/jars from the war, or don't load any of it - Jetty
is able to handle both situations.
If you don't crack open the wars, then we will probably go a step
further and add a switch to our service
User: janb
Date: 02/02/21 21:15:40
Modified:jetty/src/main/org/jboss/jetty/log JBossLogSink.java
Log:
Don't necessarily use just _log.debug() for Jetty debug: Jetty guards it's debug
output to it's log sinks, so it will only get here if Jetty has debugging enabled.
However,
User: janb
Date: 02/02/20 19:32:15
Modified:src/main/org/jboss/web AbstractWebContainer.java
Log:
When setting the web context for a war deployment, the context set in the
J2eeModuleMetaData must be used. Two lines matching the deployment with the metadata
got deleted,
User: janb
Date: 02/02/19 21:33:41
Modified:jetty/src/main/org/mortbay/html Applet.java Block.java
Break.java Comment.java Composite.java
CompositeFactory.java DefList.java Element.java
Font.java Form.java
User: janb
Date: 02/02/19 21:33:43
Modified:jetty/src/main/org/mortbay/http/jmx HttpContextMBean.java
HttpListenerMBean.java HttpServerMBean.java
NCSARequestLogMBean.java SocketListenerMBean.java
User: janb
Date: 02/02/19 21:33:44
Modified:jetty/src/main/org/mortbay/jetty/win32 Service.java
Log:
Updating to latest Jetty with tag JBOSS_20020220222111
Revision ChangesPath
1.3 +0 -0 contrib/jetty/src/main/org/mortbay/jetty/win32/Service.java
User: janb
Date: 02/02/19 21:33:43
Modified:jetty/src/main/org/mortbay/jetty Server.java
Log:
Updating to latest Jetty with tag JBOSS_20020220222111
Revision ChangesPath
1.3 +78 -53contrib/jetty/src/main/org/mortbay/jetty/Server.java
Index:
User: janb
Date: 02/02/19 21:33:43
Modified:jetty/src/main/org/mortbay/http/handler DumpHandler.java
HTAccessHandler.java NotFoundHandler.java
NullHandler.java ProxyHandler.java
ResourceHandler.java
User: janb
Date: 02/02/19 21:33:46
Modified:jetty/src/main/org/mortbay/xml XmlConfiguration.java
XmlParser.java configure_1_0.dtd configure_1_1.dtd
configure_1_2.dtd
Log:
Updating to latest Jetty with tag JBOSS_20020220222111
User: janb
Date: 02/02/19 21:33:45
Modified:jetty/src/main/org/mortbay/servlet AdminServlet.java
CGI.java Debug.java Dump.java Forward.java
MultiPartRequest.java MultiPartResponse.java
NotFoundServlet.java
User: janb
Date: 02/02/19 21:33:44
Modified:jetty/src/main/org/mortbay/jetty/servlet/jmx
ServletHttpContextMBean.java
WebApplicationMBean.java
Log:
Updating to latest Jetty with tag JBOSS_20020220222111
Revision Changes
User: janb
Date: 02/02/19 21:33:43
Modified:jetty/src/main/org/mortbay/jetty/jmx Main.java
ServerMBean.java mbean_en.properties
Log:
Updating to latest Jetty with tag JBOSS_20020220222111
Revision ChangesPath
1.3 +0 -0
User: janb
Date: 02/02/19 21:33:46
Modified:jetty/src/main/org/mortbay/util/jmx CodeMBean.java
LifeCycleMBean.java LogMBean.java LogSinkMBean.java
Main.java ModelMBeanImpl.java
OutputStreamLogSinkMBean.java
User: janb
Date: 02/02/19 21:33:46
Modified:jetty/src/main/org/mortbay/util B64Code.java
BadResource.java BlockingQueue.java
ByteArrayISO8859Writer.java
ByteArrayOutputStream2.java
User: janb
Date: 02/02/19 21:33:44
Modified:jetty/src/main/org/mortbay/jetty/servlet
AbstractSessionManager.java Dispatcher.java
FilterHandler.java FilterHolder.java
HashSessionManager.java Holder.java
User: janb
Date: 02/02/19 21:37:24
Modified:jetty/src/main/org/jboss/jetty
JBossWebApplicationContext.java Jetty.java
JettyService.java JettyServiceMBean.java
Log:
Removed necessity for jetty.xml for config.
Revision Changes
User: janb
Date: 02/02/19 21:53:51
Modified:jetty/src/etc README
Removed: jetty/src/etc demo.xml jetty.properties jetty.xml
webdefault.xml
Log:
Removed need for jetty.xml (all in jboss-service.xml) and webdefault.xml (ships
within the
User: janb
Date: 02/02/19 21:55:15
Modified:jettybuild.xml
Log:
Removed use of jetty.properties and jetty.xml
Revision ChangesPath
1.41 +9 -4 contrib/jetty/build.xml
Index: build.xml
User: janb
Date: 02/02/19 21:56:40
Modified:jetty/src/resources/jetty-plugin/META-INF jboss-service.xml
Log:
Added Jetty-specific XML to JettyService mbean configuration. Tidied up comments.
Revision ChangesPath
1.19 +109 -9
User: janb
Date: 02/02/19 22:27:04
Modified:jetty/src/main/org/apache/jasper/parser ParserUtils.java
TreeNode.java
Log:
Added new org.mortbay classes, updating apache.
Revision ChangesPath
1.3 +0 -0
User: janb
Date: 02/02/19 22:27:02
Modified:jetty/src/main/javax/servlet/http LocalStrings_es.properties
Log:
Added new org.mortbay classes, updating apache.
Revision ChangesPath
1.3 +0 -0
1 - 100 of 116 matches
Mail list logo
