June 2013 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQ-1421) addAsWebInfResource doesn't work with Arquillian 1.0.4.Final

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1421?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen moved SHRINKWRAP-458 to ARQ-1421: ----------------------------------------------- Project: Arquillian (was: ShrinkWrap) Key: ARQ-1421 (was: SHRINKWRAP-458) Affects Version/s: 1.0.4.Final (was: 1.1.2) Component/s: Base Implementation (was: impl-base) Security: Public > addAsWebInfResource doesn't work with Arquillian 1.0.4.Final > ------------------------------------------------------------ > > Key: ARQ-1421 > URL: https://issues.jboss.org/browse/ARQ-1421 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.0.4.Final > Environment: Arquillian 1.0.4.Final > Reporter: Ron Šmeral > Attachments: shrinkwrap458-reproducer.zip > > > When using {{addAsWebInfResource}} with ShrinkWrap 1.1.2 and Arquillian 1.0.4.Final, the added WEB-INF resources are 0 bytes in size. > With Arquillian 1.0.3.Final this works OK. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1419) Add support for Jetty 9

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/ARQ-1419?page=com.atlassian.jira.plugin.s... ] Martin Kouba commented on ARQ-1419: ----------------------------------- Yes, it's HTTP only. With regard to the descriptor deployment - the only relevant documentation I found is this: https://docs.jboss.org/author/display/ARQ/Descriptor+deployment. However I checked the AS7/WildFly container adapter and it seems it does not support this either. So I think we can live without this feature for now and add the support later. WDYT? > Add support for Jetty 9 > ----------------------- > > Key: ARQ-1419 > URL: https://issues.jboss.org/browse/ARQ-1419 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Jetty Containers > Reporter: Martin Kouba > Assignee: Martin Kouba > > {{arquillian-jetty-embedded-7}} is not compatible with Jetty 9. If used together, the result is: *java.lang.ClassNotFoundException: org.eclipse.jetty.server.nio.SelectChannelConnector*. > {{SelectChannelConnector}} is used in {{JettyEmbeddedContainer}} and it seems it's no longer part of Jetty 9. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1419) Add support for Jetty 9

by Jesse McConnell (JIRA)

[ https://issues.jboss.org/browse/ARQ-1419?page=com.atlassian.jira.plugin.s... ] Jesse McConnell commented on ARQ-1419: -------------------------------------- So this is just for http testing right? It seems fine at first blush, though I have to ask what the descriptor concept is that is stubbed out as not supported...maybe I can help you out there. > Add support for Jetty 9 > ----------------------- > > Key: ARQ-1419 > URL: https://issues.jboss.org/browse/ARQ-1419 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Jetty Containers > Reporter: Martin Kouba > Assignee: Martin Kouba > > {{arquillian-jetty-embedded-7}} is not compatible with Jetty 9. If used together, the result is: *java.lang.ClassNotFoundException: org.eclipse.jetty.server.nio.SelectChannelConnector*. > {{SelectChannelConnector}} is used in {{JettyEmbeddedContainer}} and it seems it's no longer part of Jetty 9. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-197) Support for Page Objects encapsulating location

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-197?page=com.atlassian.jira.plugin... ] Juraj Húska commented on ARQGRA-197: ------------------------------------ I have committed the state of the art of my work to [this|https://github.com/jhuska/arquillian-graphene/tree/ARQGRA-197-2] branch. It is not completed. I am stuck with Jetty embedded issue I guess. It incorrectly deploy .war in a multiple deployment scenario. I will introduce another container maybe if that will be a issue. > Support for Page Objects encapsulating location > ----------------------------------------------- > > Key: ARQGRA-197 > URL: https://issues.jboss.org/browse/ARQGRA-197 > Project: Arquillian Graphene > Issue Type: Feature Request > Affects Versions: 2.0.0.Alpha2 > Reporter: Lukáš Fryč > Assignee: Juraj Húska > Priority: Minor > Fix For: 2.0.0.Alpha5 > > Original Estimate: 6 hours > Remaining Estimate: 6 hours > > {code:java|title=ConferencePage.java} > @Location("view/conference/create.jsf") > public class ConferencePage { > > @FindBy(id = "create") > private ConferenceForm form; > > public ConferenceForm getForm() { > return form; > } > } > public class ConferencePage implements Bookmarkable { > > @FindBy(id = "create") > private ConferenceForm form; > > public ConferenceForm getForm() { > return form; > } > public String getLocation() { > return "view/conference/create.jsf"; > } > } > {code} > {code:java|title=Test.java} > @Test > public void test() { > ConferencePage page = goTo(ConferencePage.class); > ConferenceForm = page.getForm(); > } > {code} > The only issue is that it is not sure on which deployment and with what browser should given Page operate. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-310) initialized public field of page object is reinitialized to null

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-310?page=com.atlassian.jira.plugin... ] Lukáš Fryč reassigned ARQGRA-310: --------------------------------- Assignee: Juraj Húska Juraj, I think this is bug since the {{By}} field shouldn't be touched by Graphene at all unless it is annotated with {{@FindBy}}. > initialized public field of page object is reinitialized to null > ---------------------------------------------------------------- > > Key: ARQGRA-310 > URL: https://issues.jboss.org/browse/ARQGRA-310 > Project: Arquillian Graphene > Issue Type: Bug > Reporter: Jiří Štefek > Assignee: Juraj Húska > > When one has a page object with initialized public field like this: > https://github.com/richfaces/richfaces-qa/blob/212c0bf1c97de103e4fb381319... > and he uses it in test: > https://github.com/richfaces/richfaces-qa/blob/212c0bf1c97de103e4fb381319... > then he gets: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/RichFaces/view/5.0/... > The cause is, that the field is reinitialized to null in that @Page object. > There is an easy workaround: do not use public fields in @Page objects. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-310) initialized public field of page object is reinitialized to null

