June 2007 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Reopened: (JBWS-493) Add support for Compact Policy Expression

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-493?page=all ] Thomas Diesler reopened JBWS-493: --------------------------------- > Add support for Compact Policy Expression > ----------------------------------------- > > Key: JBWS-493 > URL: http://jira.jboss.com/jira/browse/JBWS-493 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: ws-policy > Reporter: Thomas Diesler > Assigned To: Stefano Maestri > Fix For: jbossws-2.1.1 > > > To express a policy in a more compact form while still using the XML Infoset, this > specification defines three constructs: an attribute to decorate an assertion, semantics > for recursively nested policy operators, and a policy reference/inclusion mechanism. > Each is described in the subsections below. -- 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

16 years, 10 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBWS-856) Complete WS-Policy implementation

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-856?page=all ] Thomas Diesler reopened JBWS-856: --------------------------------- > Complete WS-Policy implementation > --------------------------------- > > Key: JBWS-856 > URL: http://jira.jboss.com/jira/browse/JBWS-856 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: ws-policy > Reporter: Thomas Diesler > Assigned To: Stefano Maestri > Fix For: jbossws-2.1.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

16 years, 10 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBWS-494) Add support for Policy Intersection

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-494?page=all ] Thomas Diesler reopened JBWS-494: --------------------------------- > Add support for Policy Intersection > ----------------------------------- > > Key: JBWS-494 > URL: http://jira.jboss.com/jira/browse/JBWS-494 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: ws-policy > Reporter: Thomas Diesler > Assigned To: Stefano Maestri > Fix For: jbossws-2.1.1 > > > Policy intersection is useful when two or more parties express policy and want to limit > the policy alternatives to those that are mutually compatible. For example, when a > requester and a provider express requirements on a message exchange, intersection > identifies compatible policy alternatives (if any) included in both requester and provider > policies. Intersection is a commutative, associative function that takes two policies and > returns a policy. -- 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

16 years, 10 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBWS-492) Add support for Policy Identification

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-492?page=all ] Thomas Diesler reopened JBWS-492: --------------------------------- > Add support for Policy Identification > ------------------------------------- > > Key: JBWS-492 > URL: http://jira.jboss.com/jira/browse/JBWS-492 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: ws-policy > Reporter: Thomas Diesler > Assigned To: Stefano Maestri > Fix For: jbossws-2.1.1 > > > A policy expression may be assigned a namespace, indicated either using the > @TargetNamespace attribute of the wsp:Policy element or inherited from a containing > element (e.g., wsdl:definitions, xs:schema). If no namespace is specified by a > container or by @TargetNamespace of the wsp:Policy element, the namespace is "". > A policy expression can also itself be a Web resource, hence identifiable by a URI. To > allow policy expressions to be embedded in arbitrary containing elements, the @wsu:Id > attribute may be used to indicate a fragment ID. -- 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

16 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-1631) Add support for Service, Operation and Message Policy Subjects

by Alessio Soldano (JIRA)

Add support for Service, Operation and Message Policy Subjects -------------------------------------------------------------- Key: JBWS-1631 URL: http://jira.jboss.com/jira/browse/JBWS-1631 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: ws-policy Reporter: Alessio Soldano Assigned To: Alessio Soldano Implementation of WS-Policy (issue http://jira.jboss.org/jira/browse/JBWS-856 ) is going to consider policies attached to endpoint policy subjects only. Policy attached to service, operation and message subjects should not be ignored any more once this issue is solved. -- 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

16 years, 10 months

2
2
0 / 0

[JBoss JIRA] Reopened: (JBWS-1521) Full swa support for JAX-WS

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1521?page=all ] Thomas Diesler reopened JBWS-1521: ---------------------------------- > Full swa support for JAX-WS > --------------------------- > > Key: JBWS-1521 > URL: http://jira.jboss.com/jira/browse/JBWS-1521 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jbossws-jaxws > Reporter: Heiko Braun > 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

16 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-1663) wsconsume fails to resolve schmema

by Heiko Braun (JIRA)

wsconsume fails to resolve schmema ---------------------------------- Key: JBWS-1663 URL: http://jira.jboss.com/jira/browse/JBWS-1663 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jbossws-1.2.1 Reporter: Heiko Braun Assigned To: Heiko Braun Fix For: jbossws-2.0.1 [wsconsume] java.net.UnknownHostException: ws-i.org [wsconsume] at org.jboss.com.sun.tools.ws.processor.modeler.wsdl.WSDLModeler.buildModel(WSDLModeler. java:213) [wsconsume] at org.jboss.com.sun.tools.ws.processor.config.ModelInfo.buildModel(ModelInfo.java:88) [wsconsume] at org.jboss.com.sun.tools.ws.processor.Processor.runModeler(Processor.java:82) [wsconsume] at org.jboss.com.sun.tools.ws.wscompile.CompileTool.run(CompileTool.java:543) [wsconsume] at org.jboss.com.sun.tools.ws.util.ToolBase.run(ToolBase.java:57) [wsconsume] at org.jboss.ws.tools.jaxws.impl.WSContractConsumerImpl$1.run(WSContractConsumerImpl.jav a:163) -- 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

16 years, 10 months

3
4
0 / 0

