November 2006 - jbossws-dev - Jboss List Archives

[Design of JBoss Web Services] - Re: ws-eventing: event notification failure

by heiko.braun＠jboss.com

sorry, i did not get anything View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3985861#3985861 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3985861

19 years, 4 months

1
0
0 / 0

RE: MTOM test

by Heiko Braun

It tests StreamSource contents. But this particular example more less demo's a simple MTOM scenario and is Not really a unit test. Does it have to? -----Original Message----- From: Thomas Diesler [mailto:thomas.diesler@redhat.com] Sent: Tuesday, November 14, 2006 2:54 PM To: Heiko Braun; jbossws-dev(a)lists.jboss.org Subject: MTOM test Heiko, what is this actually testing? AFICS, the content of getLegacyData() can be anything. public void testQuery() throws Exception { Query query = new Query("Peter", "Pan"); Employee employee = port.queryEmployee(query); assertNotNull(employee); assertNotNull(employee.getLegacyData()); StreamSource xmlStream = (StreamSource)employee.getLegacyData().getContent(); IOUtils.copyStream(System.out, xmlStream.getInputStream()); } cheers -thomas -- xxxxxxxxxxxxxxxxxxxxxxxxxxxx Thomas Diesler Web Service Lead JBoss, a division of Red Hat xxxxxxxxxxxxxxxxxxxxxxxxxxxx

19 years, 4 months

1
0
0 / 0

MTOM test

by Thomas Diesler

Heiko, what is this actually testing? AFICS, the content of getLegacyData() can be anything. public void testQuery() throws Exception { Query query = new Query("Peter", "Pan"); Employee employee = port.queryEmployee(query); assertNotNull(employee); assertNotNull(employee.getLegacyData()); StreamSource xmlStream = (StreamSource)employee.getLegacyData().getContent(); IOUtils.copyStream(System.out, xmlStream.getInputStream()); } cheers -thomas -- xxxxxxxxxxxxxxxxxxxxxxxxxxxx Thomas Diesler Web Service Lead JBoss, a division of Red Hat xxxxxxxxxxxxxxxxxxxxxxxxxxxx

19 years, 4 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBAS-3766, port the webservice deployer

by scott.stark＠jboss.org

Support for an alt-dd specification at the WebMetaData level has been added. The org.jboss.test.web.test.AltDDUnitTestCase illustrates this from the ear application.xml level. The jbossws deployer could just set this directly on the WebMetaData instance before the war deployer runs. The alt dd needs to be in the unpacked war WEB-INF directory. The WebMetaData specification is treated as a deployment relative path that is first treated as a war WEB-INF path, and then as a path from the root of the top level deployment. This is copied into the expanded war WEB-INF as tomcat needs to see this as an absolute file path currently. There are changes in both the mc jboss-deployers.jar and tomcat jbossweb.jar to support this. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3985688#3985688 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3985688

19 years, 4 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JSR-181 Annotation Based UDDI Registration

by kurt.stam＠jboss.com

Check out this http://www.jboss.com/index.html?module=bb&op=viewtopic&t=91113 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3985684#3985684 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3985684

19 years, 4 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: ws-eventing: event notification failure

by maeste

I have just write you an email with subject "WS-EVENTING" View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3985429#3985429 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3985429

19 years, 4 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBAS-3766, port the webservice deployer

by jason.greene＠jboss.com

"scott.stark(a)jboss.org" wrote : Another issue I'm seeing with the current JAXWSDeployerJSE is that it is trying to use the deployment class loader before the class loading deployers have committed. The JAXWSDeployerJSE should be before the WarDeployer, not just after the JBossWebAppParsingDeployer as use of the deployment class loader requires the deployer to be after the CLASSLOADER_DEPLOYER. I created a JBoss5VDFDeployerOrdering page as a reference for how to choose the deployer relative order: | http://wiki.jboss.org/wiki/Wiki.jsp?page=JBoss5VDFDeployerOrdering | I took a look at fixing this, but the classloader constructed by the deployer fails because the jar url returned from the VFS refers to "!/WEB-INF/classes instead of "!/WEB-INF/classes/". See the follow post for more info: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3985315#3985315 -Jason View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3985317#3985317 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3985317

19 years, 4 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBAS-3766, port the webservice deployer

by scott.stark＠jboss.org

Another issue I'm seeing with the current JAXWSDeployerJSE is that it is trying to use the deployment class loader before the class loading deployers have committed. The JAXWSDeployerJSE should be before the WarDeployer, not just after the JBossWebAppParsingDeployer as use of the deployment class loader requires the deployer to be after the CLASSLOADER_DEPLOYER. I created a JBoss5VDFDeployerOrdering page as a reference for how to choose the deployer relative order: http://wiki.jboss.org/wiki/Wiki.jsp?page=JBoss5VDFDeployerOrdering It has also hard-coded its order so it cannot be overriden at the deployer descriptor level (http://jira.jboss.com/jira/browse/JBWS-1358). We need to remove this so any ordering issues can be corrected outside of the code. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3985264#3985264 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3985264

19 years, 4 months

1
0
0 / 0

Handling of unpacked wars

by Darran Lofthouse

The changes this weekend to AbstractWarDeployer to expand all wars stopped web services from being deployed. The JBossWS deployer is called first and creates an exploded war so that the web.xml can be modified. The recent changes the AbstractWarDeployer created a new exploded war and it was this that was used for deploying the web application without the modified web.xml. I understand the unpacking in AbstractWarDeployer is only temporary until Tomcat can use the VFS so I have added a check to see if JBossWS has already unpacked the war and if so use that instead of creating a new one. Regards, Darran Lofthouse.

19 years, 4 months

2
1
0 / 0

[Design of JBoss Web Services] - Re: JSR-181 Annotation Based UDDI Registration

by jgilbert

Kurt, How is the ESB leveraging jUddi? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3985080#3985080 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3985080

19 years, 4 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-dev November 2006