by Jiří Štefek (JIRA)

Jiří Štefek created ARQGRA-310: ---------------------------------- Summary: initialized public field of page object is reinitialized to null Key: ARQGRA-310 URL: https://issues.jboss.org/browse/ARQGRA-310 Project: Arquillian Graphene Issue Type: Bug Reporter: Jiří Štefek When one has a page object with initialized public field like this: https://github.com/richfaces/richfaces-qa/blob/212c0bf1c97de103e4fb381319... and he uses it in test: https://github.com/richfaces/richfaces-qa/blob/212c0bf1c97de103e4fb381319... then he gets: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/RichFaces/view/5.0/... The cause is, that the field is reinitialized to null in that @Page object. There is an easy workaround: do not use public fields in @Page objects. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-197) Support for Page Objects encapsulating location

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-197?page=com.atlassian.jira.plugin... ] Work on ARQGRA-197 started by Juraj Húska. > Support for Page Objects encapsulating location > ----------------------------------------------- > > Key: ARQGRA-197 > URL: https://issues.jboss.org/browse/ARQGRA-197 > Project: Arquillian Graphene > Issue Type: Feature Request > Affects Versions: 2.0.0.Alpha2 > Reporter: Lukáš Fryč > Assignee: Juraj Húska > Priority: Minor > Fix For: 2.0.0.Alpha5 > > Original Estimate: 6 hours > Remaining Estimate: 6 hours > > {code:java|title=ConferencePage.java} > @Location("view/conference/create.jsf") > public class ConferencePage { > > @FindBy(id = "create") > private ConferenceForm form; > > public ConferenceForm getForm() { > return form; > } > } > public class ConferencePage implements Bookmarkable { > > @FindBy(id = "create") > private ConferenceForm form; > > public ConferenceForm getForm() { > return form; > } > public String getLocation() { > return "view/conference/create.jsf"; > } > } > {code} > {code:java|title=Test.java} > @Test > public void test() { > ConferencePage page = goTo(ConferencePage.class); > ConferenceForm = page.getForm(); > } > {code} > The only issue is that it is not sure on which deployment and with what browser should given Page operate. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1419) Add support for Jetty 9

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/ARQ-1419?page=com.atlassian.jira.plugin.s... ] Martin Kouba commented on ARQ-1419: ----------------------------------- Here's the first attempt: https://github.com/mkouba/arquillian-container-jetty/tree/ARQ-1419 Actually I did not create anything new just reused existing code and fixed up some Jetty 9 relevant issues (and the code might deserve some refactoring). Jesse McConnell: Please could you have a look at this branch? I also updated the Weld version (1.1.1.Final -> 1.1.13.Final) because there was a backwards compatibility issue with SLF4J. > Add support for Jetty 9 > ----------------------- > > Key: ARQ-1419 > URL: https://issues.jboss.org/browse/ARQ-1419 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Jetty Containers > Reporter: Martin Kouba > Assignee: Martin Kouba > > {{arquillian-jetty-embedded-7}} is not compatible with Jetty 9. If used together, the result is: *java.lang.ClassNotFoundException: org.eclipse.jetty.server.nio.SelectChannelConnector*. > {{SelectChannelConnector}} is used in {{JettyEmbeddedContainer}} and it seems it's no longer part of Jetty 9. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1420) The PayloadRegistry#registerResponsePayload() is being called after the #retrieveResponsePayload() which ends up with ResponsePayloadWasNeverRegistered exception.

