July 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (REMJMX-12) Allow for protocol versions to be excluded client and server side

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/REMJMX-12?page=com.atlassian.jira.plugin.... ] Darran Lofthouse commented on REMJMX-12: ---------------------------------------- For the server side this will require the value to be used in two locations: - 1 - To exclude a version from the list of offered versions. 2 - To ensure a client is not requesting an excluded version i.e. a version could be excluded if a vulnerability is identified within it. > Allow for protocol versions to be excluded client and server side > ----------------------------------------------------------------- > > Key: REMJMX-12 > URL: https://issues.jboss.org/browse/REMJMX-12 > Project: Remoting JMX > Issue Type: Task > Components: Connection > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 1.0.4.CR1 > > > Once we start supporting multiple versions of the protocols we should also allow version to be excluded client and server side. > This will mean if a version is identified as being problematic is can be excluded to force the use of a previous version. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-858) Arquillian Extension Byteman 1.0.0.Alpha2

by Jesper Pedersen (JIRA)

Jesper Pedersen created JBJCA-858: ------------------------------------- Summary: Arquillian Extension Byteman 1.0.0.Alpha2 Key: JBJCA-858 URL: https://issues.jboss.org/browse/JBJCA-858 Project: IronJacamar Issue Type: Component Upgrade Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.1.0.Beta2 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-860) ShrinkWrap 1.0.1

by Jesper Pedersen (JIRA)

Jesper Pedersen created JBJCA-860: ------------------------------------- Summary: ShrinkWrap 1.0.1 Key: JBJCA-860 URL: https://issues.jboss.org/browse/JBJCA-860 Project: IronJacamar Issue Type: Component Upgrade Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.1.0.Beta2 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-5188) WS-Addressing Action on response is not being returned as specified in the WSDL

by Jakob Munih (JIRA)

Jakob Munih created AS7-5188: -------------------------------- Summary: WS-Addressing Action on response is not being returned as specified in the WSDL Key: AS7-5188 URL: https://issues.jboss.org/browse/AS7-5188 Project: Application Server 7 Issue Type: Bug Components: Web Services Affects Versions: 7.1.2.Final (EAP) Environment: AS7, SOA 5.2 Reporter: Jakob Munih Assignee: Alessio Soldano According to https://issues.apache.org/jira/browse/CXF-2629 its should be implemented that a WS method call can be overridden by the wsaw:Action or better by the @Action annotation. With jbossWS in AS7 as in SOA5.2 this is not honored. As show from the soa52.txt log file, having two methods with the same inbound input but different wsaw:Action the same method is called every time. In the occasion where the right return type is triggered the outbound body rightfully contains the MCCI_IN000002UV01 object representation. With the wsaw:Action referring the the other method (the same method is called as before) an empty body is replied. AS7 is a little bit more clever. It replies in the second occasion throws an SoapFault that the method not supported. Seem that CXF try to handle the situation, but there are some problems in the INVOKE phrase between jboss-ws and the deployed endpoint call. The web service is created with maven org.apache.cxf:cxf-codegen-plugin that correctly adds @Action from the interface created from the wsdl. And the implementation has @Addressing(required = true, enabled = true) annotation and sending and request without the addressing headers correctly refuses the inbound message. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
3
0 / 0

[JBoss JIRA] Created: (AS7-1375) UnsupportedDataTypeException sending email

by Tomáš Remeš (JIRA)

UnsupportedDataTypeException sending email ------------------------------------------- Key: AS7-1375 URL: https://issues.jboss.org/browse/AS7-1375 Project: Application Server 7 Issue Type: Bug Environment: jdk-u26, jboss-as-7.1.0.Alpha1-SNAPSHOT(07/22/2011) Reporter: Tomáš Remeš Seam 3 send mail example fails on: javax.activation.UnsupportedDataTypeException: no object DCH for MIME type multipart/mixed; boundary="----=_Part_1_340486764.1311336438303" at javax.activation.ObjectDataContentHandler.writeTo(DataHandler.java:905) [activation-1.1.1.jar:1.1.1] at javax.activation.DataHandler.writeTo(DataHandler.java:330) [activation-1.1.1.jar:1.1.1] at javax.mail.internet.MimeBodyPart.writeTo(MimeBodyPart.java:1476) [mail-1.4.4.jar:1.4.4] at javax.mail.internet.MimeMessage.writeTo(MimeMessage.java:1772) [mail-1.4.4.jar:1.4.4] at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:1099) [mail-1.4.4.jar:1.4.4] ... 42 more -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

13
32
0 / 0

[JBoss JIRA] (AS7-5187) Java Activation API Module prevents use of Java Mail API in JBoss OSGI

by Ed Roberts (JIRA)