[JBoss JIRA] Updated: (JBWS-1585) WSDLFilePublisher throws a java.security.AccessControlException: access denied

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1585?page=all ] Thomas Diesler updated JBWS-1585: --------------------------------- Fix Version/s: (was: jbossws-2.0.0) > WSDLFilePublisher throws a java.security.AccessControlException: access denied > ------------------------------------------------------------------------------- > > Key: JBWS-1585 > URL: http://jira.jboss.com/jira/browse/JBWS-1585 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-jaxws > Environment: jbossws-1.0.4.GA > Reporter: Roland Räz > Assigned To: Heiko Braun > > When the security manager is enabled the class org.jboss.ws.server.WSDLFilePublisher causes an AccessControlException because it uses the file constructor with the given url. > e.g. > java.security.AccessControlException: access denied > (java.io.FilePermission file:/var/opt/jboss4/jbossiv/current/temp/jboss/temp/jbossws/Sample181Service64187.wsdl delete) > Using an URI and the correct constructor resolves this issue: > ... > if (wsdlFile.startsWith(config.getServerTempDir().toURL().toExternalForm())) > { > URI uri = new URI(wsdlFile); > File file = new File(uri); > file.delete(); > } > ... -- 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

16 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1592) Investigate NPE in opMetaData.getQName() with WS-Security

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1592?page=all ] Thomas Diesler updated JBWS-1592: --------------------------------- Fix Version/s: (was: jbossws-2.0.0) > Investigate NPE in opMetaData.getQName() with WS-Security > --------------------------------------------------------- > > Key: JBWS-1592 > URL: http://jira.jboss.com/jira/browse/JBWS-1592 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: ws-security > Reporter: Jason T. Greene > Assigned To: Heiko Braun > > java.lang.NullPointerException > at org.jboss.ws.extensions.security.WSSecurityDispatcher.handleInbound(WSSecurityDispatcher.java:13 > 0) > at org.jboss.ws.extensions.security.jaxws.WSSecurityHandler.handleInboundSecurity(WSSecurityHandler > .java:59) > at org.jboss.ws.extensions.security.jaxws.WSSecurityHandlerServer.handleInbound(WSSecurityHandlerSe > rver.java:41) > at org.jboss.ws.core.jaxws.handler.GenericHandler.handleMessage(GenericHandler.java:55) > at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:276 > ) > at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleRequest(HandlerChainExecutor.java:112 > ) > at org.jboss.ws.core.jaxws.handler.HandlerDelegateJAXWS.callRequestHandlerChain(HandlerDelegateJAXW > S.java:65) > at org.jboss.ws.core.server.AbstractServiceEndpointInvoker.callRequestHandlerChain(AbstractServiceE > Client: > sdlURL = new URL("http://chaponniere-linux:8080/procedures-beans/PstProcedureManager?wsdl"); > URL securityURL = new File("jboss-wsse-client.xml").toURL(); > QName serviceName = new QName("http://procedure.procedures/", "PstProcedureManagerService"); > Service service = Service.create(wsdlURL, serviceName); > ((ServiceExt)service).setSecurityConfig(securityURL.toExternalForm()); > > PstProcedureManager port = (PstProcedureManager)service.getPort(PstProcedureManager.class); > //Hello port = (Hello)service.getPort(Hello.class); > ((StubExt)port).setConfigName("Standard WSSecurity Client"); > > Map<String, Object> reqContext = ((BindingProvider)port).getRequestContext(); > //reqContext.put(BindingProvider.ENDPOINT_ADDRESS_PROPERTY, "http://localhost:8080/jaxws-samples-wssecurity-encrypt"); > reqContext.put(BindingProvider.ENDPOINT_ADDRESS_PROPERTY, "http://chaponniere-linux:8080/procedures-beans/PstProcedureManager?wsdl"); > > String procedureNumber = port.getProcedure(1).getNumber(); > System.out.println(procedureNumber); > Server: > @WebService > @EndpointConfig(configName = "Standard WSSecurity Endpoint") > public class PstProcedureManager implements PstProcedureInterface { > @PersistenceContext > protected EntityManager em; > > @WebMethod > public PstProcedureBean getProcedure(int pId) { > Collection procedureCol = > em.createQuery("from PstProcedureBean procedureBean where procedureBean.id = :id") > .setParameter ("id", pId) > .getResultList(); > > return (PstProcedureBean)procedureCol.iterator().next(); > } > } > -- 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

16 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1583) Cannot use URL-base wsdl locatiion

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1583?page=all ] Thomas Diesler updated JBWS-1583: --------------------------------- Fix Version/s: (was: jbossws-2.0.0) > Cannot use URL-base wsdl locatiion > ---------------------------------- > > Key: JBWS-1583 > URL: http://jira.jboss.com/jira/browse/JBWS-1583 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-jaxws > Environment: JBoss 4.0.5.GA, JBoss WS 1.2 SP1 > Reporter: Oskar Carlstedt > Assigned To: Heiko Braun > > Jboss is complaining about wrong schemalocation and error in wsdl when setting the schemaLocation annotation to an "http://..."-address. Using WEB-INF/wsdl/myservicec.wsdl works fine. > //Oskar -- 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

16 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues June 2007