Ra Carter

I'm using the latest versions of Jersey and Guice but I'm see runtime errors when trying to return a collection or map. I thought Jackson could do that automatically?

Here's the exact error:

A message body writer for Java class java.util.ArrayList, and Java type java.util.Collection<java.lang.String>, and MIME media type application/json was not found.
The registered message body writers compatible with the MIME media type are:
application/json ->
com.sun.jersey.json.impl.provider.entity.JSONJAXBElementProvider$App
com.sun.jersey.json.impl.provider.entity.JSONArrayProvider$App
com.sun.jersey.json.impl.provider.entity.JSONObjectProvider$App
com.sun.jersey.json.impl.provider.entity.JSONRootElementProvider$App
com.sun.jersey.json.impl.provider.entity.JSONListElementProvider$App
*/* ->
com.sun.jersey.core.impl.provider.entity.FormProvider
com.sun.jersey.core.impl.provider.entity.StringProvider
com.sun.jersey.core.impl.provider.entity.ByteArrayProvider
com.sun.jersey.core.impl.provider.entity.FileProvider
com.sun.jersey.core.impl.provider.entity.InputStreamProvider
com.sun.jersey.core.impl.provider.entity.DataSourceProvider
com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$General
com.sun.jersey.core.impl.provider.entity.ReaderProvider
com.sun.jersey.core.impl.provider.entity.DocumentProvider
com.sun.jersey.core.impl.provider.entity.StreamingOutputProvider
com.sun.jersey.core.impl.provider.entity.SourceProvider$SourceWriter
com.sun.jersey.json.impl.provider.entity.JSONJAXBElementProvider$General
com.sun.jersey.json.impl.provider.entity.JSONArrayProvider$General
com.sun.jersey.json.impl.provider.entity.JSONObjectProvider$General
com.sun.jersey.json.impl.provider.entity.JSONWithPaddingProvider
com.sun.jersey.server.impl.template.ViewableMessageBodyWriter
com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$General
com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$General
com.sun.jersey.json.impl.provider.entity.JSONRootElementProvider$General
com.sun.jersey.json.impl.provider.entity.JSONListElementProvider$General
com.sun.jersey.json.impl.provider.entity.JacksonProviderProxy

To start, here is my guice module
public class MyModule extends ServletModule { @Override public void configureServlets() { // Bind converters for JAXB/JSON serialization. bind(MessageBodyReader.class).to(JacksonJsonProvider.class).in(Singleton.class); bind(MessageBodyWriter.class).to(JacksonJsonProvider.class).in(Singleton.class); // For dictionary resource. bind(MyResource.class); // The JSON REST API is available starting at /rest/*. serve("/rest/*").with(GuiceContainer.class); }

My rest resource is very simple:
@GET @Produces(MediaType.APPLICATION_JSON) public Collection<String> list() { return myset.stream().sorted().collect(toList()); } @POST @Path("/xyz") @Produces(MediaType.APPLICATION_JSON) public Map<String, Boolean> xyz(Collection<String> blah) { return blah.stream().collect(toMap( identity(), s -> myset.contains(s.toLowerCase()))); }


My Gradle build config file looks like this (I assume gradle is not relevant here but the deps defined may be?)
apply plugin: 'jetty' apply plugin: 'war' repositories { mavenCentral() } dependencies { compile 'com.google.guava:guava:16.0.1' compile 'com.google.inject:guice:3.0' compile 'com.google.inject.extensions:guice-servlet:3.0' // Jersey REST. compile 'com.sun.jersey:jersey-core:1.18.1' compile 'com.sun.jersey:jersey-json:1.18.1' compile 'com.sun.jersey:jersey-server:1.18.1' compile 'com.sun.jersey:jersey-servlet:1.18.1' compile 'com.sun.jersey.contribs:jersey-guice:1.18.1' // JSON. compile 'org.codehaus.jackson:jackson-core-asl:1.9.13' compile 'org.codehaus.jackson:jackson-jaxrs:1.9.13' compile 'org.codehaus.jackson:jackson-mapper-asl:1.9.13' // Servlets and javax. compile 'javax.inject:javax.inject:1' providedCompile 'javax.servlet:javax.servlet-api:3.1.0' providedCompile 'javax.servlet:jstl:1.2' providedCompile 'javax.servlet.jsp:jsp-api:2.2' providedCompile 'javax.ws.rs:javax.ws.rs-api:2.0' // Logging. compile 'ch.qos.logback:logback-classic:1.1.1' compile 'org.slf4j:slf4j-api:1.7.6' }

I'm actually running this through gradle, so my command looks something like gradle jettyRun and I should also note that I'm using java 1.8. I was assuming those things wouldn't matter here, but I'm sort of at a loss for explanations since I thought these frameworks would support json collections out of the box. Is that not the case?

Hi thank you very much for your help. Honestly I created the executor functions just to mess around with lamdas, but why wouldn't the executor shut down if there are no more open threads running in it?

edit: I totally agree things would be simpler with that stuff removed, but I was kind of doing things the hard way just to learn.

I'm really sorry if this is not the right way to ask this question, but I was horsing around with lamda functions and what not in java 1.8 and I found out that my simple program doesn't terminate. It prints all the expected results right to the last line of main, but I have to hit ctrl+c for the program to properly terminate. I don't see where I have any open threads still running. Here's the code: class Main { public static void main(String... args) throws Exception { // Read system word dictionary to array. Path input = Paths.get("/usr/share/dict/words"); List<String> words = Files.readAllLines(input, StandardCharsets.UTF_8); // Do each test in a separate thread. ExecutorService executor = Executors.newCachedThreadPool(); Runtime.getRuntime().addShutdownHook(new Thread(() -> executor.shutdown())); // Do some weird manipulations on the find sequentially. Future<Long> sequential = executor.submit(() -> { long start = System.currentTimeMillis(); manipulate(words, false); return System.currentTimeMillis() - start; }); // Do some weird manipulations on the find in parallel. Future<Long> parallel = executor.submit(() -> { long start = System.currentTimeMillis(); manipulate(words, true); return System.currentTimeMillis() - start; }); // Display the results. System.out.printf( "Sequential manipulation completed in %d milliseconds.%n", sequential.get()); System.out.printf( "Parallel manipulation completed in %d milliseconds.%n", parallel.get()); } /** Does some weird things to the collection param for the heck of it. */ static List<String> manipulate(List<String> words, boolean parallel) { return (parallel ? words.stream() : words.parallelStream()) .sorted((o1, o2) -> new Integer(o1.length()).compareTo(o2.length())) .map(s -> s.toLowerCase()) .distinct() .filter(s -> s.length() > 10 && !s.contains("'")) .collect(Collectors.toList()); } }Output

