[JBoss JIRA] (JBIDE-16347) New Tabs wizard for JQM 1.4
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16347?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-16347:
-----------------------------------
Attachment: scr.png
!scr.png!
> New Tabs wizard for JQM 1.4
> ---------------------------
>
> Key: JBIDE-16347
> URL: https://issues.jboss.org/browse/JBIDE-16347
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: jsp/jsf/xml/html source editing
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Labels: new_and_noteworthy
> Fix For: 4.2.0.Alpha2
>
> Attachments: scr.png, Tabs.png, TabsWizBan.png
>
>
> Tabs widget can be implemented as navbar
> {code}
> <div data-role="tabs" id="tabs">
> <div data-role="navbar">
> <ul>
> <li><a href="#one" data-ajax="false">one</a></li>
> <li><a href="#two" data-ajax="false">two</a></li>
> </ul>
> </div>
> <div id="one" class="ui-body-d ui-content">
> </div>
> <div id="two">
> </div>
> </div>
> {code}
> or as listview
> {code}
> <div data-role="tabs">
> <style scoped="scoped">
> .tablist-left {width: 35%; display: inline-block;}
> .tablist-content {width: 50%; display: inline-block;vertical-align: top;margin-left: 5%;}
> </style>
> <ul data-role="listview" data-inset="true" class="tablist-left">
> <li><a href="#one" data-ajax="false">one</a></li>
> <li><a href="#two" data-ajax="false">two</a></li>
> <li><a href="ajax-content.html" data-ajax="false">three</a></li>
> </ul>
> <div id="one" class="ui-body-d tablist-content">
> </div>
> <div id="two" class="ui-body-d tablist-content">
> </div>
> </div>
> {code}
> Some features are not supported by data-* attributes but can be set with script
> Collapsible
> {code}
> <script>
> $("#tabs").tabs({collapsible: true});
> </script>
> {code}
> Initially collapsed
> {code}
> <script>
> $("#tabs").tabs({collapsible: true, active: false});
> </script>
> {code}
> Specifying initially active tab
> {code}
> <script>
> $("#tabs").tabs({active: 1});
> </script>
> {code}
> Tab disablement
> {code}
> <script>
> $("#tabs").tabs({disabled: [2]});
> </script>
> {code}
> Animation of panel showing/hiding
> {code}
> <script>
> $("#tabs").tabs({show: true, hide: true});
> </script>
> {code}
> Tab activation on mouse hover
> {code}
> <script>
> $("#tabs").tabs({event: "mouseover"});
> </script>
> {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
12 years, 5 months
[JBoss JIRA] (JBIDE-16395) Generate new content in New Header wizards for JQM 1.4
by Viacheslav Kabanovich (JIRA)
Viacheslav Kabanovich created JBIDE-16395:
---------------------------------------------
Summary: Generate new content in New Header wizards for JQM 1.4
Key: JBIDE-16395
URL: https://issues.jboss.org/browse/JBIDE-16395
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: jsp/jsf/xml/html source editing
Reporter: Viacheslav Kabanovich
Assignee: Viacheslav Kabanovich
Fix For: 4.2.0.Alpha2
The automatical enhancement of links in toolbars as buttons with inline and mini style, as well as positioning the first two buttons in a header left and right, is deprecated in JQM 1.4 and will be removed in JQM 1.5.
In JQM 1.4, buttons should be set with classes, i.e. positioning is set by 'ui-btn-left' and 'ui-btn-right'.
For JQM 1.4 wizard should generate code
{code}
<div data-role="header">
<a href="#" class="ui-btn-left ui-btn ui-btn-inline ui-mini ui-corner-all ui-btn-icon-left ui-icon-delete">Cancel</a>
<h1>My App</h1>
<a href="#" class="ui-btn-right ui-btn ui-btn-inline ui-mini ui-corner-all ui-icon-check">Save</a>
</div>{code}
Input controls of wizards in both versions can be the same
--
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
12 years, 5 months
[JBoss JIRA] (JBIDE-16395) Generate new content in New Header wizard for JQM 1.4
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16395?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich updated JBIDE-16395:
------------------------------------------
Summary: Generate new content in New Header wizard for JQM 1.4 (was: Generate new content in New Header wizards for JQM 1.4)
> Generate new content in New Header wizard for JQM 1.4
> -----------------------------------------------------
>
> Key: JBIDE-16395
> URL: https://issues.jboss.org/browse/JBIDE-16395
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: jsp/jsf/xml/html source editing
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Labels: new_and_noteworthy
> Fix For: 4.2.0.Alpha2
>
>
> The automatical enhancement of links in toolbars as buttons with inline and mini style, as well as positioning the first two buttons in a header left and right, is deprecated in JQM 1.4 and will be removed in JQM 1.5.
> In JQM 1.4, buttons should be set with classes, i.e. positioning is set by 'ui-btn-left' and 'ui-btn-right'.
> For JQM 1.4 wizard should generate code
> {code}
> <div data-role="header">
> <a href="#" class="ui-btn-left ui-btn ui-btn-inline ui-mini ui-corner-all ui-btn-icon-left ui-icon-delete">Cancel</a>
> <h1>My App</h1>
> <a href="#" class="ui-btn-right ui-btn ui-btn-inline ui-mini ui-corner-all ui-icon-check">Save</a>
> </div>{code}
> Input controls of wizards in both versions can be the same
--
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
12 years, 5 months
[JBoss JIRA] (JBIDE-16220) create an all-in-one build for JBT projects, using submodules
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16220?page=com.atlassian.jira.plugi... ]
Denis Golovin edited comment on JBIDE-16220 at 1/23/14 2:09 PM:
----------------------------------------------------------------
This approach could be actually good way to do integration builds once a week or every change in this composite git repo. It would be similar to map files in eclipse. Not every commit to actual module would trigger it. If module lead wants integration build he/she should go an update submodule in composite repo.
It also would let us do:
- branches in this composite repo for different streams
- tagging in one place for everything like:
{code}git foreach 'git tag 4.1.0.GA -m "JBoss Tools 4.1.0.GA"{code}
The name for repo would be jbosstools-releng (similar to what they have in eclipse) or jbosstools-submodules or jbosstools-aggregated or jbosstools-product or e.t.c ... your suggestions are welcome.
was (Author: dgolovin):
This approach could be actually good way to do integration builds once a week or every change in this composite git repo. It would be similar to tag files in eclipse. Not every commit to actual module would trigger it. If module lead wants integration build he/she should go an update submodule in composite repo.
It also would let us do:
- branches in this composite repo for different streams
- tagging in one place for everything like:
{code}git foreach 'git tag 4.1.0.GA -m "JBoss Tools 4.1.0.GA"{code}
The name for repo would be jbosstools-releng (similar to what they have in eclipse) or jbosstools-submodules or jbosstools-aggregated or jbosstools-product or e.t.c ... your suggestions are welcome.
> create an all-in-one build for JBT projects, using submodules
> -------------------------------------------------------------
>
> Key: JBIDE-16220
> URL: https://issues.jboss.org/browse/JBIDE-16220
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.2.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.2.x
>
> Attachments: buildlog_maven311.txt
>
>
> Git 1.8.2 includes an option to have submodules track a branch tip, rather than specific commit IDs.
> {code:title=https://github.com/git/git/blob/master/Documentation/RelNotes/1.8.2.txt#L186-L188}
> "git submodule" started learning a new mode to integrate with the
> tip of the remote branch (as opposed to integrating with the commit
> recorded in the superproject's gitlink).
> {code}
> Therefore, while the solution [~dgolovin] has for his https://github.com/dgolovin/jbosstools-submodules project is a decent option, it requires updating to stay current with branch tips. It's therefore only really as useful as it stays current.
> If we can get Git 1.8.2 or newer installed on the Jenkins slaves, we could do a submodule build against whatever branch we wanted - master, 4.2.0.Alpha1x, etc.
--
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
12 years, 5 months
[JBoss JIRA] (JBIDE-2032) Help button works not in all wizards.
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-2032?page=com.atlassian.jira.plugin... ]
Denis Golovin commented on JBIDE-2032:
--------------------------------------
{quote}What happens if the docs bundle is not installed ? will there be some nontangible error ?{quote}
If doc plugin is not installed there would be a message in help tray: "The context help for this user interface element could not be found."
> Help button works not in all wizards.
> -------------------------------------
>
> Key: JBIDE-2032
> URL: https://issues.jboss.org/browse/JBIDE-2032
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: help
> Affects Versions: 2.1.0.beta1
> Reporter: Anton Klimkovich
> Assignee: Denis Golovin
> Priority: Minor
> Fix For: 4.2.x
>
> Attachments: CreateJSFLibrary.PNG, DriverDefinitions.PNG, EditDriverDefinitions.PNG, InstallNewServerAdapter.PNG, JSFImplementationLibrary.PNG, NewConnectionProfile.PNG, NewDriverDefinitions.PNG, NewSeamRuntime.PNG, NewServer.PNG, Resource - Eclipse Platform _028.png
>
>
> Wizards with non-working help button attached.
--
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
12 years, 5 months
[JBoss JIRA] (JBIDE-13159) gwt-kitchensink fails to deploy - class not found
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13159?page=com.atlassian.jira.plugi... ]
Snjezana Peco resolved JBIDE-13159.
-----------------------------------
Resolution: Out of Date
> gwt-kitchensink fails to deploy - class not found
> -------------------------------------------------
>
> Key: JBIDE-13159
> URL: https://issues.jboss.org/browse/JBIDE-13159
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: gwt, maven
> Affects Versions: 4.0.0.CR1
> Environment: JBDS 6.0.0.CR1a B133
> JBT 4.0.0.CR1a B97
> OS X 10.8.2
> Oracle Java 1.7
> Reporter: Martin Malina
> Assignee: Snjezana Peco
> Fix For: 4.1.2.Final
>
>
> When you try to deploy the gwt project from Central, it fails to deploy with the following error:
> {code}
> 15:27:18,698 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found jboss-gwt-webapp.war in deployment directory. To trigger deployment create a file called jboss-gwt-webapp.war.dodeploy
> 15:27:18,713 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "jboss-gwt-webapp.war"
> 15:27:20,830 INFO [org.jboss.as.jpa] (MSC service thread 1-3) JBAS011401: Read persistence.xml for primary
> 15:27:20,978 WARN [org.jboss.as.dependency.private] (MSC service thread 1-3) JBAS018567: Deployment "deployment.jboss-gwt-webapp.war" is using a private module ("org.jboss.as.naming:main") which may be changed or removed in future versions without notice.
> 15:27:20,979 WARN [org.jboss.as.dependency.private] (MSC service thread 1-3) JBAS018567: Deployment "deployment.jboss-gwt-webapp.war" is using a private module ("org.jboss.as.server:main") which may be changed or removed in future versions without notice.
> 15:27:21,021 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016002: Processing weld deployment jboss-gwt-webapp.war
> 15:27:21,301 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016005: Starting Services for CDI deployment: jboss-gwt-webapp.war
> 15:27:21,332 INFO [org.jboss.weld.Version] (MSC service thread 1-2) WELD-000900 1.1.5 (AS71)
> 15:27:21,364 INFO [org.jboss.as.jpa] (MSC service thread 1-1) JBAS011402: Starting Persistence Unit Service 'jboss-gwt-webapp.war#primary'
> 15:27:21,461 INFO [org.hibernate.annotations.common.Version] (MSC service thread 1-1) HCANN000001: Hibernate Commons Annotations {4.0.1.Final}
> 15:27:21,467 INFO [org.hibernate.Version] (MSC service thread 1-1) HHH000412: Hibernate Core {4.0.1.Final}
> 15:27:21,469 INFO [org.hibernate.cfg.Environment] (MSC service thread 1-1) HHH000206: hibernate.properties not found
> 15:27:21,473 INFO [org.hibernate.cfg.Environment] (MSC service thread 1-1) HHH000021: Bytecode provider name : javassist
> 15:27:21,490 INFO [org.hibernate.ejb.Ejb3Configuration] (MSC service thread 1-1) HHH000204: Processing PersistenceUnitInfo [
> name: primary
> ...]
> 15:27:21,499 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.persistenceunit."jboss-gwt-webapp.war#primary": org.jboss.msc.service.StartException in service jboss.persistenceunit."jboss-gwt-webapp.war#primary": Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [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: java.lang.RuntimeException: error trying to scan <jar-file>: vfs:/Users/rasp/jbossqa/runtimes/jboss-as-7.1.1.Final/standalone/deployments/jboss-gwt-webapp.war/WEB-INF/classes/
> at org.hibernate.ejb.Ejb3Configuration.scanForClasses(Ejb3Configuration.java:854)
> at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:596)
> at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:72)
> at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.createContainerEntityManagerFactory(PersistenceUnitServiceImpl.java:162)
> at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.start(PersistenceUnitServiceImpl.java:85)
> 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]
> ... 3 more
> Caused by: java.lang.RuntimeException: JBAS011431: Could not load entity class 'org.jboss.errai.marshalling.server.impl.ServerMarshallingFactoryImpl$30' with PersistenceUnitInfo.getClassLoader()
> at org.jboss.as.jpa.hibernate4.HibernateAnnotationScanner.getPackagesInJar(HibernateAnnotationScanner.java:175)
> at org.hibernate.ejb.Ejb3Configuration.addScannedEntries(Ejb3Configuration.java:489)
> at org.hibernate.ejb.Ejb3Configuration.scanForClasses(Ejb3Configuration.java:851)
> ... 9 more
> Caused by: java.lang.ClassNotFoundException: org.jboss.errai.marshalling.server.impl.ServerMarshallingFactoryImpl$30 from [Module "deployment.jboss-gwt-webapp.war:main" 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.performLoadClass(ConcurrentClassLoader.java:398)
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120)
> at org.jboss.as.jpa.hibernate4.HibernateAnnotationScanner.getPackagesInJar(HibernateAnnotationScanner.java:171)
> ... 11 more
> 15:27:21,714 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "jboss-gwt-webapp.war" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.persistenceunit.\"jboss-gwt-webapp.war#primary\"" => "org.jboss.msc.service.StartException in service jboss.persistenceunit.\"jboss-gwt-webapp.war#primary\": Failed to start service"}}
> 15:27:21,742 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015877: Stopped deployment jboss-gwt-webapp.war in 27ms
> 15:27:21,743 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report
> JBAS014777: Services which failed to start: service jboss.persistenceunit."jboss-gwt-webapp.war#primary": org.jboss.msc.service.StartException in service jboss.persistenceunit."jboss-gwt-webapp.war#primary": Failed to start service
> 15:27:21,745 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014671: Failed services" => {"jboss.persistenceunit.\"jboss-gwt-webapp.war#primary\"" => "org.jboss.msc.service.StartException in service jboss.persistenceunit.\"jboss-gwt-webapp.war#primary\": Failed to start service"}}}}
> {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
12 years, 5 months
[JBoss JIRA] (JBIDE-13159) gwt-kitchensink fails to deploy - class not found
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13159?page=com.atlassian.jira.plugi... ]
Snjezana Peco updated JBIDE-13159:
----------------------------------
Fix Version/s: 4.1.2.Final
(was: 4.1.x)
> gwt-kitchensink fails to deploy - class not found
> -------------------------------------------------
>
> Key: JBIDE-13159
> URL: https://issues.jboss.org/browse/JBIDE-13159
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: gwt, maven
> Affects Versions: 4.0.0.CR1
> Environment: JBDS 6.0.0.CR1a B133
> JBT 4.0.0.CR1a B97
> OS X 10.8.2
> Oracle Java 1.7
> Reporter: Martin Malina
> Assignee: Snjezana Peco
> Fix For: 4.1.2.Final
>
>
> When you try to deploy the gwt project from Central, it fails to deploy with the following error:
> {code}
> 15:27:18,698 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found jboss-gwt-webapp.war in deployment directory. To trigger deployment create a file called jboss-gwt-webapp.war.dodeploy
> 15:27:18,713 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "jboss-gwt-webapp.war"
> 15:27:20,830 INFO [org.jboss.as.jpa] (MSC service thread 1-3) JBAS011401: Read persistence.xml for primary
> 15:27:20,978 WARN [org.jboss.as.dependency.private] (MSC service thread 1-3) JBAS018567: Deployment "deployment.jboss-gwt-webapp.war" is using a private module ("org.jboss.as.naming:main") which may be changed or removed in future versions without notice.
> 15:27:20,979 WARN [org.jboss.as.dependency.private] (MSC service thread 1-3) JBAS018567: Deployment "deployment.jboss-gwt-webapp.war" is using a private module ("org.jboss.as.server:main") which may be changed or removed in future versions without notice.
> 15:27:21,021 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016002: Processing weld deployment jboss-gwt-webapp.war
> 15:27:21,301 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016005: Starting Services for CDI deployment: jboss-gwt-webapp.war
> 15:27:21,332 INFO [org.jboss.weld.Version] (MSC service thread 1-2) WELD-000900 1.1.5 (AS71)
> 15:27:21,364 INFO [org.jboss.as.jpa] (MSC service thread 1-1) JBAS011402: Starting Persistence Unit Service 'jboss-gwt-webapp.war#primary'
> 15:27:21,461 INFO [org.hibernate.annotations.common.Version] (MSC service thread 1-1) HCANN000001: Hibernate Commons Annotations {4.0.1.Final}
> 15:27:21,467 INFO [org.hibernate.Version] (MSC service thread 1-1) HHH000412: Hibernate Core {4.0.1.Final}
> 15:27:21,469 INFO [org.hibernate.cfg.Environment] (MSC service thread 1-1) HHH000206: hibernate.properties not found
> 15:27:21,473 INFO [org.hibernate.cfg.Environment] (MSC service thread 1-1) HHH000021: Bytecode provider name : javassist
> 15:27:21,490 INFO [org.hibernate.ejb.Ejb3Configuration] (MSC service thread 1-1) HHH000204: Processing PersistenceUnitInfo [
> name: primary
> ...]
> 15:27:21,499 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.persistenceunit."jboss-gwt-webapp.war#primary": org.jboss.msc.service.StartException in service jboss.persistenceunit."jboss-gwt-webapp.war#primary": Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [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: java.lang.RuntimeException: error trying to scan <jar-file>: vfs:/Users/rasp/jbossqa/runtimes/jboss-as-7.1.1.Final/standalone/deployments/jboss-gwt-webapp.war/WEB-INF/classes/
> at org.hibernate.ejb.Ejb3Configuration.scanForClasses(Ejb3Configuration.java:854)
> at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:596)
> at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:72)
> at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.createContainerEntityManagerFactory(PersistenceUnitServiceImpl.java:162)
> at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.start(PersistenceUnitServiceImpl.java:85)
> 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]
> ... 3 more
> Caused by: java.lang.RuntimeException: JBAS011431: Could not load entity class 'org.jboss.errai.marshalling.server.impl.ServerMarshallingFactoryImpl$30' with PersistenceUnitInfo.getClassLoader()
> at org.jboss.as.jpa.hibernate4.HibernateAnnotationScanner.getPackagesInJar(HibernateAnnotationScanner.java:175)
> at org.hibernate.ejb.Ejb3Configuration.addScannedEntries(Ejb3Configuration.java:489)
> at org.hibernate.ejb.Ejb3Configuration.scanForClasses(Ejb3Configuration.java:851)
> ... 9 more
> Caused by: java.lang.ClassNotFoundException: org.jboss.errai.marshalling.server.impl.ServerMarshallingFactoryImpl$30 from [Module "deployment.jboss-gwt-webapp.war:main" 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.performLoadClass(ConcurrentClassLoader.java:398)
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120)
> at org.jboss.as.jpa.hibernate4.HibernateAnnotationScanner.getPackagesInJar(HibernateAnnotationScanner.java:171)
> ... 11 more
> 15:27:21,714 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "jboss-gwt-webapp.war" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.persistenceunit.\"jboss-gwt-webapp.war#primary\"" => "org.jboss.msc.service.StartException in service jboss.persistenceunit.\"jboss-gwt-webapp.war#primary\": Failed to start service"}}
> 15:27:21,742 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015877: Stopped deployment jboss-gwt-webapp.war in 27ms
> 15:27:21,743 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report
> JBAS014777: Services which failed to start: service jboss.persistenceunit."jboss-gwt-webapp.war#primary": org.jboss.msc.service.StartException in service jboss.persistenceunit."jboss-gwt-webapp.war#primary": Failed to start service
> 15:27:21,745 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014671: Failed services" => {"jboss.persistenceunit.\"jboss-gwt-webapp.war#primary\"" => "org.jboss.msc.service.StartException in service jboss.persistenceunit.\"jboss-gwt-webapp.war#primary\": Failed to start service"}}}}
> {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
12 years, 5 months
[JBoss JIRA] (JBIDE-12139) Proxy Settings - setting a proxy seems to cause Project Examples, News and Blogs to spin forever
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12139?page=com.atlassian.jira.plugi... ]
Snjezana Peco updated JBIDE-12139:
----------------------------------
Fix Version/s: 4.2.0.Alpha1
4.1.1.Final
(was: 4.0.x)
> Proxy Settings - setting a proxy seems to cause Project Examples, News and Blogs to spin forever
> ------------------------------------------------------------------------------------------------
>
> Key: JBIDE-12139
> URL: https://issues.jboss.org/browse/JBIDE-12139
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 3.3.0.CR1
> Environment: CR1b
> Reporter: Burr Sutter
> Assignee: Snjezana Peco
> Fix For: 4.1.1.Final, 4.2.0.Alpha1
>
> Attachments: JBDS_Proxy_Settings.png, jbide-12139.png, proxy.png
>
>
> I have been experimenting with an internally hosted maven repository for EAP6 - where I need to set a proxy in order to access that internal server. Eclipse-Preferences-Network Connections allows you to establish a proxy - I certainly could have done it incorrectly. But I also watched an end-user, who required a proxy for internal network server access struggle with JBDS - because JBDS could not find the newly created OpenShift application - it would always timeout.
> Screenshot of my settings are attached - they should work on the VPN.
--
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
12 years, 5 months