October 2007 - jbossws-dev - Jboss List Archives

[Design of JBoss Web Services] - [Productivity] Level 0 - WS Culture

by alessio.soldano＠jboss.com

This thread is about the first level of productivity efforts we're thinking about for jbossws. Please refer to this http://www.jboss.com/index.html?module=bb&op=viewtopic&t=121127 for a topic introduction. Every technology has its own learning curve. Understanding webservices might be not so easy at first because of the number and complexity of all the specification involved. Moreover, the world wide web contains lots of tutorials, guides, walk-through concerning webservice development, but most of them are either hard to understand, obsolete or out-of-date, referring proprietary/non-standard technologies, etc. This is most likely going to mislead and confuse the readers. A clear guide providing the right directions for a correct learning path may help customers acquire the knowledge they really need without waisting a lot of time. This: - increases the user satisfaction - gives us customers that really know what webservices are about and use them according to the aims they are meant to be used for - finally allows customers to easily proceed one step ahead and leverage our advanced features (related to the following levels) for their business, instead of struggling with beginners' issues because of their poor knowledge. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4095120#4095120 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4095120

17 years, 3 months

1
0
0 / 0

Re: [jboss-dev] metadata not attached to DeploymentUnit

by Thomas Diesler

Yes, JBossWebMetaData always used to be there. Now I only have WebMetaData attached if there is no jboss-web.xml. On Fri, 2007-10-12 at 15:32 +0200, Carlo de Wolf wrote: > This might be because the JBossWebMetaData isn't specified as an > optional input for that deployer. Which deployer are you talking about? > > Carlo > > On Fri, 2007-10-12 at 14:41 +0200, Thomas Diesler wrote: > > Hi Scott, > > > > we used to be able to detect a webapp deployment like this. Later, we > > inspect the meta data for WS relevant servlet classes. > > > > After the recent change to the new metadata model, the attachment is > > missing. Is this work in progress (i.e. will the attachment be there > > again) or should we do things differently? > > > > public boolean isWebServiceDeployment(DeploymentUnit unit) > > { > > if (unit.getAttachment(JBossWebMetaData.class) == null) > > return false; > > > > return true; > > } > > > > cheers > > -thomas > > > > _______________________________________________ > jboss-development mailing list > jboss-development(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-development -- xxxxxxxxxxxxxxxxxxxxxxxxxxxx Thomas Diesler Web Service Lead JBoss, a division of Red Hat xxxxxxxxxxxxxxxxxxxxxxxxxxxx

17 years, 3 months

2
2
0 / 0

[Design of JBoss Web Services] - Re: Thoughts about productivity

by alessio.soldano＠jboss.com

In particular concerning the samples, the strategy I'm think about is to provide customers with some real world usecases. Each of them is going to have its own scenario. Then we'll propose you reliable implementations leveraging the most suitable jbossws features and discussing the choices we take for the key points of each usecase. As said, soon you'll have the opportunity to choose the usecases you think are the most interesting; however if everybody want to start describing its own enterprise usecase/scenario... we'll be happy to consider that too. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4094685#4094685 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4094685

17 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - Thoughts about productivity

by alessio.soldano＠jboss.com

Thanks to years of work the JBossWS project is mature enought to compare with the major webservice stacks all around. Constant development is required to implement WS-* standards, to support the integration within the JBoss enterprise products and so on. Moreover webservices should play a major part in the Service Oriented Architecture we're trasforming the customers' business to. For this reasons, apart from continuosly developing and enhancing our implementation and the integration layers we actually provide, it's time to reflect upon the real JBossWS users' needings, in terms of their productivity. Are they making the most of our project? what they miss in order to do that? Considering the whole webservice technology is not so trivial, our efforts should go in the direction of helping users through a product that easily address their issues, saving their time. We are required to supply customers with reliable solutions that can nevertheless be easily achieved and finally brought to a production environment. In short: what should we do to make the whole ws experience easier? I'm currently thinking about how this is going to be obtained; for sure, considering our target, we are going to base our productivity strategy on the real world lifecycle of a webservice application. This way we should cope with most of the issues ws users have to deal with, from the technology choices before the implementation, to the testing and all the issues concerning the productization of a service / service client. This means that we plan to organize our productivity efforts into five level ("WS Culture", "Start from scratch", "Development", "Transition / staging" and "Production"). Each of them is going to require different actions, including documentation improvement, creation of new tools, more and better samples and most probably some IDE integration efforts. I'll start one thread on this forum for each level, explaining what we think could be useful to do. Since there is going to be some days between this brainstorming phase and the actual definition of work, every comment, thought, etc from the community and from related projects' team on every thread could be useful. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4094684#4094684 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4094684

17 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: metadata integration

by scott.stark＠jboss.org

Regarding your question in the JBWS-1842 issue, yes, we want webservices to consume the spec descriptor based org.jboss.javaee.metadata.spec.ServiceReferenceMetaData, but we can't then have the metadata project depend on the jbossws-spi. Only the jbossas integration code can have this dependency. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4094656#4094656 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4094656

17 years, 3 months

1
0
0 / 0

metadata not attached to DeploymentUnit

by Thomas Diesler

Hi Scott, we used to be able to detect a webapp deployment like this. Later, we inspect the meta data for WS relevant servlet classes. After the recent change to the new metadata model, the attachment is missing. Is this work in progress (i.e. will the attachment be there again) or should we do things differently? public boolean isWebServiceDeployment(DeploymentUnit unit) { if (unit.getAttachment(JBossWebMetaData.class) == null) return false; return true; } cheers -thomas -- xxxxxxxxxxxxxxxxxxxxxxxxxxxx Thomas Diesler Web Service Lead JBoss, a division of Red Hat xxxxxxxxxxxxxxxxxxxxxxxxxxxx

17 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - Forcing JAXB Schema Generator To Preserve Java Object Inheri

by richard_opalka

Hi Folks, I've found that our 'WSDL schema section' generation process is in method JAXBWSDLGenerator.processTypes() where we call JAXBRI.generateSchema() method. This JAXB based schema generation doesn't preserve the object inheritance hierarchy in generated schema. So my question is: Is there a way to force JAXB schema generator to preserve object inheritance hierarchy in generated schema? Richard View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4094403#4094403 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4094403

17 years, 3 months

1
0
0 / 0

jbossws in Branch_4_2

by Thomas Diesler

Hi Dimitris, could you please comment on http://jira.jboss.org/jira/browse/JBAS-4811 cheers -thoams -- xxxxxxxxxxxxxxxxxxxxxxxxxxxx Thomas Diesler Web Service Lead JBoss, a division of Red Hat xxxxxxxxxxxxxxxxxxxxxxxxxxxx

17 years, 3 months

1
0
0 / 0

(no subject)

by ropalka＠redhat.com

Hi Folks, each time when you will add a new test that uses EJB3 annotations to the SVN repository, please specify this test also in test-excludes-jboss40.no.ejb3.txt file. Thx, Richard

17 years, 3 months

2
1
0 / 0

[Design of JBoss Web Services] - Re: Failed to create a new SAX parser

by richard_opalka

No, I haven't seen it yet. Richard View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4094123#4094123 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4094123

17 years, 3 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 October 2007