November 2007 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-1923) Stack CXF Release Criteria

by Thomas Diesler (JIRA)

Stack CXF Release Criteria -------------------------- Key: JBWS-1923 URL: http://jira.jboss.com/jira/browse/JBWS-1923 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Assigned To: Thomas Diesler Fix For: jbossws-2.1.0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBWS-1922) Stack Metro Release Criteria

by Thomas Diesler (JIRA)

Stack Metro Release Criteria ---------------------------- Key: JBWS-1922 URL: http://jira.jboss.com/jira/browse/JBWS-1922 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Assigned To: Heiko Braun -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBWS-1914) Distribution is not QAed against the JBoss AS 4.0.5 target container

by Richard Opalka (JIRA)

Distribution is not QAed against the JBoss AS 4.0.5 target container -------------------------------------------------------------------- Key: JBWS-1914 URL: http://jira.jboss.com/jira/browse/JBWS-1914 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: jbossws-2.0.2 Reporter: Richard Opalka Assigned To: Richard Opalka Fix For: jbossws-2.0.3 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (JBWS-1920) Pass J2EE-1.4 CTS for jaxr, jaxrpc, saaj, webservice

by Thomas Diesler (JIRA)

Pass J2EE-1.4 CTS for jaxr, jaxrpc, saaj, webservice ---------------------------------------------------- Key: JBWS-1920 URL: http://jira.jboss.com/jira/browse/JBWS-1920 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Components: jbossws-jaxws Reporter: Thomas Diesler Assigned To: Heiko Braun Fix For: jbossws-2.0.3 Run the J2EE-1.4 tests with jdk-1.5 against jboss-4.2.x -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBWS-1921) Pass JavaEE5 CTS for jaxr, jaxrpc, jaxws, jws, saaj, webservice, webservices12

by Thomas Diesler (JIRA)

Pass JavaEE5 CTS for jaxr, jaxrpc, jaxws, jws, saaj, webservice, webservices12 ------------------------------------------------------------------------------ Key: JBWS-1921 URL: http://jira.jboss.com/jira/browse/JBWS-1921 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Components: jbossws-jaxws Reporter: Thomas Diesler Assigned To: Thomas Diesler Fix For: jbossws-2.0.3 Run the JavaEE5 tests with jdk-1.5 against jboss-5.0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBWS-1860) Port JBWS-1833 - ConfigObserver was causing a memory leak to JBossWS1.2.1

by Magesh Kumar B (JIRA)

Port JBWS-1833 - ConfigObserver was causing a memory leak to JBossWS1.2.1 ------------------------------------------------------------------------- Key: JBWS-1860 URL: http://jira.jboss.com/jira/browse/JBWS-1860 Project: JBoss Web Services Issue Type: Support Patch Security Level: Public (Everyone can see) Affects Versions: jbossws-1.2.1 Reporter: Magesh Kumar B Assigned To: Magesh Kumar B Priority: Critical Port [JBWS-1833] - ConfigObserver was causing a memory leak to JBossWS1.2.1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 1 month

2
24
0 / 0

[JBoss JIRA] Created: (JBWS-1915) Nillable schema attribute is incorrectly generated for primitive types

by Richard Opalka (JIRA)

Nillable schema attribute is incorrectly generated for primitive types ---------------------------------------------------------------------- Key: JBWS-1915 URL: http://jira.jboss.com/jira/browse/JBWS-1915 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-jaxws Affects Versions: jbossws-2.0.2 Reporter: Richard Opalka Assigned To: Richard Opalka Fix For: jbossws-2.0.3 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1833) ConfigObserver was causing a memory leak

by Magesh Kumar B (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1833?page=all ] Magesh Kumar B updated JBWS-1833: --------------------------------- Security: Public (was: JBoss Internal) > ConfigObserver was causing a memory leak > ---------------------------------------- > > Key: JBWS-1833 > URL: http://jira.jboss.com/jira/browse/JBWS-1833 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: jbossws-1.2.1 > Environment: https://na1.salesforce.com/50030000003iZKa > Reporter: Heiko Braun > Assigned To: Heiko Braun > Priority: Critical > Fix For: jbossws-2.0.1.SP2 > > > ConfigObserver becomes a possible memory leak: > I think the leak is created through the Observable pattern that's used between EndpointMetaData(Subject) and CommonBindingProvider(Observer): > For each invocation we create a ServiceEndpointInvoker. Each invoker will be associated with a BindingProvider. This links the CommonBindingProvider to EndpointMetaData through the Observer pattern. > The EndpointMetaData is kept in the registry. IMO this is result in a memory leak. > I'll need to verify this assumption. But basically you could monitor a deployed EndpointMetaData#configObservable.countObservers(). If the above statement is true is will increase with every request that's being processed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-1848) Pass JavaEE5 CTS for jaxr, jaxrpc, jaxws, jws, saaj, webservice, webservices12

by Thomas Diesler (JIRA)

Pass JavaEE5 CTS for jaxr, jaxrpc, jaxws, jws, saaj, webservice, webservices12 ------------------------------------------------------------------------------ Key: JBWS-1848 URL: http://jira.jboss.com/jira/browse/JBWS-1848 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Components: jbossws-jaxws Reporter: Thomas Diesler Assigned To: Thomas Diesler Fix For: jbossws-2.0.1 Run the JavaEE5 tests with jdk-1.5 against jboss-5.0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JBWS-1799) Two ejb3s exposed as 2 different web services in the same ear file. Can't have same methods with different parameters..

by Sureshbabu Thyvalappil (JIRA)

Two ejb3s exposed as 2 different web services in the same ear file. Can't have same methods with different parameters.. ----------------------------------------------------------------------------------------------------------------------- Key: JBWS-1799 URL: http://jira.jboss.com/jira/browse/JBWS-1799 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jbossws-1.2.1 Environment: Debian etch. Reporter: Sureshbabu Thyvalappil Please look at the url for description. http://www.jboss.com/index.html?module=bb&op=viewtopic&t=116665 First ejb: @WebService(name="UserAccountServiceEndPoint", targetNamespace="namespace1", serviceName="UserAccountService1.0") @SOAPBinding(style=SOAPBinding.Style.DOCUMENT,use=SOAPBinding.Use.LITERAL) @Stateless @WebContext(transportGuarantee="NONE",contextRoot="/svc-useracctv1.0",urlPattern="/UserAccountService1.0") public class UserAccountService implements IUserAccountService { @WebMethod @TransactionAttribute(javax.ejb.TransactionAttributeType.SUPPORTS) public boolean authenticate(@WebParam(name="username") String aUsername) { boolean ret; ......... return ret; } } interface for 1st ejb: @Remote public interface IUserAccountService { public boolean authenticate(String aUsername); } second ejb: @WebService(name="UserAccountServiceExtEndPoint", targetNamespace="namespaceExt", serviceName="UserAccountServiceExt1.0") @SOAPBinding(style=SOAPBinding.Style.DOCUMENT,use=SOAPBinding.Use.LITERAL) @Stateless @WebContext(transportGuarantee="NONE",contextRoot="/svc-useracctv1.0",urlPattern="/UserAccountServiceExt1.0") public class UserAccountServiceExt implements IUserAccountServiceExt { @WebMethod @TransactionAttribute(javax.ejb.TransactionAttributeType.SUPPORTS) public boolean authenticate(@WebParam(name="username") String aUsername, @WebParam(name="password") String password) { boolean ret; ......... return ret; } } interface for 2nd ejb: @Remote public interface IUserAccountServiceExt { public boolean authenticate(String aUsername, String aPassword); } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 1 month

4
10
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues November 2007