You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Hugo Palma (JIRA)" <de...@tapestry.apache.org> on 2007/06/16 20:55:25 UTC

[jira] Created: (TAPESTRY-1581) It should be possible to provide a jetty.xml file to JettyRunner

It should be possible to provide a jetty.xml file to JettyRunner
----------------------------------------------------------------

                 Key: TAPESTRY-1581
                 URL: https://issues.apache.org/jira/browse/TAPESTRY-1581
             Project: Tapestry
          Issue Type: Wish
          Components: tapestry-test
    Affects Versions: 5.0.4
            Reporter: Hugo Palma


Right now it's not possible to provide the JettyRunner with a jetty.xml file. This doesn't allow for one to configure the application with for example JNDI resources and more.

Almost every web application uses some kind of resource, it has to be possible to configure them when running the integrations tests.
I think this would require the use of Jetty 6, but that shouldn't be a problem....i think

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


[jira] Commented: (TAPESTRY-1581) It should be possible to provide a jetty.xml file to JettyRunner

Posted by "Hugo Palma (JIRA)" <de...@tapestry.apache.org>.
    [ https://issues.apache.org/jira/browse/TAPESTRY-1581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12508166 ] 

Hugo Palma commented on TAPESTRY-1581:
--------------------------------------

I got some answers from the selenium folks, it seems the plan is to change to Jetty6 after the selenium-rc 1.0 release.

So, i'm thinking maybe it's better to just wait for that to happen.
I'm closing this.

> It should be possible to provide a jetty.xml file to JettyRunner
> ----------------------------------------------------------------
>
>                 Key: TAPESTRY-1581
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-1581
>             Project: Tapestry
>          Issue Type: Wish
>          Components: tapestry-test
>    Affects Versions: 5.0.4
>            Reporter: Hugo Palma
>
> Right now it's not possible to provide the JettyRunner with a jetty.xml file. This doesn't allow for one to configure the application with for example JNDI resources and more.
> Almost every web application uses some kind of resource, it has to be possible to configure them when running the integrations tests.
> I think this would require the use of Jetty 6, but that shouldn't be a problem....i think

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


[jira] Commented: (TAPESTRY-1581) It should be possible to provide a jetty.xml file to JettyRunner

Posted by "Hugo Palma (JIRA)" <de...@tapestry.apache.org>.
    [ https://issues.apache.org/jira/browse/TAPESTRY-1581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12508139 ] 

Hugo Palma commented on TAPESTRY-1581:
--------------------------------------

I've actually taken a shot at implementing this, in the process i found that selenium is much more closely tied to Jetty 5 than i thought.
I started fiddling with the classpath and stuff but didn't find a way to get it working without being too intrusive.

So i guess it's best if we just wait for selenium to catch up and start using Jetty 6, unless someone finds a way of doing this of course...

I've posted the question about selenium with Jetty 6 in the openqa forum(http://forums.openqa.org/thread.jspa?threadID=8787), hoping to get some answers there....

> It should be possible to provide a jetty.xml file to JettyRunner
> ----------------------------------------------------------------
>
>                 Key: TAPESTRY-1581
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-1581
>             Project: Tapestry
>          Issue Type: Wish
>          Components: tapestry-test
>    Affects Versions: 5.0.4
>            Reporter: Hugo Palma
>
> Right now it's not possible to provide the JettyRunner with a jetty.xml file. This doesn't allow for one to configure the application with for example JNDI resources and more.
> Almost every web application uses some kind of resource, it has to be possible to configure them when running the integrations tests.
> I think this would require the use of Jetty 6, but that shouldn't be a problem....i think

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


[jira] Closed: (TAPESTRY-1581) It should be possible to provide a jetty.xml file to JettyRunner

Posted by "Hugo Palma (JIRA)" <de...@tapestry.apache.org>.
     [ https://issues.apache.org/jira/browse/TAPESTRY-1581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hugo Palma closed TAPESTRY-1581.
--------------------------------

    Resolution: Won't Fix

> It should be possible to provide a jetty.xml file to JettyRunner
> ----------------------------------------------------------------
>
>                 Key: TAPESTRY-1581
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-1581
>             Project: Tapestry
>          Issue Type: Wish
>          Components: tapestry-test
>    Affects Versions: 5.0.4
>            Reporter: Hugo Palma
>
> Right now it's not possible to provide the JettyRunner with a jetty.xml file. This doesn't allow for one to configure the application with for example JNDI resources and more.
> Almost every web application uses some kind of resource, it has to be possible to configure them when running the integrations tests.
> I think this would require the use of Jetty 6, but that shouldn't be a problem....i think

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


[jira] Commented: (TAPESTRY-1581) It should be possible to provide a jetty.xml file to JettyRunner

Posted by "Hugo Palma (JIRA)" <de...@tapestry.apache.org>.
    [ https://issues.apache.org/jira/browse/TAPESTRY-1581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507669 ] 

Hugo Palma commented on TAPESTRY-1581:
--------------------------------------

True, but only the selenium server component right ?

I don't this invalidates the fact that you could run the application being tested in Jetty 6 or even any other container like Tomcat or whatever. Selenium-RC just issues HTTP commands to any running listener, it doesn't care about the container.

The fact that the selenium pom references jetty 5 as a dependency could make it a little trickier classpath wise, but i think it can be worked around.....

I wouldn't insist on this if i didn't feel it was important....it's just that not being able to integration test with configured resources just doesn't cut it for most applications.

> It should be possible to provide a jetty.xml file to JettyRunner
> ----------------------------------------------------------------
>
>                 Key: TAPESTRY-1581
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-1581
>             Project: Tapestry
>          Issue Type: Wish
>          Components: tapestry-test
>    Affects Versions: 5.0.4
>            Reporter: Hugo Palma
>
> Right now it's not possible to provide the JettyRunner with a jetty.xml file. This doesn't allow for one to configure the application with for example JNDI resources and more.
> Almost every web application uses some kind of resource, it has to be possible to configure them when running the integrations tests.
> I think this would require the use of Jetty 6, but that shouldn't be a problem....i think

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


[jira] Commented: (TAPESTRY-1581) It should be possible to provide a jetty.xml file to JettyRunner

Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
    [ https://issues.apache.org/jira/browse/TAPESTRY-1581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507651 ] 

Howard M. Lewis Ship commented on TAPESTRY-1581:
------------------------------------------------

Selenium is tied to Jetty 5.

> It should be possible to provide a jetty.xml file to JettyRunner
> ----------------------------------------------------------------
>
>                 Key: TAPESTRY-1581
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-1581
>             Project: Tapestry
>          Issue Type: Wish
>          Components: tapestry-test
>    Affects Versions: 5.0.4
>            Reporter: Hugo Palma
>
> Right now it's not possible to provide the JettyRunner with a jetty.xml file. This doesn't allow for one to configure the application with for example JNDI resources and more.
> Almost every web application uses some kind of resource, it has to be possible to configure them when running the integrations tests.
> I think this would require the use of Jetty 6, but that shouldn't be a problem....i think

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org