April 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBPORTAL-2362) Improve german language-resource-files in portal-cms.war, portal-admin.war and portal-users-samples.war

by Hardy Massen (JIRA)

Improve german language-resource-files in portal-cms.war, portal-admin.war and portal-users-samples.war ------------------------------------------------------------------------------------------------------- Key: JBPORTAL-2362 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2362 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.7.2 Final Reporter: Hardy Massen Some german language-resource-files need corrections: 1. file jboss-portal.sar/portal-cms.sar/portal-cms.war/WEB-INF/classes/Resource_de.properties: CMS_MSG_UPLOADARCHIVE_ASYNC=Ihr Archiv wurde zur Verarbeitung akzeptiert. Sobald die Verarbeitung abgeschlossen ist, wird die Ressource wird in Ihrem Verzeichnis gelistet werden. should be: CMS_MSG_UPLOADARCHIVE_ASYNC=Ihr Archiv wurde zur Verarbeitung akzeptiert. Sobald die Verarbeitung abgeschlossen ist, wird die Ressource in Ihrem Verzeichnis gelistet werden. 2. also file jboss-portal.sar/portal-cms.sar/portal-cms.war/WEB-INF/classes/Resource_de.properties: CMS_LINK_TO_RESOURCES=Verweise auf Ressourcen innerhalb dieses Portals sollten absolut sein. Beispiel: Ein Verweis auf ein Bild mit dem Pfad default/images/back.gif sollte genau wie hier aufgef\u00fchrt eingegeben werden. Stellen Sie dem Ressourcenpfad kein Slash (/) voran. Sie k\u00f6nnen den Verweis \u00fcberpr\u00fcfen, indem Sie auf den Vorschau-Button im Editor klicken. should be: CMS_LINK_TO_RESOURCES=Verweise auf Ressourcen innerhalb dieses Portals sollten relativ sein. Beispiel: Ein Verweis auf ein Bild mit dem Pfad default/images/back.gif sollte genau wie hier aufgef\u00fchrt eingegeben werden. Stellen Sie dem Ressourcenpfad kein Slash (/) voran. Sie k\u00f6nnen den Verweis \u00fcberpr\u00fcfen, indem Sie auf den Vorschau-Button im Editor klicken. In my opinion, the "absolute path" should be a "relative path", like the example "default/images/back.gif" say. /path/from/root = absolute path/from/somewhere = relative This is also wrong in all other existing language-versions. 3. file jboss-portal.sar/samples/portal-users-samples.sar/portal-users-samples.war/WEB-INF/classes/Resource_de.properties: ONE_USER_ONLINE=Sie sind der einizge Benutzer online should be: ONE_USER_ONLINE=Sie sind der einzige Benutzer online -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
2
0 / 0

[JBoss JIRA] Closed: (JBREM-139) need automated test for servlet server invoker

by Ron Sigal (JIRA)

