what is tagPlugins.xml for? (was Re: [newbie] making jstl to work when jetty is run programatically)

jetty and axis

Hello, I am newbie in this. I implemented a web service with tomcat and axis 
for my  end degree project. I have to replace tomcat with jetty. Anyone 
knowns a tutorial  or examples for invoke axis with jetty?

Thanks

-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Jetty-support mailing list
Jetty-support <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jetty-support

Re: Chinese characters in the URL

Re: Initializing servlets with references to existing objects

Benjamin,

the problem is that the context attributes are a merge of the ones set each
start cycle from web.xml and by the app itself   PLUS any configured attributes
set before the webapp is started.

You are using  getServletContext().setAttribute  before the webapp is started
and hence you get the NPE (OK crappy error!)

You can just set your attributes directly on the webApplicationContext
and they will be available as context attributes to your webapp.

Benjamin Podszun wrote:
> Hi there.
> 
> In my project I have a default/delegator servlet that needs access to  a
> (reference to an) object. I currently start the server like this:
> 
> WebApplicationContext webAppContext;
> _jetty = new Server();
> 
> // logging config here..
> 
> webAppContext = new WebApplicationContext();
> webAppContext = _jetty.addWebApplication("/", config.getServerRoot
> ().getAbsolutePath());
> WebApplicationHandler handler = new WebApplicationHandler();
> ServletHolder delegator = handler.addServlet("/*", 
> DelegatorServlet.class.getName());
> 
> // Does't work
> // delegator.getServletContext().setAttribute("MyObject", someObject);
> 
> FilterHolder filterHolder = handler.defineFilter("DBFilter", 
> DBFilter.class.getName());
> handler.addFilterHolder(filterHolder);
> webAppContext.addHandler(handler);
> _jetty.start();
> 
> I added the commented part of my last try: I thought I maybe could  add
> my reference to the ServletContext, but that ends up with a NPE 
> although the object is not null when I setAttribute() it..
> 
> Any hints how to do that? I don't want the servlet to access the rest 
> of the application via static methods.
> 
> Thanks in advance,
> Ben
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log
> files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
> _______________________________________________
> Jetty-support mailing list
> Jetty-support <at> lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/jetty-support
> 

-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Jetty-support mailing list
Jetty-support <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jetty-support

Re: with DEBUG/TRACE on, (ignorable) socket timeout exceptions in 5.1.5?

Eric,

I hate!

  try
  {
     ...
  }
  catch(Exception e)
  {}

So jetty always does at least a 

  try
  {
     ...
  }
  catch(Exception e)
  {
     LogSupport.ignore(e);
  }

So you can see ALL exceptions if you need to.

-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Jetty-support mailing list
Jetty-support <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jetty-support

Re: Error 404 after moving from 4.2.23 to 5.1.6 using xml configuration

Bill,

nothing shouts out in that xml as wrong.

Can you drop your webapp into $JETTY_HOME/webapps and try the standard jetty.xml
with the release.   This will confirm that your webapp is OK with Jetty 5.

we can then look in more detail at what the problem is (or just cut back the
new jetty.xml to what you need).

cheers