Sequential manipulation completed in 511 milliseconds.
Parallel manipulation completed in 455 milliseconds.
^c

I am trying to use Jetty with ant using these instructions: http://docs.codehaus.org/display/JETTY/Ant+Jetty+Plugin.

Jetty starts up ok but I still to make a few more adjustments:

* Increase JVM memory (set the -Xms, -Xmx, and -XX:MaxPermSize)
* Enable remote debugging

My ant task is defined as such:
<target name="jetty" depends="make-webapp"> <taskdef resource="tasks.properties" loaderref="jetty.loader"> <classpath> <fileset dir="jetty-lib/"> <include name="eclipse-jdt-core-3.1.1.jar" /> <include name="jetty-6.1.26.jar" /> <include name="jetty-ant-6.1.26.jar" /> <include name="jetty-naming-6.1.26.jar" /> <include name="jetty-plus-6.1.26.jar" /> <include name="jetty-util-6.1.26.jar" /> <include name="jsp-2.1-jetty-6.1.16.jar" /> <include name="jsp-api-2.1-glassfish-9.1.1.B51.25.p1.jar" /> <include name="servlet-api-2.5-6.1.5.jar" /> <include name="jsp-2.1-glassfish-9.1.1.B51.25.p1.jar" /> </fileset> </classpath> </taskdef> <mkdir dir="target/work" /> <jetty tempDirectory="target/work"> <webApp name="myapp" warfile="target/myapp" contextpath="/myapp" /> </jetty> </target>
target/myapp has everything it needs including the WEB-INF/lib and WEB-INF/classes folders.

So how can I increase memory and enable remote debugging with this set up?

Just to close the loop on my own thread; the problem was indeed how I configured the additional memory. Apparently --JvmMs, --JvmMx, and --JvmSs parameters to the tomcat7.exe windows service install program were not enough. I had to also specify the --JavaOptions parameters such that I could set the -Xmx and -Xms parameters explicitly.