by Jakub Narloch (JIRA)

[ https://issues.jboss.org/browse/ARQ-1420?page=com.atlassian.jira.plugin.s... ] Jakub Narloch commented on ARQ-1420: ------------------------------------ Please see: https://github.com/jmnarloch/arquillian-extension-warp-rest. After running the mvn clean install, all the tests will pass except for StockServiceResourceTestCase#testStockGetWarp test from arquillian-warp-jaxrs-ftest-cxf. Which fails with fallowing error: {code} Tests run: 3, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 69.816 sec <<< FAILURE! testStockGetWarp(org.jboss.arquillian.quickstart.cxf.service.rs.StockServiceResourceTestCase) Time elapsed: 61.942 sec <<< ERROR! org.jboss.arquillian.warp.exception.ServerWarpExecutionException: The error occured during server request processing: The response payload with serialId 4065404507533364875 was never registered at org.jboss.arquillian.warp.impl.client.execution.DefaultResponseDeenrichmentService.retrieveResponsePayload(DefaultResponseDeenrichmentService.java:121) at org.jboss.arquillian.warp.impl.client.execution.DefaultResponseDeenrichmentService.deenrichResponse(DefaultResponseDeenrichmentService.java:84) at org.jboss.arquillian.warp.impl.client.execution.EnrichmentObserver.deenrichResponse(EnrichmentObserver.java:98) {code} > The PayloadRegistry#registerResponsePayload() is being called after the #retrieveResponsePayload() which ends up with ResponsePayloadWasNeverRegistered exception. > ------------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: ARQ-1420 > URL: https://issues.jboss.org/browse/ARQ-1420 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha3 > Reporter: Jakub Narloch > Assignee: Lukáš Fryč > > I'm facing some problem in the JAX-RS extension for the CXF. I'm already know that the CXF filter is doing a explicit OutputStream.flush() on the response, but not sure whether this affects anything. Although, it is worth to mention that I'm not facing any problems with other implementations. Currently I was able to debug only that the #retrieveResponsePayload() is being called before the payload registration, which cause an exception to be raised. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1420) The PayloadRegistry#registerResponsePayload() is being called after the #retrieveResponsePayload() which ends up with ResponsePayloadWasNeverRegistered exception.

by Jakub Narloch (JIRA)

[ https://issues.jboss.org/browse/ARQ-1420?page=com.atlassian.jira.plugin.s... ] Jakub Narloch updated ARQ-1420: ------------------------------- Assignee: Lukáš Fryč > The PayloadRegistry#registerResponsePayload() is being called after the #retrieveResponsePayload() which ends up with ResponsePayloadWasNeverRegistered exception. > ------------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: ARQ-1420 > URL: https://issues.jboss.org/browse/ARQ-1420 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha3 > Reporter: Jakub Narloch > Assignee: Lukáš Fryč > > I'm facing some problem in the JAX-RS extension for the CXF. I'm already know that the CXF filter is doing a explicit OutputStream.flush() on the response, but not sure whether this affects anything. Although, it is worth to mention that I'm not facing any problems with other implementations. Currently I was able to debug only that the #retrieveResponsePayload() is being called before the payload registration, which cause an exception to be raised. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues June 2013