Bill Ferrett wrote:
> I am using the following xml configuration file under 4.2.23 and I can
> access my servlet using
> http://myserver:8080/mycontext/servlet/myservlet
> 
> however after installing 5.1.6 this no longer works.  I can access html
> files, e.g.
> http://myserver:8080/mycontext/index.html
> but any servlet requests result in an error 404.
> My servlet is loaded on startup perfectly - I can tell from the log - I
> just can't access it.  I assume I need to modify my xml file for 5.x.y
> but I can't find any info on what needs to be changed
> 
> <!-- =============================================================== -->
> <!-- Configure the Jetty Server                                      -->
> <!-- =============================================================== -->
> <Configure class="org.mortbay.jetty.Server">
> 
>   <!-- =============================================================== -->
>   <!-- Configure the Request Listeners                                 -->
>   <!-- =============================================================== -->
> 
>   <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
>   <!-- Add and configure a HTTP listener to port 8080      -->
>   <!-- The default port can be changed using: java -Djetty.port=80     -->
>   <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
>   <Call name="addListener">
>     <Arg>
>       <New class="org.mortbay.http.SocketListener">
>         <Set name="Port"><SystemProperty name="jetty.port"
> default="8080"/></Set>
>         <Set name="MinThreads">5</Set>
>         <Set name="MaxThreads">50</Set>
>         <Set name="MaxIdleTimeMs">30000</Set>
>         <Set name="LowResourcePersistTimeMs">1000</Set>
>         <Set name="ConfidentialPort">8443</Set>
>         <Set name="IntegralPort">8443</Set>
>         <Set name="PoolName">http</Set>
>         <Set name="LingerTimeSecs">-1</Set>
>       </New>
>     </Arg>
>   </Call>
> 
> 
>   <!-- =============================================================== -->
>   <!-- Configure the Contexts                                          -->
>   <!-- =============================================================== -->
>   <Call name="addWebApplication">
>     <Arg>/mycontext/*</Arg>
>     <Arg>c:\apps\mycontext</Arg>
>     <Set name="extractWAR">false</Set>
>   </Call>
> 
>   <!-- =============================================================== -->
>   <!-- Configure the Request Log                                       -->
>   <!-- =============================================================== -->
>   <Set name="RequestLog">
>     <New class="org.mortbay.http.NCSARequestLog">
>       <Arg><SystemProperty name="jetty.home"
> default="."/>/logs/yyyy_mm_dd.request.log</Arg>
>       <Set name="retainDays">90</Set>
>       <Set name="append">true</Set>
>       <Set name="extended">false</Set>
>       <Set name="buffered">false</Set>
>       <Set name="LogTimeZone">GMT</Set>
>     </New>
>   </Set>
> 
>   <!-- =============================================================== -->
>   <!-- Configure the Other Server Options                              -->
>   <!-- =============================================================== -->
>   <Set name="requestsPerGC">2000</Set>
>   <Set name="statsOn">false</Set>
> 
> </Configure>
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log
> files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
> _______________________________________________
> Jetty-support mailing list
> Jetty-support <at> lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/jetty-support
> 

-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Jetty-support mailing list
Jetty-support <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jetty-support

Static vs. Dynamic content stream differences.

I have a servlet which reads static content sitting on disk and pumps it 
out in the response stream.  This servlet reads a jar file (a J2ME 
application) from disk and returns it's bytes as a 
application/java-archive.  The same jar file can be accessed directly 
rather than going through the servlet.  Here are the two URLs to access 
this jar file:

(1) http://karasulu.homeip.net/activation/test/
(2) http://karasulu.homeip.net/activation/HausKeys.jar

I made sure the response headers and content type of the servlet (1) 
matches that of the server's response to the direct static file access 
in (2).  Now here's the interesting problem:

The two resultant streams are different somehow and I cannot figure out 
how.  I know they are different because my Sony Ericsson T610 can load 
(2) just fine.  However when it tries to load from (1) the request makes 
it to the servlet and initiates the return of the response but the 
response causes the phone to give me the following error:

"Your client is not allowed to access the requested object"

I would like both these URLs to have the same effect hence be exactly 
the same through the eyes of this phone's WAP browser.  Something in the 
responses is different.  Even though the response headers are all the 
same I cannot get these two URLs to behave the same way.  Here are the 
headers for both (obviously with different dates):

statusCode: 200
statusLine: HTTP/1.1 200 OK
statusText: OK
responseCharSet: ISO-8859-1
responseFooters:
responseHeaders:
    Date: Fri, 02 Dec 2005 19:13:24 GMT
    Server: Jetty/5.1.5 (Linux/2.6.14-1.1637_FC4 i386 java/1.5.0_05
    Content-Type: application/java-archive
    Content-Length: 33603
    Accept-Ranges: bytes
    Last-Modified: Fri, 02 Dec 2005 19:13:24 GMT

Ahh and from the Server header you can see that I'm using Jetty 5.1.5 on 
SUN JDK 1.5.0_05.  Any clue as to what is different in these responses?  
I'm totally perplexed.

Thanks much,
Alex

-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Jetty-support mailing list
Jetty-support <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jetty-support

Is a webapplication guaranteed to have the same ClassLoader for different Servlets?

Hi there,

I am currently implementing a servlet-interface and I want to hold
some server-wide valid data in SingleTons.
However several different servlets in the same webblication (outch,
buzzword) and all those servlets want to share data via the
singletons.

This works but I have fears that its maybe a bit dirty and not
guaranteed to work.
So is a weblication (one directory containing a Web-INF and the
several servlet-classes) guaranteed to be loaded by the same
classloader (and therefor share the same static fields?).

Thanks you in advance, lg Clemens

-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
_______________________________________________
Jetty-support mailing list
Jetty-support <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jetty-support

Tracing requests in normal operation ?

Hi,

I want to trace requests - including the content - during normal
operation. E.g. there is a web application running which receives
requests which I want to intercept and log/dump/whatever without the
web application taking notice.
How would I achieve that ? Right now if I define my own HttpHandler
and therein access the content, it gets consumed. But there does not
seem to be an easy way to manipulate the input stream in the request ?

regards,
Tom

-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
_______________________________________________
Jetty-support mailing list
Jetty-support <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jetty-support

Re: Re: Initializing servlets with references to existing objects

Hi Greg.
First of all: Thanks for your answer.

On 02.12.2005, at 23:03, Greg Wilkins wrote:
> the problem is that the context attributes are a merge of the ones  
> set each
> start cycle from web.xml and by the app itself   PLUS any  
> configured attributes
> set before the webapp is started.

Sounds exactly like I want it to be.

> You are using  getServletContext().setAttribute  before the webapp  
> is started
> and hence you get the NPE (OK crappy error!)

Makes sense - I understand that the ServletContext doesn't exist  
before I actually start the server.

> You can just set your attributes directly on the webApplicationContext
> and they will be available as context attributes to your webapp.

I'm not sure if I understood this one. I tried

WebApplicationHandler handler = new WebApplicationHandler();
handler.addServlet("/*", DelegatorServlet.class.getName());
handler.setContextAttribute("foo", "bar");

which unfortunately results in exactly the same problem/error. Unless  
I comment this entry I get

Dec 5, 2005 2:17:48 AM myclass start
SEVERE: null
java.lang.NullPointerException
         at  
org.mortbay.jetty.servlet.ServletHandler.getContextAttribute 
(ServletHandler.java:934)
         at  
org.mortbay.jetty.servlet.WebApplicationHandler.setContextAttribute 
(WebApplicationHandler.java:585)
         at myclass.start(Unknown Source)
         at myclass.main(Unknown Source)

I tried as well

WebApplicationHandler handler = new WebApplicationHandler();
ServletHolder delegator = handler.addServlet("/*",  
DelegatorServlet.class.getName());
delegator.setInitParameter("foo", "bar");

which works fine - but only for String(s) and not for Objects/ 
references..

Did I missunderstand what you suggested? Or am I doing something  
stupid anyway? I just want to put some properties (Objects)  
programmatically into the servlet context before it is initialized..

Thanks in advance,
Ben

>
> Benjamin Podszun wrote:
>> Hi there.
>>
>> In my project I have a default/delegator servlet that needs access  
>> to  a
>> (reference to an) object. I currently start the server like this:
>>
>> WebApplicationContext webAppContext;
>> _jetty = new Server();
>>
>> // logging config here..
>>
>> webAppContext = new WebApplicationContext();
>> webAppContext = _jetty.addWebApplication("/", config.getServerRoot
>> ().getAbsolutePath());
>> WebApplicationHandler handler = new WebApplicationHandler();
>> ServletHolder delegator = handler.addServlet("/*",
>> DelegatorServlet.class.getName());
>>
>> // Does't work
>> // delegator.getServletContext().setAttribute("MyObject",  
>> someObject);
>>
>> FilterHolder filterHolder = handler.defineFilter("DBFilter",
>> DBFilter.class.getName());
>> handler.addFilterHolder(filterHolder);
>> webAppContext.addHandler(handler);
>> _jetty.start();
>>
>> I added the commented part of my last try: I thought I maybe  
>> could  add
>> my reference to the ServletContext, but that ends up with a NPE
>> although the object is not null when I setAttribute() it..
>>
>> Any hints how to do that? I don't want the servlet to access the rest
>> of the application via static methods.
>>
>> Thanks in advance,
>> Ben

-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Jetty-support mailing list
Jetty-support <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jetty-support