For example:
set CATALINA_HOME=C:\tomcat set CATALINA_BASE=%CATALINA_HOME%\t1 %CATALINA_HOME%\bin\service.bat install t1 %CATALINA_HOME%\bin\tomcat7.exe //US//t1 \ --DisplayName=t1 \ --Description="Tomcat 7 instance 1" \ --JvmOptions=-Xms256m;-Xmx1024m;-XX:MaxPermSize=256m;-Dcatalina.base=%CATALINA_BASE%;-Dcatalina.home=%CATALINA_HOME%;-Djava.endorsed.dirs=%CATALINA_HOME%\endorsed;-Djava.io.tmpdir=%CATAlINA_BASE%\temp;-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager;-Djava.util.logging.config.file=%CATALINA_BASE%\conf\logging.properties \ --JvmMs=256 --JvmMx=1024 --JvmSs=100000 rem repeat for each instance... rem all that should be on one line
(FYI: I am now using multiple tomcat instances in one single tomcat installation as opposed to several separate installations.)

I'm not exactly sure what the other tomcat7 Jvm parameters are used for. I'm still trying to figure that one out.

I am trying to run multiple tomcat servers on Windows. I have downloaded and installed the tomcat7 zip (not using the installer) to three different folders, and updated the port information so they do not conflict. Everything seems to work fine if I run all three manually using the service.bat script that comes with tomcat.

When executing service.bat manually, I updated the java memory parameters by modifying service.bat as such:
set "JAVA_OPTS=-Xms512m -Xmx1024m -XX:PermSize=512m -XX:MaxPermSize=1024m"
However strange things happen when I run it as a Windows service. I installed the services with the following commands:
cd C:\tomcat1 bin\service.bat install t1 bin\tomcat7.exe //US//t1 --JvmMs=1024 --JvmMx=2048 --JvmSs=1073152 cd C:\tomcat2 bin\service.bat install t2 bin\tomcat7.exe //US//t2 --JvmMs=1024 --JvmMx=2048 --JvmSs=1073152 cd C:\tomcat1\ bin\service.bat install t3 bin\tomcat7.exe //US//t3 --JvmMs=1024 --JvmMx=2048 --JvmSs=1073152

When running these servers I'll see that my web applications stop responding. I don't see any error messages, it's just very slow to respond, and usually doesn't respond at all. Very strange.

Are there any issues with using tomcat7 services like this? Am I doing something crazy with setting the Jvm params in the service install? Any suggestions for how to find the root cause?

Also, is there any chance that are any conflicts with %CATALINA_HOME%? If so, how can I resolve that?

So the problem was with JBoss 4.2.3, which includes incompatible versions of hibernate in jboss/server/default/lib. Removing them resolved the issue.

I actually posted this same question on the hibernate forums, but also posting here in case someone here can help.

So I am trying to upgrade to Hibernate 3.6.0 (from 3.5.2). I'm using JBoss 4.2, Spring 2.1, and the code contains a combination of hbm files and annotations and makes reference to ehcache as well. I can upgrade spring by the way, but I'd prefer not to just yet if I didn't have to.

