6 Replies Latest reply on Apr 7, 2011 10:09 AM by ozizka

Implementing DeploymentContainer - What to put to ProtocolMetaData?

ozizka Apr 1, 2011 7:25 PM

Hi,

What's to be filled into ProtocolMetadata? Any doc/wiki on this?

I've this Tomcat's output from /manager/list

OK - Listed applications for virtual host localhost
/:running:0:ROOT
/manager:running:1:manager
/docs:running:0:docs
/examples:running:0:examples
/host-manager:running:0:host-manager

So I parsed it as follows

    private ProtocolMetaData parseForProtocolMetaData(String textResponse) {
        final ProtocolMetaData protocolMetaData = new ProtocolMetaData();
        final HTTPContext httpContext = new HTTPContext(this.conf.getHost(), this.conf.getHttpPort());

        String[] lines = textResponse.split("\\n");
        for (int i = 1; i < lines.length; i++) {
            String line = lines[i];
            String[] parts = line.split(":");
            if( parts.length < 4 ) continue;
            httpContext.add(new Servlet(parts[0], parts[3]));
        }

        protocolMetaData.addContext(httpContext);
        return protocolMetaData;
    }

Is that correct?

I'm getting this (in a test I stolen from the tomcat embedded impl ;-)

shouldBeAbleToInjectMembersIntoTestClass(org.jboss.arquillian.container.tomcat.remote_6.TomcatRemoteInContainerTestCase)  Time elapsed: 0.006 sec  <<< ERROR!
java.lang.IllegalArgumentException: ArquillianServletRunner not found. Could not determine ContextRoot from ProtocolMetadata, please contact DeployableContainer developer.
    at org.jboss.arquillian.protocol.servlet.ServletUtil.determineBaseURI(ServletUtil.java:63)
    at org.jboss.arquillian.protocol.servlet.BaseServletProtocol.getExecutor(BaseServletProtocol.java:56)
    at org.jboss.arquillian.protocol.servlet.BaseServletProtocol.getExecutor(BaseServletProtocol.java:30)
    at org.jboss.arquillian.impl.execution.RemoteTestExecuter.getContainerMethodExecutor(RemoteTestExecuter.java:105)
    at org.jboss.arquillian.impl.execution.RemoteTestExecuter.execute(RemoteTestExecuter.java:96)

Which seems like I should pack something into the archive.

Thanks for hints.

1. Implementing DeploymentContainer - What to put to ProtocolMetaData?

ozizka Apr 1, 2011 8:13 PM (in response to ozizka)

I think I got it... the list from Tomcat doesn't contain listing of servlet mappings, so I am shifted one level up in what I am parsing
Actions
2. Implementing DeploymentContainer - What to put to ProtocolMetaData?

aslak Apr 4, 2011 5:14 AM (in response to ozizka)

Yea, the ProtocolMetaData should contain a HTTPContext with all Servlets in the Deployment.
Actions
3. Implementing DeploymentContainer - What to put to ProtocolMetaData?

ozizka Apr 4, 2011 7:06 AM (in response to aslak)

What does it use for? What if I don't fill it?
Actions
4. Implementing DeploymentContainer - What to put to ProtocolMetaData?

aslak Apr 4, 2011 7:26 AM (in response to ozizka)

It is used by the Protocol implementation, e.g. Servlet 2.5/3.0. They add them selves to the deployment in the packaging phase so the test can be executed incontainer. They expect if(when) you execute the @Test to find 'them sevles' in the metadata to know which ip/port/contextRoot to use to execute against. If you don't provide this info, only Client mode will work.

Also, the @ArquillianResource URL injection point enricher use this info to fetch baseURL from your deployment. e.g.

@ArquillianResource(MyServlet.class) URL baseUrl; <-- could be http://localhost:8080/my.war/
Actions
5. Re: Implementing DeploymentContainer - What to put to ProtocolMetaData?

ozizka Apr 7, 2011 10:02 AM (in response to ozizka)
I'm still not able to fix ArquillianServletRunner not found.
We discussed the HTTPContext, now I am filling it correctly, but that error is caused by the server not being packed to the WAR.

I have found org.jboss.arquillian.protocol.servlet.v_3.web-fragment.xml. There's

<servlet> <servlet-name>ArquillianServletRunner</servlet-name> <servlet-class>org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner</servlet-class> </servlet> <servlet-mapping> <servlet-name>ArquillianServletRunner</servlet-name> <url-pattern>/ArquillianServletRunner</url-pattern> </servlet-mapping>

But it seems it's not applied to the web.xml of my war (created by ShrinkWrap).
I've also tried to add org.jboss.arquillian.protocol.servlet.ServletUtil.class.getPackage() to addPackages (recursively); didn't help.

What should I try next?
Actions
6. Re: Implementing DeploymentContainer - What to put to ProtocolMetaData?

ozizka Apr 7, 2011 10:09 AM (in response to ozizka)

I will try to use the ProtocolDeploymentAppender from my appender.
Actions

Go to original post