November 2007 - jbossws-dev - Jboss List Archives

[Design of JBoss Web Services] - Re: Deployment.types not propagated

by thomas.diesler＠jboss.com

With the current API it seems the attachments that I get from org.jboss.deployers.client.spi.Deployment.getPredeterminedManagedObjects() are read only. Please show me the correct usage of a client using attachments View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4103197#4103197 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4103197

17 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Using the namespace in @WebFault

by veskok

Done, Jira issue JBWS-1904 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4102913#4102913 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4102913

17 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Using the namespace in @WebFault

by thomas.diesler＠jboss.com

Yes, please create a jira issue for that and cross reference it with this forum post. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4102894#4102894 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4102894

17 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - Using the namespace in @WebFault

by veskok

It seems that even the latest version of 2.0.1 I downloaded from SVN still is not using the namespace information in the WebFault annotation to define the namespace of the XmlType that is put into the schema part of the WSDL for a fault. The service namespace is used instead. By looking at the code it seems this is not a bug but rather is done on purpose. However, there are cases when one will need to explicitly define the namespace through an annotation. The solution would be: 1. To change the current behavior. This is easy, I did it by just adding a line of code in org.jboss.metadata.builder.jaxws.JAXWSMetaDataBuilder. However, I can't be sure this will not break some use cases I don't see at the moment. 2. Start using the namespace in @XmlType which is totally ignored currently. This would be again one or two lines of code in the same place. I can submit the code I changed to the email of the person that can take care of the problem if you think I'm right. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4102893#4102893 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4102893

17 years, 2 months

1
0
0 / 0

conf call minutes

by Thomas Diesler

Hi Folks, here the conf call minutes from 08-Nov-2007 Thomas: - jbossws-2.0.2.GA is delayed because of various AS50 issues - we give it a little more time and work on the AS50 issues Heiko: - jbossws-2.0.2 passes the TCK14 - worked on customer patches and tools issues - fixed the memory leak in DOMUtils Richard: - merged ws-rm to trunk and created a wiki page - is on holiday next week Allesio: - is in seatle and did not attend -- xxxxxxxxxxxxxxxxxxxxxxxxxxxx Thomas Diesler Web Service Lead JBoss, a division of Red Hat xxxxxxxxxxxxxxxxxxxxxxxxxxxx

17 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Deployment.types not propagated

by adrian＠jboss.org

You're doing it wrong. :-) The types shouldn't even be on the deployment (I agreed this with Scott before) but it obviously hasn't been removed from the api yet. :-) The types should be part of the ManagedObject stuff for the profile service such that the console can sort the deployments into categories. Instead, you should add a marker into the attachments of the deployment. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4102881#4102881 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4102881

17 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - Deployment.types not propagated

by thomas.diesler＠jboss.com

| [tdiesler@tddell trunk]$ ant -Dtest=org.jboss.test.ws.jaxws.jbws1762.packaged_jar_ejb3.Iteration1TestCase one-test | | Caused by: java.lang.IllegalStateException: Endpoint already registered: jboss.ws:context=jaxws-jbws1762-packaged,endpoint=EJB3Bean | at org.jboss.wsf.framework.management.DefaultEndpointRegistry.register(DefaultEndpointRegistry.java:89) | at org.jboss.wsf.framework.management.ManagedEndpointRegistry.register(ManagedEndpointRegistry.java:59) | at org.jboss.wsf.framework.deployment.EndpointRegistryDeploymentAspect.create(EndpointRegistryDeploymentAspect.java:46) | at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:115) | at org.jboss.wsf.container.jboss50.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:95) | at org.jboss.wsf.container.jboss50.AbstractWebServiceDeployer.deploy(AbstractWebServiceDeployer.java:63) | The WebAppDeploymentAspect adds a type string like this | org.jboss.deployers.client.spi.Deployment deployment = createDeployment(warURL); | | // Mark the deployment as generated web app | // so the JSE deployer hook can ignore it | Set<String> types = deployment.getTypes(); | if (types == null) | { | types = new HashSet<String>(); | deployment.setTypes(types); | } | types.add(WebAppDesciptorModifier.PROPERTY_GENERATED_WEBAPP); | During deployment of the above using this code | public boolean isWebServiceDeployment(DeploymentUnit unit) | { | JBossWebMetaData webMetaData = unit.getAttachment(JBossWebMetaData.class); | boolean isGenerated = unit.getTypes().contains(WebAppDesciptorModifier.PROPERTY_GENERATED_WEBAPP); | return isGenerated == false && webMetaData != null; | } | isGenerated is always false. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4102859#4102859 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4102859

17 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: [Productivity] Level 4 - Production

by maeste

Hi all, Very very busy in last weeks, I found time just now to give my two cents. What I would jbossws provide at this level is a sophisticated log system, giving me the opportunity to understand who is using my service and how. My idea is to provide a log (and docs to explain how to enable/disable or set a dedicated file and so on) awstats compatible. I know awstats is designed for web apps, but I think you (we if I get time to contribute) can think how to provide compatible logs, because it is grat for immediate statistic and graphs. In a SOA world we have to consider stats and graphs for the management have to consider service level since service is becoming the access to the businness (as web have been until now). Of course this kind of feature and all which could be thought at this level have to consider not only jbossws services but probably more general SOA services (I'm thinking to ESB too). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4102569#4102569 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4102569

17 years, 2 months

1
0
0 / 0

NPE in ProxyFactoryHelper

by Thomas Diesler

Hi Carlo, could you please have a look at http://jira.jboss.com/jira/browse/JBAS-4949 This is currently blocking most of our CTS tests. cheers -thomas -- xxxxxxxxxxxxxxxxxxxxxxxxxxxx Thomas Diesler Web Service Lead JBoss, a division of Red Hat xxxxxxxxxxxxxxxxxxxxxxxxxxxx

17 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: WS-RM Initial Implementation Merged to Trunk

by richard.opalka＠jboss.com

First draft: http://jbws.dyndns.org/mediawiki/index.php?title=WS_Reliable_Messaging Richard View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4102269#4102269 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4102269

17 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-dev November 2007