Anyway, I seem to be unable to find the right combination of hibernate jars right now. The closest I came was with these:* hibernate-commons-annotations-3.2.0.Final.jar * hibernate-c3p0-3.6.0.Final.jar * hibernate-core-3.6.0.Final.jar * hibernate-jpa-2.0-api-1.0.0.Final.jar * hibernate-ehcache-3.6.0.Final.jar * hibernate-validator-3.0.0.GA.jar I may not need all of those but JBoss seems to start without error with that combination. However my unit tests fail on save operations with this stack trace:java.lang.NoSuchMethodError: org.hibernate.event.PreInsertEvent.getSource()Lorg/hibernate/engine/SessionImplementor; at org.hibernate.validator.event.ValidateEventListener.onPreInsert(ValidateEventListener.java:172) at org.hibernate.action.EntityInsertAction.preInsert(EntityInsertAction.java:178) at org.hibernate.action.EntityInsertAction.execute(EntityInsertAction.java:72) at org.hibernate.engine.ActionQueue.execute(ActionQueue.java:273) at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:265) at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:184) at org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:321) at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:51) at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1216) at org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java:383) at org.hibernate.transaction.JDBCTransaction.commit(JDBCTransaction.java:133) at org.springframework.orm.hibernate3.HibernateTransactionManager.doCommit(HibernateTransactionManager.java:555) at org.springframework.transaction.support.AbstractPlatformTransactionManager.processCommit(AbstractPlatformTransactionManager.java:662) at org.springframework.transaction.support.AbstractPlatformTransactionManager.commit(AbstractPlatformTransactionManager.java:632) at org.springframework.transaction.interceptor.TransactionAspectSupport.commitTransactionAfterReturning(TransactionAspectSupport.java:314) at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:117) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161) at org.springframework.aop.interceptor.AbstractTraceInterceptor.invoke(AbstractTraceInterceptor.java:113) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at $Proxy44.save(Unknown Source) ....At this point I started trying varying combinations of jars. Namely I tried upgrading to hibernate-validator-4.0.1.Final, but no matter what, I always seem to run into this error when starting up JBoss now:... Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'sessionFactory' defined in ServletContext resource [/WEB-INF/classes/applicationContext.xml]: Invocation of init method failed; nested exception is [b]org.hibernate.AnnotationException: java.lang.NoSuchMethodException: org.hibernate.validator.ClassValidator.<init>(java.lang.Class, java.util.ResourceBundle, org.hibernate.validator.MessageInterpolator, java.util.Map, org.hibernate.annotations.common.reflection.ReflectionManager)[/b] Caused by: org.hibernate.AnnotationException: java.lang.NoSuchMethodException: org.hibernate.validator.ClassValidator.<init>(java.lang.Class, java.util.ResourceBundle, org.hibernate.validator.MessageInterpolator, java.util.Map, org.hibernate.annotations.common.reflection.ReflectionManager) at org.hibernate.cfg.Configuration.applyHibernateValidatorLegacyConstraintsOnDDL(Configuratio n.java:1651) at org.hibernate.cfg.Configuration.applyConstraintsToDDL(Configuration.java:1623) at org.hibernate.cfg.Configuration.secondPassCompile(Configuration.java:1415) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1826) at org.springframework.orm.hibernate3.LocalSessionFactoryBean.newSessionFactory(LocalSessionF actoryBean.java:728) at org.springframework.orm.hibernate3.LocalSessionFactoryBean.buildSessionFactory(LocalSessio nFactoryBean.java:668) at org.springframework.orm.hibernate3.AbstractSessionFactoryBean.afterPropertiesSet(AbstractS essionFactoryBean.java:211) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMet hods(AbstractAutowireCapableBeanFactory.java:1201) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBea n(AbstractAutowireCapableBeanFactory.java:1171) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(Ab stractAutowireCapableBeanFactory.java:425) at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFact ory.java:251) at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(Defaul tSingletonBeanRegistry.java:156) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory. java:248) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory. java:160) at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(Bea nDefinitionValueResolver.java:261) at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecess ary(BeanDefinitionValueResolver.java:109) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyProperty Values(AbstractAutowireCapableBeanFactory.java:1099) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean( AbstractAutowireCapableBeanFactory.java:861) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(Ab stractAutowireCapableBeanFactory.java:421) at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFact ory.java:251) at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(Defaul tSingletonBeanRegistry.java:156) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory. java:248) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory. java:160) at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(Bea nDefinitionValueResolver.java:261) at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecess ary(BeanDefinitionValueResolver.java:109) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyProperty Values(AbstractAutowireCapableBeanFactory.java:1099) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean( AbstractAutowireCapableBeanFactory.java:861) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(Ab stractAutowireCapableBeanFactory.java:421) at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFact ory.java:251) at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(Defaul tSingletonBeanRegistry.java:156) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory. java:248) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory. java:160) at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(Bea nDefinitionValueResolver.java:261) at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecess ary(BeanDefinitionValueResolver.java:109) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyProperty Values(AbstractAutowireCapableBeanFactory.java:1099) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean( AbstractAutowireCapableBeanFactory.java:861) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(Ab stractAutowireCapableBeanFactory.java:421) at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFact ory.java:251) at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(Defaul tSingletonBeanRegistry.java:156) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory. java:248) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory. java:160) at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSinglet ons(DefaultListableBeanFactory.java:287) at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplication Context.java:352) at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.ja va:244) at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java :187) at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderList ener.java:49) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3856) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4361) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:790) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:770) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:553) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) ... I have no idea where org.hibernate.validator.ClassValidator is nor do I know who is requiring it.

Currently I am at a loss. Is this a jar dependency issue? If so, what jars do I need? If not, should I make any code changes? Any help would be greatly appreciated on this issue.

