[JBoss JIRA] (AS7-4439) CXF Does not work with Turkish Locale
by Kabir Khan (JIRA)
Kabir Khan created AS7-4439:
-------------------------------
Summary: CXF Does not work with Turkish Locale
Key: AS7-4439
URL: https://issues.jboss.org/browse/AS7-4439
Project: Application Server 7
Issue Type: Bug
Components: Web Services
Reporter: Kabir Khan
Assignee: Alessio Soldano
I'm trying to run the tests as described in AS7-4301, and there is a problem with how EnumUtil parses the annotation.
{code}
static <T extends Enum<T>> T valueOf(Class<T> enumClass, String name) {
return Enum.valueOf(enumClass, name.toUpperCase());
}
{code}
"unqualified" becomes "UNQUALIF?ED", using name.toUpperCase(Locale.ENGLISH) should fix this. I'm assigning to you since you have more knowledge of Apache CXF.
{code}
properties=[org.jboss.as.webservices.metadata.modelEjbComponentViewName -> service jboss.deployment.subunit."ws-notannotated-XXX.ear"."ws-notannotated-XXX.war".component.SampleBeanWebService.VIEW."org.jboss.as.test.integration.ws.context.application.SampleBeanWebService".SERVICE_ENDPOINT]
11:32:36,214 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-16) Creating Service {http://application.context.ws.integration.test.as.jboss.org/}SampleBeanWebServiceService from class org.jboss.as.test.integration.ws.context.application.SampleBeanWebService
11:32:36,221 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-16) MSC00001: Failed to start service jboss.deployment.subunit."ws-notannotated-XXX.ear"."ws-notannotated-XXX.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.subunit."ws-notannotated-XXX.ear"."ws-notannotated-XXX.war".INSTALL: JBAS018733: Failed to process phase INSTALL of subdeployment "ws-notannotated-XXX.war" of deployment "ws-notannotated-XXX.ear"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:120) [jboss-as-server-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
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$Worker.runTask(ThreadPoolExecutor.java:886) [classes.jar:1.6.0_29]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [classes.jar:1.6.0_29]
at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_29]
Caused by: javax.xml.ws.WebServiceException: java.lang.IllegalArgumentException: No enum const class org.apache.ws.commons.schema.XmlSchemaForm.UNQUAL?F?ED
at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:350)
at org.jboss.wsf.stack.cxf.deployment.EndpointImpl.doPublish(EndpointImpl.java:88)
at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:239)
at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:509)
at org.jboss.wsf.stack.cxf.configuration.NonSpringBusHolder.configure(NonSpringBusHolder.java:117)
at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.startDeploymentBus(BusDeploymentAspect.java:113)
at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.start(BusDeploymentAspect.java:66)
at org.jboss.as.webservices.deployers.AspectDeploymentProcessor.deploy(AspectDeploymentProcessor.java:74)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:114) [jboss-as-server-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
... 5 more
Caused by: java.lang.IllegalArgumentException: No enum const class org.apache.ws.commons.schema.XmlSchemaForm.UNQUAL?F?ED
at java.lang.Enum.valueOf(Enum.java:196) [classes.jar:1.6.0_29]
at org.apache.ws.commons.schema.EnumUtil.valueOf(EnumUtil.java:31)
at org.apache.ws.commons.schema.XmlSchemaForm.schemaValueOf(XmlSchemaForm.java:32)
at org.apache.ws.commons.schema.SchemaBuilder.getFormDefault(SchemaBuilder.java:181)
at org.apache.ws.commons.schema.SchemaBuilder.handleSchemaElementBasics(SchemaBuilder.java:1489)
at org.apache.ws.commons.schema.SchemaBuilder.handleXmlSchemaElement(SchemaBuilder.java:649)
at org.apache.ws.commons.schema.SchemaBuilder.build(SchemaBuilder.java:157)
at org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:412)
at org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:398)
at org.apache.cxf.common.xmlschema.SchemaCollection.read(SchemaCollection.java:133)
at org.apache.cxf.databinding.AbstractDataBinding.addSchemaDocument(AbstractDataBinding.java:190)
at org.apache.cxf.databinding.AbstractDataBinding.addSchemaDocument(AbstractDataBinding.java:93)
at org.apache.cxf.jaxb.JAXBDataBinding.initialize(JAXBDataBinding.java:349)
at org.apache.cxf.service.factory.AbstractServiceFactoryBean.initializeDataBindings(AbstractServiceFactoryBean.java:86)
at org.apache.cxf.service.factory.ReflectionServiceFactoryBean.buildServiceFromClass(ReflectionServiceFactoryBean.java:444)
at org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean.buildServiceFromClass(JaxWsServiceFactoryBean.java:685)
at org.apache.cxf.service.factory.ReflectionServiceFactoryBean.initializeServiceModel(ReflectionServiceFactoryBean.java:507)
at org.apache.cxf.service.factory.ReflectionServiceFactoryBean.create(ReflectionServiceFactoryBean.java:241)
at org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean.create(JaxWsServiceFactoryBean.java:205)
at org.apache.cxf.frontend.AbstractWSDLBasedEndpointFactory.createEndpoint(AbstractWSDLBasedEndpointFactory.java:101)
at org.apache.cxf.frontend.ServerFactoryBean.create(ServerFactoryBean.java:157)
at org.apache.cxf.jaxws.JaxWsServerFactoryBean.create(JaxWsServerFactoryBean.java:203)
at org.apache.cxf.jaxws.EndpointImpl.getServer(EndpointImpl.java:433)
at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:322)
... 13 more
{code}
--
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
14 years
[JBoss JIRA] (JBJCA-793) JBossTS is missing bridge part for TransactionTimeoutConfiguration
by Viacheslav Krot (JIRA)
Viacheslav Krot created JBJCA-793:
-------------------------------------
Summary: JBossTS is missing bridge part for TransactionTimeoutConfiguration
Key: JBJCA-793
URL: https://issues.jboss.org/browse/JBJCA-793
Project: IronJacamar
Issue Type: Bug
Components: Core
Affects Versions: 1.0.7.Final
Environment: JBoss AS 7.1.0
Reporter: Viacheslav Krot
Assignee: Jesper Pedersen
JBossTS is missing bridge part for TransactionTimeoutConfiguration.
org.jboss.jca.core.connectionmanager.tx.TxConnectionManagerImpl#getTimeLeftBeforeTransactionTimeout checks if transactionManager is instance of org.jboss.jca.core.spi.transaction.TransactionTimeoutConfiguration, but transactionManager comes from JBossTM, it is instance of com.arjuna.ats.jbossatx.jts.TransactionManagerDelegate in my case, that in turn implements org.jboss.tm.TransactionTimeoutConfiguration, thus check always fails.
--
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
14 years
[JBoss JIRA] (AS7-3036) Remove OSGi bundles that cannot be supported
by Rafael Soares (JIRA)
[ https://issues.jboss.org/browse/AS7-3036?page=com.atlassian.jira.plugin.s... ]
Rafael Soares commented on AS7-3036:
------------------------------------
Sorry.
I found the same doubt solved here https://community.jboss.org/message/723971#723971
??Now we support maven coordinates in the capability name attribute. So you would simply specify the maven coordinates for the web console.??
That's an amazing feature...
Thanks.
> Remove OSGi bundles that cannot be supported
> --------------------------------------------
>
> Key: AS7-3036
> URL: https://issues.jboss.org/browse/AS7-3036
> Project: Application Server 7
> Issue Type: Task
> Components: OSGi
> Reporter: Thomas Diesler
> Assignee: Thomas Diesler
> Fix For: 7.1.0.Final
>
>
> Currently we have:
> * Webconsole, provided by Felix (requires HttpService)
> * HttpService, provided by PaxWeb (runs on Jetty)
> * Webapp support, provided by PaxWeb (runs on Jetty)
> * LogService, provided by Felix
> * ConfigAdmin service, provided by Felix
> * JMX services, provided by Aries
> * EventAdmin, provided by Felix
> * DeclarativServices, provided by Felix
> * STOMP endpoints (Stilts), provided by JBoss
> * Blueprint, provided by Aries
> * XML parsing, provided by JBoss
> * JNDI support, provided by JBoss
> * JTA support, provided by JBoss
--
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
14 years
[JBoss JIRA] (AS7-4431) json nodes with escape characters not being processed correctly by cli
by Simeon Pinder (JIRA)
Simeon Pinder created AS7-4431:
----------------------------------
Summary: json nodes with escape characters not being processed correctly by cli
Key: AS7-4431
URL: https://issues.jboss.org/browse/AS7-4431
Project: Application Server 7
Issue Type: Bug
Components: CLI
Affects Versions: 7.1.1.Final
Environment: standalone but should occur with domain as well.
Reporter: Simeon Pinder
Assignee: Alexey Loubyansky
Priority: Critical
The address for 'subsystem=mail/mail-session=java:jboss/mail/Default' must be escaped because of the ':' and '/' characters in the 'mail-session' node.
Log in via the DMR cli shell and you're able to browse the same node via '/subsystem=mail/mail-session=java\:jboss\/mail\/Default/:read-resource' If you attempt to read the same node via escaped json you get:
failureDescription=JBAS014807: Management resource '[
("subsystem" => "mail"),
("mail-session" => "java:jboss")
]' not found, rolledBack=true}
--
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
14 years
[JBoss JIRA] (AS7-3036) Remove OSGi bundles that cannot be supported
by Rafael Soares (JIRA)
[ https://issues.jboss.org/browse/AS7-3036?page=com.atlassian.jira.plugin.s... ]
Rafael Soares commented on AS7-3036:
------------------------------------
Thanks for reply!
But, where can I find the bundle files? Can I get from the original project repos and then deploy into AS7?
> Remove OSGi bundles that cannot be supported
> --------------------------------------------
>
> Key: AS7-3036
> URL: https://issues.jboss.org/browse/AS7-3036
> Project: Application Server 7
> Issue Type: Task
> Components: OSGi
> Reporter: Thomas Diesler
> Assignee: Thomas Diesler
> Fix For: 7.1.0.Final
>
>
> Currently we have:
> * Webconsole, provided by Felix (requires HttpService)
> * HttpService, provided by PaxWeb (runs on Jetty)
> * Webapp support, provided by PaxWeb (runs on Jetty)
> * LogService, provided by Felix
> * ConfigAdmin service, provided by Felix
> * JMX services, provided by Aries
> * EventAdmin, provided by Felix
> * DeclarativServices, provided by Felix
> * STOMP endpoints (Stilts), provided by JBoss
> * Blueprint, provided by Aries
> * XML parsing, provided by JBoss
> * JNDI support, provided by JBoss
> * JTA support, provided by JBoss
--
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
14 years
[JBoss JIRA] (AS7-4445) Kitchensink archetype - comments additions to the generated pom.xml
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/AS7-4445?page=com.atlassian.jira.plugin.s... ]
Brian Leathem moved RF-12107 to AS7-4445:
-----------------------------------------
Project: Application Server 7 (was: RichFaces)
Key: AS7-4445 (was: RF-12107)
Affects Version/s: (was: 4.2.0.Final)
Component/s: (was: archetype)
Security: (was: Public)
> Kitchensink archetype - comments additions to the generated pom.xml
> -------------------------------------------------------------------
>
> Key: AS7-4445
> URL: https://issues.jboss.org/browse/AS7-4445
> Project: Application Server 7
> Issue Type: Enhancement
> Environment: app generated by Kitchensink archetype
> Reporter: Juraj Huska
> Assignee: Brian Leathem
> Priority: Optional
>
> I would like to suggest some comments additions, to increase user's comprehension.
> - _To the comment above arq-jbossas-managed profile:_
> There should be mentioned that you have to provide path to your JBoss instance, by changing the jbossHome property in arquillian.xml, or we can alter the profile to download and unzip JBoss distribution as it is [here|https://github.com/richfaces/qa/blob/master/pom.xml#L559].
> - _In the same comment as mentioned above_
> There should be definitely mentioned the version of JBoss AS it works with, or there should be this version defined explicitly, since it does not work with all AS 7 distributions
> - _The comment above arq-jbossas-remote profile_
> There is the same problem with JBoss AS versions as mentioned above.
--
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
14 years
[JBoss JIRA] (AS7-4440) Deploying Spring OSGi WAR bundle
by Rui Abreu (JIRA)
Rui Abreu created AS7-4440:
------------------------------
Summary: Deploying Spring OSGi WAR bundle
Key: AS7-4440
URL: https://issues.jboss.org/browse/AS7-4440
Project: Application Server 7
Issue Type: Bug
Affects Versions: 7.1.1.Final
Reporter: Rui Abreu
When deploying a Spring powered OSGi WAR bundle to 7.1.1 Final, the following exception arises:
11:52:08,998 ERROR [stderr] (WebExtender-Init) Exception in thread "WebExtender-Init" java.lang.NoClassDefFoundError: org/apache/catalina/Loader
11:52:08,998 ERROR [stderr] (WebExtender-Init) at org.springframework.osgi.web.extender.internal.activator.WarListenerConfiguration.createDefaultWarDeployer(WarListenerConfiguration.java:194)
11:52:08,999 ERROR [stderr] (WebExtender-Init) at org.springframework.osgi.web.extender.internal.activator.WarListenerConfiguration.<init>(WarListenerConfiguration.java:105)
11:52:08,999 ERROR [stderr] (WebExtender-Init) at org.springframework.osgi.web.extender.internal.activator.WarLoaderListener$1.run(WarLoaderListener.java:361)
11:52:09,000 ERROR [stderr] (WebExtender-Init) at java.lang.Thread.run(Thread.java:722)
11:52:09,001 ERROR [stderr] (WebExtender-Init) Caused by: java.lang.ClassNotFoundException: org.apache.catalina.Loader from [Module "deployment.org.springframework.osgi.web:1.2.1" from Service Module Loader]
The spring-osgi-1.2.1 was previously deployed to the server and the test of sharing a spring bean between two Spring OSGi JAR bundles was successful
--
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
14 years, 1 month