Ed Roberts created AS7-5187: ------------------------------- Summary: Java Activation API Module prevents use of Java Mail API in JBoss OSGI Key: AS7-5187 URL: https://issues.jboss.org/browse/AS7-5187 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.1.2.Final (EAP), 7.1.1.Final Environment: jdk-u32, jboss-as-7.1.1.Final, Windows XP Reporter: Ed Roberts The module.xml content for javax.activation.api prevents the ability to expose it and the javax.mail.api modules to the JBoss OSGi container. Inside the module.xml there is a dependency declaration on javax.mail and an embedded import statement that includes everything beneath META-INF. This statement is including the Manifest.mf which causes the OSGi container to believe the activation bundle is the mail bundle. Adding additional exclude or exclude-set statements does not alter the include in any way. Some documentation explaining the relation between these sibling elements within the module schema would help, and inclusion of the module schema in the jboss as distribution also. 2012-07-17 10:11:47,182 ERROR [org.eclipse.gemini.blueprint.extender.internal.activator.ContextLoaderListener](EclipseGeminiBlueprintExtenderThread-5) Application context refresh failed (OsgiBundleXmlApplicationContext(bundle=my-svc, config=osgibundle:/META-INF/spring/*.xml)): org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'myService': Invocation of init method failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'myBean' defined in URL [bundle://my.svc-44-0-0/META-INF/spring/osgi.xml]: Instantiation of bean failed; nested exception is java.lang.NoClassDefFoundError: javax/mail/MessagingException at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1455) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:519) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456) at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:294) at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:225) at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:291) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:193) at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:567) at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:913) at org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext.access$1600(AbstractDelegatedExecutionApplicationContext.java:60) at org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext$4.run(AbstractDelegatedExecutionApplicationContext.java:325) at org.eclipse.gemini.blueprint.util.internal.PrivilegedUtils.executeWithCustomTCCL(PrivilegedUtils.java:85) at org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext.completeRefresh(AbstractDelegatedExecutionApplicationContext.java:290) at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$CompleteRefreshTask.run(DependencyWaiterApplicationContextExecutor.java:137) at java.lang.Thread.run(Thread.java:662) Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'myBean' defined in URL [bundle://my.svc-44-0-0/META-INF/spring/osgi.xml]: Instantiation of bean failed; nested exception is java.lang.NoClassDefFoundError: javax/mail/MessagingException at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:997) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:943) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:485) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456) at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:294) at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:225) at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:291) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:193) at org.eclipse.gemini.blueprint.service.exporter.support.OsgiServiceFactoryBean.afterPropertiesSet(OsgiServiceFactoryBean.java:198) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1514) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1452) ... 14 more Caused by: java.lang.NoClassDefFoundError: javax/mail/MessagingException at java.lang.Class.getDeclaredConstructors0(Native Method) at java.lang.Class.privateGetDeclaredConstructors(Class.java:2389) at java.lang.Class.getConstructor0(Class.java:2699) at java.lang.Class.getDeclaredConstructor(Class.java:1985) at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:67) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:990) ... 24 more Caused by: java.lang.ClassNotFoundException: javax.mail.MessagingException from [Module "deployment.my-svc:1.0.0.SNAPSHOT" from Service Module Loader] at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468) at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456) at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:423) at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120) ... 30 more -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-5097) cli: show more detailed info when connection failed

by Alexey Loubyansky (JIRA)

Alexey Loubyansky created AS7-5097: -------------------------------------- Summary: cli: show more detailed info when connection failed Key: AS7-5097 URL: https://issues.jboss.org/browse/AS7-5097 Project: Application Server 7 Issue Type: Task Components: CLI Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: 7.2.0.Alpha1 Currently, when the connection failed for some reason (other than authentication or ssl), only a general message is printed. It'd be more useful to include the actual error message reported by the remoting. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
1
0 / 0

[JBoss JIRA] (AS7-5096) cli: add headers to batches

by Alexey Loubyansky (JIRA)

Alexey Loubyansky created AS7-5096: -------------------------------------- Summary: cli: add headers to batches Key: AS7-5096 URL: https://issues.jboss.org/browse/AS7-5096 Project: Application Server 7 Issue Type: Task Components: CLI Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: 7.2.0.Alpha1 Currently, batches that translate into composite operations are missing a way to specify rollout plans and other headers. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
1
0 / 0

[JBoss JIRA] (AS7-5078) if-else control flow for cli

by Alexey Loubyansky (JIRA)

Alexey Loubyansky created AS7-5078: -------------------------------------- Summary: if-else control flow for cli Key: AS7-5078 URL: https://issues.jboss.org/browse/AS7-5078 Project: Application Server 7 Issue Type: Task Components: CLI Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: 7.2.0.Alpha1 It'd be useful to be able to implement if-else control flow in the cli. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
1
0 / 0

[JBoss JIRA] (AS7-3281) Add a "force" attribute to CLI add operations to allow existing resources to be transparently recreated

by Robert Reimann (JIRA)

Robert Reimann created AS7-3281: ----------------------------------- Summary: Add a "force" attribute to CLI add operations to allow existing resources to be transparently recreated Key: AS7-3281 URL: https://issues.jboss.org/browse/AS7-3281 Project: Application Server 7 Issue Type: Feature Request Components: CLI Affects Versions: 7.1.0.CR1b Reporter: Robert Reimann Assignee: Alexey Loubyansky To allow for repeatable CLI script executions (e.g. in case of a missconfiguration like wrong IP or DB-Password provided) conditional logic is required to prevent "Duplicate resource" failures. These logic is typically contained in a wrapper script (shell script or another scripting language). Pseudocode: {code} exists = test if the resource to be (re-)added already exists if (exists) remove resource add resource {code} Adding a "force" or "override" attribute to the add operation (which recreates the resources transparently if necessary) would remove the need for conditional logic and additional wrapper scripts. A simple example, assuming that the logger to be added already exists: {code} /subsystem=logging/logger=com.arjuna:add(level=TRACE, force=true) {code} In such a case the existing logger should be removed and recreated with the new properties provided. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2012