When throwing an exception in one of my Axis service methods I notice that there is a detail section in the soap response. This is Axis 1.1 btw and the code looks like this:
public class Serivce extends ServletEndpointSupport { public void serviceMethod() { throw new Exception("very bad"); } }
which produces output like this:
<soapenv:Envelope...> <soapenv:Body ...> <soapenv:Fault ...> <faultcode>...</faultcode> <faultstring>...</faultstring> <detail><ns1:hostname xmlns:ns1="http://xml.apache.org/axis/">hostname</ns1:hostname> </detail> </soapenv:Fault> </soapenv:Body> </soapenv:Envelope>
I don't mind the detail section and I believe it is used for custom object properties, but is there any way to remove the hostname node or control the exception output? In this case I don't want to reveal my server host name.

The maven standard directory layout guidelines specify a src/main/config folder. However I notice that files included in this folder do not seem to end up in my jar file unless I specifically specify a sourceDirectory setting inside the build node of pom.xml.

Doesn't this defeat the point if I have to manually specify this folder? Is there a reason src/main/config is not treated as a source folder by default in maven? Should I be putting stuff in that folder (i.e. log4j.xml) at all? If so, what is appropriate to put there and how is it different than src/main/resources?

Currently I am using several file appenders in my log4j configuration. They are all the same except they are used by different loggers and write to a different file name. Is there a way to specify the file name as a parameter to the appender so I don't have to keep copying and pasting the same appender information?

An example for what I am looking for might look something like this:

<appender name="fileAppender" class="org.apache.log4j.RollingFileAppender"> ... <param name="File" value="/logs/FILE_NAME." /> ... </appender> <logger name="mylogger1"> <appender-ref ref="fileAppender" fileName="db.log" /> </logger> <logger name="mylogger2"> <appender-ref ref="fileAppender" fileName="error.log" /> </logger>

Is it possible to do something like this with log4j?

Ulf Dittmer wrote:That assumes a Servlet 3.0 container, which are not widely used yet.

Yes, I'm using the 2.5 Java EE API where HttpServletResponse.getHeaders is not yet implemented.

It looks like 3.0 is still a draft specification? I don't think I am ready to adopt it yet.

Is there any other less obvious way to read the response headers?

Is there any way to read HTTP response headers with Servlets? HttpServletResponse does not seem to have anything that serves this purpose.

Also I'm using a JBoss server, so if there is no way to do this with the Servlet spec, is there some JBoss specific way of reading this information before it gets served?

I want to log HTTP Headers using Apache Axis 1.1 (may upgrade Axis2 eventually).

I am able to fetch the HttpServletRequest from the handler and log the request HTTP headers using that, but I cannot figure out how to access the response HTTP headers since HttpServletResponse does not seem to provide access to that information. Is there a way to get at this information with Axis?

My technique for getting the request HTTP headers is like this by the way:
public class RequestHandler extends BasicHandler { @Override public void invoke(MessageContext context) throws AxisFault { if (!(context.getProperty("transport.http.servletRequest") instanceof HttpServletRequest)) return; StringBuilder headers = new StringBuilder(); HttpServletRequest request = (HttpServletRequest)context.getProperty("transport.http.servletRequest"); Enumeration e = request.getHeaderNames(); while (e.hasMoreElements()) { String headerName = (String)e.nextElement(); headers.append(String.format("%s: %s%n", headerName, request.getHeader(headerName))); } // log System.out.println(headers.toString()); } }


Is there way to do something similar with the response?

Also is there a way to have my handler run last in Axis 1.1?

I have an object that will start reading and writing a bunch of files from and to disk. I would like to be able to test this without actually having to write out data though.

In my initial implementation I was just passing around input and output directory strings and letting my object do what it needed to from there, but I realize this is hard to test. I was thinking to use InputStream and OutputStream parameters instead which would let me use byte streams in testing, I suppose, but I don't think I can write new files with OutputStreams.

Now I'm thinking to make a factory object that I will mock out later and return byte streams instead of file output streams in testing but this seems less than ideal. I'd really like to mock File and Stream objects but I'm not sure what the best approach for that is. I will need things like File.isDirectory, File.mkdir, and new FileOutputStream(new File(directory, newFileToCreate)). Sorry if I haven't done a good job of explaining my issue, but can anyone recommend some best practices for testing things that use File I/O in Java?