[JBoss JIRA] (AS7-5664) Upgrade wss4j to 1.6.7
by Paul Gier (JIRA)
Paul Gier created AS7-5664:
------------------------------
Summary: Upgrade wss4j to 1.6.7
Key: AS7-5664
URL: https://issues.jboss.org/browse/AS7-5664
Project: Application Server 7
Issue Type: Component Upgrade
Components: Web Services
Reporter: Paul Gier
Assignee: Alessio Soldano
Fix For: 7.2.0.Alpha1, 7.1.4.Final (EAP)
Apache cxf 2.4.9 has a compile time dependency on org.apache.security.ws:wss4j 1.6.7. Since Apache cxf 2.4.9 is already included in AS 7, it seems to make sense to upgrade wss4j to avoid possible problems with cxf 2.4.9.
The webservices testsuite has been verified to work with the wss4j upgrade.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] (AS7-4557) Javadoc tool fails on certain AS dependencies' sources.
by Ondrej Zizka (JIRA)
[ https://issues.jboss.org/browse/AS7-4557?page=com.atlassian.jira.plugin.s... ]
Ondrej Zizka updated AS7-4557:
------------------------------
Priority: Minor (was: Major)
As a workaround, the affected jars are excluded.
Changing to Minor.
> Javadoc tool fails on certain AS dependencies' sources.
> -------------------------------------------------------
>
> Key: AS7-4557
> URL: https://issues.jboss.org/browse/AS7-4557
> Project: Application Server 7
> Issue Type: Bug
> Components: Build System
> Reporter: Ondrej Zizka
> Priority: Minor
>
> Including certain AS 7 deps sources into the aggregated javadoc (AS7-582) causes it to throw the exception below.
> Some of these are:
> {code:xml}
> <include>org.infinispan:infinispan-core</include>
> <include>org.jboss.as:jboss-as-controller-client</include>
> <include>org.jboss:jboss-dmr</include>
> {code}
> I'm not sure whether we have someone specialized on JDK tools.
> It's this known bug: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6442982
> Also discussed here: http://stackoverflow.com/questions/44853/why-am-i-getting-a-classcastexce...
> Workaround: Find what annotation causes that, and include it in JavaDoc's classpath.
> {code}
> [ERROR] java.lang.ClassCastException: com.sun.tools.javadoc.ClassDocImpl cannot be cast to com.sun.javadoc.AnnotationTypeDoc
> [ERROR] at com.sun.tools.javadoc.AnnotationDescImpl.annotationType(AnnotationDescImpl.java:46)
> [ERROR] at com.sun.tools.doclets.internal.toolkit.util.Util.isDeprecated(Util.java:811)
> [ERROR] at com.sun.tools.doclets.formats.html.ClassWriterImpl.writeClassDeprecationInfo(ClassWriterImpl.java:242)
> [ERROR] at com.sun.tools.doclets.internal.toolkit.builders.ClassBuilder.buildDeprecationInfo(ClassBuilder.java:229)
> [ERROR] at sun.reflect.GeneratedMethodAccessor17.invoke(Unknown Source)
> [ERROR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> [ERROR] at java.lang.reflect.Method.invoke(Method.java:597)
> [ERROR] at com.sun.tools.doclets.internal.toolkit.builders.ClassBuilder.invokeMethod(ClassBuilder.java:101)
> [ERROR] at com.sun.tools.doclets.internal.toolkit.builders.AbstractBuilder.build(AbstractBuilder.java:90)
> [ERROR] at com.sun.tools.doclets.internal.toolkit.builders.ClassBuilder.buildClassDoc(ClassBuilder.java:124)
> [ERROR] at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source)
> [ERROR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> [ERROR] at java.lang.reflect.Method.invoke(Method.java:597)
> [ERROR] at com.sun.tools.doclets.internal.toolkit.builders.ClassBuilder.invokeMethod(ClassBuilder.java:101)
> [ERROR] at com.sun.tools.doclets.internal.toolkit.builders.AbstractBuilder.build(AbstractBuilder.java:90)
> [ERROR] at com.sun.tools.doclets.internal.toolkit.builders.ClassBuilder.build(ClassBuilder.java:108)
> [ERROR] at com.sun.tools.doclets.formats.html.HtmlDoclet.generateClassFiles(HtmlDoclet.java:155)
> [ERROR] at com.sun.tools.doclets.internal.toolkit.AbstractDoclet.generateClassFiles(AbstractDoclet.java:164)
> [ERROR] at com.sun.tools.doclets.internal.toolkit.AbstractDoclet.startGeneration(AbstractDoclet.java:106)
> [ERROR] at com.sun.tools.doclets.internal.toolkit.AbstractDoclet.start(AbstractDoclet.java:64)
> [ERROR] at com.sun.tools.doclets.formats.html.HtmlDoclet.start(HtmlDoclet.java:42)
> [ERROR] at com.sun.tools.doclets.standard.Standard.start(Standard.java:23)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] (AS7-5717) module command fails inside a cli deployment archive
by Stan Silvert (JIRA)
Stan Silvert created AS7-5717:
---------------------------------
Summary: module command fails inside a cli deployment archive
Key: AS7-5717
URL: https://issues.jboss.org/browse/AS7-5717
Project: Application Server 7
Issue Type: Feature Request
Components: CLI
Affects Versions: 7.2.0.Alpha1
Reporter: Stan Silvert
Assignee: Stan Silvert
Create a CLI deployment archive containing a script. If the script contains a module command then it will fail because the module command does not set the current directory to the root of the archive.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] (AS7-5731) Add equivalent @WebContext for JAX-RS?
by Fernando Rubbo (JIRA)
Fernando Rubbo created AS7-5731:
-----------------------------------
Summary: Add equivalent @WebContext for JAX-RS?
Key: AS7-5731
URL: https://issues.jboss.org/browse/AS7-5731
Project: Application Server 7
Issue Type: Feature Request
Reporter: Fernando Rubbo
Currently, in our application we use @WebContext to set a different contextRoot for JAX-WS. For example:
@Stateless
@SecurityDomain("test2")
@WebService(name = "HelloSoap", portName = "HelloSoapPort", serviceName = "HelloSoap", targetNamespace = "http://com.test")
@WebContext(contextRoot = "/ws", urlPattern = "/HelloSoap", secureWSDLAccess = false, authMethod = "BASIC", transportGuarantee = "NONE")
public class HelloSoap { ... }
We would like to have an equivalent annotation for JAX-RS? It is required whenever a web app uses FORM_AUTH and there exists web services (JAX-WS and JAX-RS), inside of the same package, using as BASIC_AUTH.
Thankyou in advance,
Fernando Rubbo
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] (AS7-5744) JRE logging.properties file in a jar fails the deployment of an application
by Francois MESSIAEN (JIRA)
Francois MESSIAEN created AS7-5744:
--------------------------------------
Summary: JRE logging.properties file in a jar fails the deployment of an application
Key: AS7-5744
URL: https://issues.jboss.org/browse/AS7-5744
Project: Application Server 7
Issue Type: Bug
Components: EE, Logging
Affects Versions: 7.1.3.Final (EAP)
Environment: Windows 7 pro
JBoss 7.1.3
Reporter: Francois MESSIAEN
Assignee: David Lloyd
If a logging.properties file, as described in the java.util.logging.LogManager, is in a jar file of the ear, the application fails to be deployed. An Exception is thrown:
{noformat}
11:38:03,842 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC00001: Failed to start service jboss.deployment.unit."fullear.ear".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."fullear.ear".POST_MODULE: JBAS018733: N'a pas pu traiter la phase POST_MODULE de deployment "fullear.ear"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:123) [jboss-as-server-7.1.3.Final.jar:7.1.3.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_07]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_07]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_07]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011555: N'a pas pu configurer la connexion par le fichier de configuration 'logging.properties'
at org.jboss.as.logging.LoggingConfigurationProcessor.deploy(LoggingConfigurationProcessor.java:125)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:116) [jboss-as-server-7.1.3.Final.jar:7.1.3.Final]
... 5 more
Caused by: java.lang.IllegalArgumentException: className is null
at org.jboss.logmanager.config.AbstractPropertyConfiguration.<init>(AbstractPropertyConfiguration.java:52) [jboss-logmanager-1.3.2.Final.jar:1.3.2.Final]
at org.jboss.logmanager.config.HandlerConfigurationImpl.<init>(HandlerConfigurationImpl.java:54) [jboss-logmanager-1.3.2.Final.jar:1.3.2.Final]
at org.jboss.logmanager.config.LogContextConfigurationImpl.addHandlerConfiguration(LogContextConfigurationImpl.java:138) [jboss-logmanager-1.3.2.Final.jar:1.3.2.Final]
at org.jboss.logmanager.PropertyConfigurator.configureHandler(PropertyConfigurator.java:477) [jboss-logmanager-1.3.2.Final.jar:1.3.2.Final]
at org.jboss.logmanager.PropertyConfigurator.configure(PropertyConfigurator.java:379) [jboss-logmanager-1.3.2.Final.jar:1.3.2.Final]
at org.jboss.logmanager.PropertyConfigurator.configure(PropertyConfigurator.java:92) [jboss-logmanager-1.3.2.Final.jar:1.3.2.Final]
at org.jboss.as.logging.LoggingConfigurationProcessor.deploy(LoggingConfigurationProcessor.java:122)
... 6 more
11:38:03,845 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 1) JBAS014774: Rapport de statut de service
JBAS014777: Services qui n'ont pas pu démarrer : service jboss.deployment.unit."fullear.ear".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."fullear.ear".POST_MODULE: JBAS018733: N'a pas pu traiter la phase POST_MODULE de deployment "fullear.ear"
{noformat}
The content of the fullear.ear I use for this test is:
* lib
** myejbClient.jar
* META-INF
** application.xml
** jboss-app.xml
** jboss-deployment-structure.xml
** jboss-ejb-client.xml
** management-trackfolder-hornetq-jms.xml
** MANIFEST.MF
* myejb.jar
* web.war
I put the logging.properties files in myejbclient.jar file. The content of that jar file is :
* org
** mapp
*** ejb
**** logging.properties
**** Greeter.class
* META-INF
** MANIFEST.MF
The logging.properties file is a copy of the [JRE_HOME]/lib/logging.properties
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months