[ https://jira.jboss.org/jira/browse/JBREM-139?page=com.atlassian.jira.plug... ] Ron Sigal closed JBREM-139. --------------------------- Resolution: Done > need automated test for servlet server invoker > ---------------------------------------------- > > Key: JBREM-139 > URL: https://jira.jboss.org/jira/browse/JBREM-139 > Project: JBoss Remoting > Issue Type: Task > Components: general > Affects Versions: 1.2.0 final, 2.5.0.SP2 (Flounder) , 2.2.2.SP11 > Reporter: Tom Elrod > Assignee: Ron Sigal > Priority: Minor > Fix For: 2.5.0.SP3 (Flounder), 2.2.2.SP12 > > > Tests for servlet invoker is manual since have to deploy servlet-invoker.war to jboss in order for it to work. Need to figure out if there > is an easy automated way to do this (since would currently require JBossAS, don't think realistic to run as unit test for JBossRemoting > test run). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBREM-139) need automated test for servlet server invoker

by Ron Sigal (JIRA)

[ https://jira.jboss.org/jira/browse/JBREM-139?page=com.atlassian.jira.plug... ] Ron Sigal commented on JBREM-139: --------------------------------- The changes have been applied to the 2.2 and 2.x branches. Note that on the 2.2 branch, build.xml assumes that the AS is from the 4.2 generation, and on the 2.x branch, build.xml assumes that the AS is from the 5.0 generation. > need automated test for servlet server invoker > ---------------------------------------------- > > Key: JBREM-139 > URL: https://jira.jboss.org/jira/browse/JBREM-139 > Project: JBoss Remoting > Issue Type: Task > Components: general > Affects Versions: 1.2.0 final, 2.5.0.SP2 (Flounder) , 2.2.2.SP11 > Reporter: Tom Elrod > Assignee: Ron Sigal > Priority: Minor > Fix For: 2.5.0.SP3 (Flounder), 2.2.2.SP12 > > > Tests for servlet invoker is manual since have to deploy servlet-invoker.war to jboss in order for it to work. Need to figure out if there > is an easy automated way to do this (since would currently require JBossAS, don't think realistic to run as unit test for JBossRemoting > test run). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBREM-139) need automated test for servlet server invoker

by Ron Sigal (JIRA)

[ https://jira.jboss.org/jira/browse/JBREM-139?page=com.atlassian.jira.plug... ] Ron Sigal commented on JBREM-139: --------------------------------- Other than assuming the existence of an Application Server, the tests are now automated. That is, an AS is configured and started, the tests are run, and the AS is restored to its original state and stopped. The tests are run by the "tests.functional.servlet" target in build.xml. One other necessary step is to set the values in the local.properties file in the main directory. > need automated test for servlet server invoker > ---------------------------------------------- > > Key: JBREM-139 > URL: https://jira.jboss.org/jira/browse/JBREM-139 > Project: JBoss Remoting > Issue Type: Task > Components: general > Affects Versions: 1.2.0 final, 2.5.0.SP2 (Flounder) , 2.2.2.SP11 > Reporter: Tom Elrod > Assignee: Ron Sigal > Priority: Minor > Fix For: 2.5.0.SP3 (Flounder), 2.2.2.SP12 > > > Tests for servlet invoker is manual since have to deploy servlet-invoker.war to jboss in order for it to work. Need to figure out if there > is an easy automated way to do this (since would currently require JBossAS, don't think realistic to run as unit test for JBossRemoting > test run). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBASM-25) Always set jboss.server.log.threshold=DEBUG when starting server test configurations

by Shelly McGowan (JIRA)

Always set jboss.server.log.threshold=DEBUG when starting server test configurations ------------------------------------------------------------------------------------ Key: JBASM-25 URL: https://jira.jboss.org/jira/browse/JBASM-25 Project: JBoss AS Server Manager Issue Type: Feature Request Reporter: Shelly McGowan Assignee: Shelly McGowan Fix For: 1.0.1.GA so it does not have to be configured individually. Reference: https://jira.jboss.org/jira/browse/JBAS-6205?focusedCommentId=12438665#ac... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-6728) 'local-transaction' prop is missing from the template for Tx ConnectionFactories

by Ian Springer (JIRA)

'local-transaction' prop is missing from the template for Tx ConnectionFactories -------------------------------------------------------------------------------- Key: JBAS-6728 URL: https://jira.jboss.org/jira/browse/JBAS-6728 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: ProfileService Reporter: Ian Springer Assignee: Scott M Stark The property should be in the template, since it is present in the set of properties for an existing Tx CF and its view use is CONFIGURATION , e.g.: name=local-transaction, mappedName=localTransactions, viewUse=CONFIGURATION, mandatory=false, value= SimpleMetaType:java.lang.Boolean:false -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

3
5
0 / 0

[JBoss JIRA] Reopened: (JBAS-6716) add back securityConfig config property to JMS destination resources

by Ian Springer (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-6716?page=com.atlassian.jira.plug... ] Ian Springer reopened JBAS-6716: -------------------------------- For an existing topic or queue with a security config (e.g. - see attached xml file), the securityConfig ManagedProperty still has a value of null: name=securityConfig, viewUse=CONFIGURATION, readOnly=false, mandatory=false, removed=false, type=MapCompositeMetaType, value= <<<null>>> > add back securityConfig config property to JMS destination resources > --------------------------------------------------------------------- > > Key: JBAS-6716 > URL: https://jira.jboss.org/jira/browse/JBAS-6716 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: ProfileService > Reporter: Charles Crouch > Assignee: Emanuel Muckenhuber > Priority: Critical > Fix For: JBossAS-5.1.0.CR1 > > Attachments: MyQueueWithSecurityConfig-service.xml > > > e.g. > <c:map-property required="false" name="securityConfig" description="The destination's security configuration"> > <c:simple-property required="false" name="tagName"/> > </c:map-property> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JASSIST-68) Remove limitation on public constructors

by Erik Putrycz (JIRA)

Remove limitation on public constructors ---------------------------------------- Key: JASSIST-68 URL: https://jira.jboss.org/jira/browse/JASSIST-68 Project: Javassist Issue Type: Feature Request Affects Versions: 3.8.1.GA Reporter: Erik Putrycz Assignee: Shigeru Chiba Currently when extending a class with javassist, it is required that the superclass has a public constructor. However, in some cases, this is not a necessary constraint. For instance when extending a class and generating a factory with Javassist, it is better to hide the constructor to prevent users to bypass the factory, and this is not possible currently. This would involve a minor change in inheritAllConstructors() in class CtNewClass -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JASSIST-32) Add method debugWriteFile(String directoryName) to CtClass

by Martin Burger (JIRA)

Add method debugWriteFile(String directoryName) to CtClass ---------------------------------------------------------- Key: JASSIST-32 URL: http://jira.jboss.com/jira/browse/JASSIST-32 Project: Javassist Issue Type: Feature Request Reporter: Martin Burger Assigned To: Shigeru Chiba Priority: Minor Attachments: patch.txt Class CtClass provides method debugWriteFile(). A method debugWriteFile(String directoryName) that calls writeFile(directoryName) would be helpful. -- 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

15 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-6738) secure-wsdl-access is mssing in jboss_5_0.dtd

by Haohua xie (JIRA)

secure-wsdl-access is mssing in jboss_5_0.dtd --------------------------------------------- Key: JBAS-6738 URL: https://jira.jboss.org/jira/browse/JBAS-6738 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.0.1.GA Environment: openSUSU 11.1 x86_64, Sun JDK 1.6.0_12 x86_64 Reporter: Haohua xie Here is my jboss.xml <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE jboss PUBLIC "-//JBoss//DTD JBOSS 5.0//EN" "http://www.jboss.org/j2ee/dtd/jboss_5_0.dtd"> <jboss> <webservices> <context-root>/hxie/framework/security/admin/logic</context-root> </webservices> <enterprise-beans> <session> <ejb-name>LdapAuthInfoLogicBean</ejb-name> <port-component> <port-component-name>LdapAuthInfoLogic</port-component-name> <port-component-uri>/LdapAuthInfoLogic</port-component-uri>  <auth-method>BASIC</auth-method> <transport-guarantee>NONE</transport-guarantee> <secure-wsdl-access>false</secure-wsdl-access> </port-component> </session> </enterprise-beans> </jboss> When I deployed the ear to JBoss 5.0.1 GA, I got the following exception and deployment failed. 2009-04-04 11:52:29,348 DEBUG [org.jboss.deployers.vfs.spi.deployer.JBossXBDeployerHelper] (main) Parsing file: ZipEntryHandler(a)594588547[path=hxie-framework-security-admin.ear/ejb/hxie-framework-security-admin-logic.jar/META-INF/jboss.xml context=file:/home/xhh/workspace/framework/jboss-5.0.1.GA-jdk6/server/default/deploy/ real=file:/home/xhh/workspace/framework/jboss-5.0.1.GA-jdk6/server/default/deploy/hxie-framework-security-admin.ear/ejb/hxie-framework-security-admin-logic.jar/META-INF/jboss.xml] for type: class org.jboss.metadata.ejb.jboss.JBossMetaData 2009-04-04 11:52:29,349 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (main) Created parser: org.apache.xerces.jaxp.SAXParserImpl@3c196fa2, isNamespaceAware: true, isValidating: true, isXIncludeAware: true 2009-04-04 11:52:29,349 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (main) http://xml.org/sax/features/validation set to: true 2009-04-04 11:52:29,349 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (main) http://xml.org/sax/features/namespaces set to: true 2009-04-04 11:52:29,349 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (main) http://apache.org/xml/features/xinclude/fixup-base-uris set to: false 2009-04-04 11:52:29,349 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (main) http://apache.org/xml/features/xinclude/fixup-language set to: false 2009-04-04 11:52:29,349 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (main) http://apache.org/xml/features/validation/dynamic set to: true 2009-04-04 11:52:29,349 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (main) http://apache.org/xml/features/validation/schema set to: false 2009-04-04 11:52:29,349 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (main) http://xml.org/sax/features/validation set to: true 2009-04-04 11:52:29,350 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (main) Created parser: org.apache.xerces.jaxp.SAXParserImpl@3c196fa2, isNamespaceAware: true, isValidating: true, isXIncludeAware: true 2009-04-04 11:52:29,557 DEBUG [org.jboss.deployment.JBossEjbParsingDeployer] (main) Error during deploy: vfszip:/home/xhh/workspace/framework/jboss-5.0.1.GA-jdk6/server/default/deploy/hxie-framework-security-admin.ear/ejb/hxie-framework-security-admin-logic.jar/ org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfszip:/home/xhh/workspace/framework/jboss-5.0.1.GA-jdk6/server/default/deploy/hxie-framework-security-admin.ear/ejb/hxie-framework-security-admin-logic.jar/ at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:337) at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:297) at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:269) at org.jboss.deployment.JBossEjbParsingDeployer.createMetaData(JBossEjbParsingDeployer.java:95) at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.deploy(AbstractParsingDeployerWithOutput.java:230) at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171) at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1210) at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1062) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553) at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781) at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:698) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:304) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:205) at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:405) at org.jboss.Main.boot(Main.java:209) at org.jboss.Main$1.run(Main.java:547) at java.lang.Thread.run(Thread.java:619) Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Element type "secure-wsdl-access" must be declared. @ vfszip:/home/xhh/workspace/framework/jboss-5.0.1.GA-jdk6/server/default/deploy/hxie-framework-security-admin.ear/ejb/hxie-framework-security-admin-logic.jar/META-INF/jboss.xml[19,25] at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203) at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:168) at org.jboss.deployers.vfs.spi.deployer.JBossXBDeployerHelper.parse(JBossXBDeployerHelper.java:199) at org.jboss.deployers.vfs.spi.deployer.JBossXBDeployerHelper.parse(JBossXBDeployerHelper.java:170) at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:132) at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:118) at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parseAndInit(AbstractVFSParsingDeployer.java:256) at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:188) at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:323) ... 24 more Caused by: org.xml.sax.SAXException: Element type "secure-wsdl-access" must be declared. @ vfszip:/home/xhh/workspace/framework/jboss-5.0.1.GA-jdk6/server/default/deploy/hxie-framework-security-admin.ear/ejb/hxie-framework-security-admin-logic.jar/META-INF/jboss.xml[19,25] at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$MetaDataErrorHandler.error(SaxJBossXBParser.java:426) at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.dtd.XMLDTDValidator.handleStartElement(Unknown Source) at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199) ... 32 more 2009-04-04 11:52:29,560 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] (main) Error installing to Parse: name=vfszip:/home/xhh/workspace/framework/jboss-5.0.1.GA-jdk6/server/default/deploy/hxie-framework-security-admin.ear/ state=Not Installed mode=Manual requiredState=Parse org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfszip:/home/xhh/workspace/framework/jboss-5.0.1.GA-jdk6/server/default/deploy/hxie-framework-security-admin.ear/ejb/hxie-framework-security-admin-logic.jar/ at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:337) at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:297) at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:269) at org.jboss.deployment.JBossEjbParsingDeployer.createMetaData(JBossEjbParsingDeployer.java:95) at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.deploy(AbstractParsingDeployerWithOutput.java:230) at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171) at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1210) at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1062) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553) at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781) at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:698) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:304) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:205) at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:405) at org.jboss.Main.boot(Main.java:209) at org.jboss.Main$1.run(Main.java:547) at java.lang.Thread.run(Thread.java:619) Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Element type "secure-wsdl-access" must be declared. @ vfszip:/home/xhh/workspace/framework/jboss-5.0.1.GA-jdk6/server/default/deploy/hxie-framework-security-admin.ear/ejb/hxie-framework-security-admin-logic.jar/META-INF/jboss.xml[19,25] at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203) at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:168) at org.jboss.deployers.vfs.spi.deployer.JBossXBDeployerHelper.parse(JBossXBDeployerHelper.java:199) at org.jboss.deployers.vfs.spi.deployer.JBossXBDeployerHelper.parse(JBossXBDeployerHelper.java:170) at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:132) at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:118) at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parseAndInit(AbstractVFSParsingDeployer.java:256) at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:188) at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:323) ... 24 more Caused by: org.xml.sax.SAXException: Element type "secure-wsdl-access" must be declared. @ vfszip:/home/xhh/workspace/framework/jboss-5.0.1.GA-jdk6/server/default/deploy/hxie-framework-security-admin.ear/ejb/hxie-framework-security-admin-logic.jar/META-INF/jboss.xml[19,25] at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$MetaDataErrorHandler.error(SaxJBossXBParser.java:426) at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.dtd.XMLDTDValidator.handleStartElement(Unknown Source) at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199) ... 32 more in jboss_5_0.dtd:  <!ELEMENT port-component (port-component-name, port-component-uri?, auth-method?, transport-guarantee?) > secure-wsdl-access is not included in the definition of port-component remove the DOCTYPE of jboss.xml and the ear can be deployed successfully. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2009