[JBoss JIRA] (JBIDE-11348) Not generate clientsample codes in user-created folder on JBoss web services, only in src folder.
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11348?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-11348:
----------------------------------
Fix Version/s: (was: 4.0.x)
> Not generate clientsample codes in user-created folder on JBoss web services, only in src folder.
> -------------------------------------------------------------------------------------------------
>
> Key: JBIDE-11348
> URL: https://issues.jboss.org/browse/JBIDE-11348
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Webservices
> Affects Versions: 3.3.0.M5
> Environment: Eclipse Indigo 3.7.2, JBossTools 3.3
> Reporter: Joseph Hwang
> Assignee: Brian Fitzpatrick
> Priority: Minor
> Attachments: 1_buildpath.jpg, 2_no_folder_choice.jpg, 3_generate_user_defined_folder.jpg, 4_choose_user_defined_folder.jpg, 5_generate_ws_client_code.jpg, 6_no_client_sample.jpg, 7_choose_src_folder.jpg, client_2.jpg, client_3.jpg, client_4.jpg, generating_client.doc, HelloWorld.zip, readme_pls.docx
>
>
> Web Services deployment is ok! But generating clientsample codes is failed in user-created folder.
> clientsample codes is generated only in default 'src' folder.
> Pls, check this thread https://community.jboss.org/thread/196669?start=0&tstart=0 .
--
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, 9 months
[JBoss JIRA] (JBIDE-14987) Forge 2 Notification Popup is not working in Windows 8
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14987?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-14987:
----------------------------------
Fix Version/s: 4.1.0.CR1
> Forge 2 Notification Popup is not working in Windows 8
> ------------------------------------------------------
>
> Key: JBIDE-14987
> URL: https://issues.jboss.org/browse/JBIDE-14987
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.1.0.Beta1
> Environment: JBoss Developer Studio 7.0.0.Beta1
> Reporter: George Gastaldi
> Fix For: 4.1.0.CR1
>
>
> The following exception is thrown:
> {code}
> Caused by: java.lang.NullPointerException
> at org.jboss.tools.forge.ui.notifications.NotificationDialog.calculateInitialLocation(NotificationDialog.java:80)
> at org.jboss.tools.forge.ui.notifications.NotificationDialog.createShell(NotificationDialog.java:68)
> at org.jboss.tools.forge.ui.notifications.NotificationDialog.<init>(NotificationDialog.java:55)
> at org.jboss.tools.forge.ui.notifications.NotificationDialog.notify(NotificationDialog.java:29)
> at org.jboss.tools.forge.ui.ext.wizards.ForgeWizard$1.run(ForgeWizard.java:123)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135){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, 9 months
[JBoss JIRA] (JBIDE-15053) Support DownloadRuntimes with no download url
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15053?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-15053:
----------------------------------
Fix Version/s: (was: 4.1.x)
> Support DownloadRuntimes with no download url
> ---------------------------------------------
>
> Key: JBIDE-15053
> URL: https://issues.jboss.org/browse/JBIDE-15053
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection, server
> Affects Versions: 4.1.0.CR1
> Reporter: Fred Bricon
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.1.0.CR1
>
>
> EAP runtimes defined in stacks don't show up as download runtimes. They don't have a download url but have a human readable url. As in JBDS 6 (in central), they should appear as a valid choice and display the human url so the user can manually go and install the runtime.
> I also noticed that if the download url is missing the download runtime wizard refuses to finish (url not valid error). It should close without any error.
--
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, 9 months
[JBoss JIRA] (JBIDE-13601) Backport to 4.0.x - [Eclipse Integration] GPE's "GWT Compile" doesn't create the errai classes
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13601?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-13601:
----------------------------------
Fix Version/s: 4.0.2.Final
(was: 4.0.1.Final)
> Backport to 4.0.x - [Eclipse Integration] GPE's "GWT Compile" doesn't create the errai classes
> ----------------------------------------------------------------------------------------------
>
> Key: JBIDE-13601
> URL: https://issues.jboss.org/browse/JBIDE-13601
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Affects Versions: 4.0.0.Final
> Environment: Windows 7, Google Plugin for Eclipse 2.5.2, JBoss Tools 3.3.0.Beta1, m2e 1.0.100, m2e-wtp 0.15.2
> Reporter: Fred Bricon
> Assignee: Nick Boldt
> Labels: new_and_noteworthy
> Fix For: 4.0.2.Final
>
> Attachments: 0001-JBIDE-13487-fix-errai-deployment-issues.patch
>
>
> We're trying to achieve the following workflow for the user inside Eclipse/ GPE / JBoss Tools:
> * create project
> * execute Google > GWT Compile
> * Run As > Run On Server
> * browse the application
> When a gwt maven project is detected, GPE sets the GWT compilation output directory to target/<artifactId>-<version>/. So ultimately we could automatically mark that folder as deployable for WTP and pretty much achieve that ideal workflow.
> Until this is done automatically, we can do it manually. Here's a slightly more complex workflow :
> * Create a new GWT Project from JBoss Central
> * Right-click on project > Google > GWT compile
> * Add the Kitchensink module
> * Click on Compile. Upon completion, a target/<artifactId>-<version> folder is created
> * Right-click on project > Properties > Deployment Assembly
> * Click Add > folder > select target/<artifactId>-<version> click ok to complete
> * Right-click on project > Run As > Run on server
> * select JBoss AS7 / EAP, OK
> * Project deploys without errors
> * KitchenSink.html is displayed in browser, with the full form.
> Problem is, when the page is displayed, the following exceptions appear in the AS console :
> {noformat}
> 23:24:33,487 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016008: Starting weld service for deployment jesuisoula.war
> 23:24:33,784 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-2) configuring Errai CDI
> 23:24:33,789 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-2) Created Errai-CDI context: cbc75356-e760-43e2-9faf-e32025719b58
> 23:24:33,964 INFO [ErraiJNDI] (MSC service thread 1-2) searching to see if ErraiService is already bound...
> 23:24:34,167 INFO [org.jboss.errai.common.metadata.PackagingUtil] (Thread-70) identifying deployment type for uri: /D:/Dev/servers/jboss-eap-6.0-ER3/standalone/deployments/jesuisoula.war/WEB-INF/classes/
> 23:24:34,168 INFO [org.jboss.errai.common.metadata.PackagingUtil] (Thread-70) identifying deployment type for uri: /D:/Dev/servers/jboss-eap-6.0-ER3/standalone/deployments/jesuisoula.war/WEB-INF/lib/errai-bus-2.0-SNAPSHOT.jar/
> 23:24:34,169 INFO [org.jboss.errai.common.metadata.PackagingUtil] (Thread-70) identifying deployment type for uri: /D:/Dev/servers/jboss-eap-6.0-ER3/standalone/deployments/jesuisoula.war/WEB-INF/lib/errai-cdi-client-2.0-SNAPSHOT.jar/
> 23:24:34,170 INFO [org.jboss.errai.common.metadata.PackagingUtil] (Thread-70) identifying deployment type for uri: /D:/Dev/servers/jboss-eap-6.0-ER3/standalone/deployments/jesuisoula.war/WEB-INF/lib/errai-ioc-2.0-SNAPSHOT.jar/
> 23:24:34,171 INFO [org.jboss.errai.common.metadata.PackagingUtil] (Thread-70) identifying deployment type for uri: /D:/Dev/servers/jboss-eap-6.0-ER3/standalone/deployments/jesuisoula.war/WEB-INF/lib/errai-marshalling-2.0-SNAPSHOT.jar/
> 23:24:34,171 INFO [org.jboss.errai.common.metadata.PackagingUtil] (Thread-70) identifying deployment type for uri: /D:/Dev/servers/jboss-eap-6.0-ER3/standalone/deployments/jesuisoula.war/WEB-INF/lib/errai-tools-2.0-SNAPSHOT.jar/
> 23:24:34,172 INFO [org.jboss.errai.common.metadata.PackagingUtil] (Thread-70) identifying deployment type for uri: /D:/Dev/servers/jboss-eap-6.0-ER3/standalone/deployments/jesuisoula.war/WEB-INF/lib/errai-weld-integration-2.0-SNAPSHOT.jar/
> 23:24:34,206 INFO [org.jboss.errai.common.metadata.PackagingUtil] (Thread-70) identifying deployment type for uri: /D:/Dev/servers/jboss-eap-6.0-ER3/standalone/deployments/jesuisoula.war/WEB-INF/lib/errai-tools-2.0-SNAPSHOT.jar/
> 23:24:34,368 INFO [org.jboss.errai.common.metadata.PackagingUtil] (Thread-70) identifying deployment type for uri: /D:/Dev/servers/jboss-eap-6.0-ER3/standalone/deployments/jesuisoula.war/WEB-INF/lib/errai-cdi-client-2.0-SNAPSHOT.jar/
> 23:24:34,389 INFO [org.jboss.errai.common.metadata.PackagingUtil] (Thread-70) identifying deployment type for uri: /D:/Dev/servers/jboss-eap-6.0-ER3/standalone/deployments/jesuisoula.war/WEB-INF/lib/errai-bus-2.0-SNAPSHOT.jar/
> 23:24:34,692 INFO [org.jboss.errai.common.metadata.PackagingUtil] (Thread-70) identifying deployment type for uri: /D:/Dev/servers/jboss-eap-6.0-ER3/standalone/deployments/jesuisoula.war/WEB-INF/lib/errai-marshalling-2.0-SNAPSHOT.jar/
> 23:24:34,783 INFO [org.jboss.errai.common.metadata.PackagingUtil] (Thread-70) identifying deployment type for uri: /D:/Dev/servers/jboss-eap-6.0-ER3/standalone/deployments/jesuisoula.war/WEB-INF/lib/errai-weld-integration-2.0-SNAPSHOT.jar/
> 23:24:34,821 INFO [org.jboss.errai.common.metadata.PackagingUtil] (Thread-70) identifying deployment type for uri: /D:/Dev/servers/jboss-eap-6.0-ER3/standalone/deployments/jesuisoula.war/WEB-INF/classes/
> 23:24:34,833 INFO [org.jboss.errai.common.metadata.PackagingUtil] (Thread-70) identifying deployment type for uri: /D:/Dev/servers/jboss-eap-6.0-ER3/standalone/deployments/jesuisoula.war/WEB-INF/lib/errai-ioc-2.0-SNAPSHOT.jar/
> 23:24:34,898 INFO [org.jboss.errai.reflections.Reflections] (Thread-70) Reflections took 690 ms to scan 7 urls, producing 311 keys and 1031 values
> 23:24:34,899 INFO [org.jboss.errai.common.metadata.PackagingUtil] (Thread-70) identifying deployment type for uri: /D:/Dev/servers/jboss-eap-6.0-ER3/standalone/deployments/jesuisoula.war/WEB-INF/lib/errai-tools-2.0-SNAPSHOT.jar/
> 23:24:35,332 INFO [org.jboss.errai.common.metadata.PackagingUtil] (Thread-70) identifying deployment type for uri: /D:/Dev/servers/jboss-eap-6.0-ER3/standalone/deployments/jesuisoula.war/WEB-INF/lib/errai-cdi-client-2.0-SNAPSHOT.jar/
> 23:24:35,344 INFO [org.jboss.errai.common.metadata.PackagingUtil] (Thread-70) identifying deployment type for uri: /D:/Dev/servers/jboss-eap-6.0-ER3/standalone/deployments/jesuisoula.war/WEB-INF/lib/errai-bus-2.0-SNAPSHOT.jar/
> 23:24:35,505 INFO [org.jboss.errai.common.metadata.PackagingUtil] (Thread-70) identifying deployment type for uri: /D:/Dev/servers/jboss-eap-6.0-ER3/standalone/deployments/jesuisoula.war/WEB-INF/lib/errai-marshalling-2.0-SNAPSHOT.jar/
> 23:24:35,597 INFO [org.jboss.errai.common.metadata.PackagingUtil] (Thread-70) identifying deployment type for uri: /D:/Dev/servers/jboss-eap-6.0-ER3/standalone/deployments/jesuisoula.war/WEB-INF/lib/errai-weld-integration-2.0-SNAPSHOT.jar/
> 23:24:35,627 INFO [org.jboss.errai.common.metadata.PackagingUtil] (Thread-70) identifying deployment type for uri: /D:/Dev/servers/jboss-eap-6.0-ER3/standalone/deployments/jesuisoula.war/WEB-INF/classes/
> 23:24:35,637 INFO [org.jboss.errai.common.metadata.PackagingUtil] (Thread-70) identifying deployment type for uri: /D:/Dev/servers/jboss-eap-6.0-ER3/standalone/deployments/jesuisoula.war/WEB-INF/lib/errai-ioc-2.0-SNAPSHOT.jar/
> 23:24:35,703 INFO [org.jboss.errai.reflections.Reflections] (Thread-70) Reflections took 804 ms to scan 7 urls, producing 311 keys and 1031 values
> 23:24:35,815 INFO [org.jboss.errai.bus.server.service.bootstrap.OrderedBootstrap] (MSC service thread 1-2) Bootstrap Errai
> 23:24:35,816 INFO [org.jboss.errai.bus.server.service.bootstrap.OrderedBootstrap] (MSC service thread 1-2) Working directory: D:\Dev\servers\jboss-eap-6.0-ER3\bin
> 23:24:35,818 INFO [org.jboss.errai.bus.server.service.bootstrap.DefaultComponents] (MSC service thread 1-2) using dispatcher implementation: org.jboss.errai.bus.server.SimpleDispatcher
> 23:24:35,825 INFO [org.jboss.errai.bus.server.service.bootstrap.DefaultComponents] (MSC service thread 1-2) using session provider implementation: org.jboss.errai.bus.server.HttpSessionProvider
> 23:24:35,837 INFO [org.jboss.errai.bus.server.service.bootstrap.LoadExtensions] (MSC service thread 1-2) searching for Errai extensions ...
> 23:24:35,847 INFO [org.jboss.errai.bus.server.service.bootstrap.LoadExtensions] (MSC service thread 1-2) found extension org.jboss.errai.tools.monitoring.MonitorExtension
> 23:24:35,899 INFO [org.jboss.errai.bus.server.service.bootstrap.DiscoverServices] (MSC service thread 1-2) auto-discovery of services disabled.
> 23:24:35,900 INFO [org.jboss.errai.bus.server.service.bootstrap.BootstrapContext] (MSC service thread 1-2) Running deferred bootstrap tasks ...
> 23:24:35,900 INFO [org.jboss.errai.bus.server.service.bootstrap.OrderedBootstrap] (MSC service thread 1-2) Initialization complete
> 23:24:35,930 INFO [ErraiJNDI] (MSC service thread 1-2) found ErraiService bound at: java:global/ErraiService
> 23:24:35,947 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-2) Register RPC Endpoint: public@ApplicationScoped @Service class org.jboss.tools.gwt.kitchensink.controller.MemberServiceImpl(interface org.jboss.tools.gwt.kitchensink.client.shared.MemberService)
> 23:24:36,328 INFO [org.jboss.web] (MSC service thread 1-4) JBAS018210: Registering web context: /jesuisoula
> 23:24:36,335 INFO [org.jboss.as] (MSC service thread 1-5) JBAS015874: JBoss EAP 6.0.0.Beta1 (AS 7.1.0.Final-redhat-1) started in 20026ms - Started 195 of 268 services (72 services are passive or on-demand)
> 23:24:36,398 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "jesuisoula.war"
> 23:24:40,547 INFO [ErraiMarshalling] (http-localhost-127.0.0.1-8080-1) searching for marshaller class: org.jboss.errai.marshalling.server.impl.ServerMarshallingFactoryImpl
> 23:24:40,548 WARN [ErraiMarshalling] (http-localhost-127.0.0.1-8080-1) could not locate marshaller class. will attempt dynamic generation.
> 23:24:40,562 INFO [org.jboss.errai.marshalling.rebind.MarshallerGeneratorFactory] (http-localhost-127.0.0.1-8080-1) generating marshalling class...
> 23:24:40,622 INFO [org.jboss.errai.marshalling.rebind.MarshallerGeneratorFactory] (http-localhost-127.0.0.1-8080-1) Checking ErraiApp.properties for configured types ...
> 23:24:40,662 INFO [org.jboss.errai.marshalling.rebind.MarshallerGeneratorFactory] (http-localhost-127.0.0.1-8080-1) comprehended 59 classes
> 23:24:41,049 INFO [org.jboss.errai.marshalling.rebind.MarshallerGeneratorFactory] (http-localhost-127.0.0.1-8080-1) generated marshalling class in 486ms.
> 23:24:42,057 INFO [stdout] (http-localhost-127.0.0.1-8080-1) *** FAILED TO COMPILE MARSHALLER CLASS ***
> 23:24:42,058 INFO [stdout] (http-localhost-127.0.0.1-8080-1) *** Classpath Used: D:\Dev\servers\jboss-eap-6.0-ER3\standalone\deployments\jesuisoula.war\WEB-INF\classes;D:\Dev\servers\jboss-eap-6.0-ER3\standalone\deployments\jesuisoula.war\WEB-INF\lib\errai-bus-2.0-SNAPSHOT.jar;D:\Dev\servers\jboss-eap-6.0-ER3\standalone\deployments\jesuisoula.war\WEB-INF\lib\errai-cdi-client-2.0-SNAPSHOT.jar;D:\Dev\servers\jboss-eap-6.0-ER3\standalone\deployments\jesuisoula.war\WEB-INF\lib\errai-ioc-2.0-SNAPSHOT.jar;D:\Dev\servers\jboss-eap-6.0-ER3\standalone\deployments\jesuisoula.war\WEB-INF\lib\errai-marshalling-2.0-SNAPSHOT.jar;D:\Dev\servers\jboss-eap-6.0-ER3\standalone\deployments\jesuisoula.war\WEB-INF\lib\errai-tools-2.0-SNAPSHOT.jar;D:\Dev\servers\jboss-eap-6.0-ER3\standalone\deployments\jesuisoula.war\WEB-INF\lib\errai-weld-integration-2.0-SNAPSHOT.jar;D:\Dev\servers\jboss-eap-6.0-ER3\jboss-modules.jar;D:\Dev\servers\jboss-eap-6.0-ER3\modules\com\sun\jsf-impl\main\jsf-impl-2.1.5-redhat-1.jar;D:\Dev\servers\jboss-eap-6.0-ER3\modules\org\jboss\as\weld\main\jboss-as-weld-7.1.0.Final-redhat-1.jar;D:\Dev\servers\jboss-eap-6.0-ER3\jboss-modules.jar
> 23:24:42,066 INFO [stdout] (http-localhost-127.0.0.1-8080-1) D:\Dev\servers\jboss-eap-6.0-ER3\standalone\deployments\jesuisoula.war\WEB-INF\classes\org\jboss\tools\gwt\kitchensink\client\shared\Member.class: warning: Cannot find annotation method 'uniqueConstraints()' in type 'javax.persistence.Table': class file for javax.persistence.Table not found
> 23:24:42,071 INFO [stdout] (http-localhost-127.0.0.1-8080-1) D:\Dev\servers\jboss-eap-6.0-ER3\standalone\deployments\jesuisoula.war\WEB-INF\classes\org\jboss\tools\gwt\kitchensink\client\shared\Member.class: warning: Cannot find annotation method 'columnNames()' in type 'javax.persistence.UniqueConstraint': class file for javax.persistence.UniqueConstraint not found
> 23:24:42,076 INFO [stdout] (http-localhost-127.0.0.1-8080-1) D:\Dev\servers\jboss-eap-6.0-ER3\standalone\deployments\jesuisoula.war\WEB-INF\classes\org\jboss\tools\gwt\kitchensink\client\shared\Member.class: warning: Cannot find annotation method 'min()' in type 'javax.validation.constraints.Size': class file for javax.validation.constraints.Size not found
> 23:24:42,081 INFO [stdout] (http-localhost-127.0.0.1-8080-1) D:\Dev\servers\jboss-eap-6.0-ER3\standalone\deployments\jesuisoula.war\WEB-INF\classes\org\jboss\tools\gwt\kitchensink\client\shared\Member.class: warning: Cannot find annotation method 'max()' in type 'javax.validation.constraints.Size'
> 23:24:42,086 INFO [stdout] (http-localhost-127.0.0.1-8080-1) D:\Dev\servers\jboss-eap-6.0-ER3\standalone\deployments\jesuisoula.war\WEB-INF\classes\org\jboss\tools\gwt\kitchensink\client\shared\Member.class: warning: Cannot find annotation method 'regexp()' in type 'javax.validation.constraints.Pattern': class file for javax.validation.constraints.Pattern not found
> 23:24:42,092 INFO [stdout] (http-localhost-127.0.0.1-8080-1) D:\Dev\servers\jboss-eap-6.0-ER3\standalone\deployments\jesuisoula.war\WEB-INF\classes\org\jboss\tools\gwt\kitchensink\client\shared\Member.class: warning: Cannot find annotation method 'message()' in type 'javax.validation.constraints.Pattern'
> 23:24:42,097 INFO [stdout] (http-localhost-127.0.0.1-8080-1) D:\Dev\servers\jboss-eap-6.0-ER3\standalone\deployments\jesuisoula.war\WEB-INF\classes\org\jboss\tools\gwt\kitchensink\client\shared\Member.class: warning: Cannot find annotation method 'min()' in type 'javax.validation.constraints.Size'
> 23:24:42,103 INFO [stdout] (http-localhost-127.0.0.1-8080-1) D:\Dev\servers\jboss-eap-6.0-ER3\standalone\deployments\jesuisoula.war\WEB-INF\classes\org\jboss\tools\gwt\kitchensink\client\shared\Member.class: warning: Cannot find annotation method 'max()' in type 'javax.validation.constraints.Size'
> 23:24:42,110 INFO [stdout] (http-localhost-127.0.0.1-8080-1) D:\Dev\servers\jboss-eap-6.0-ER3\standalone\deployments\jesuisoula.war\WEB-INF\classes\org\jboss\tools\gwt\kitchensink\client\shared\Member.class: warning: Cannot find annotation method 'fraction()' in type 'javax.validation.constraints.Digits': class file for javax.validation.constraints.Digits not found
> 23:24:42,117 INFO [stdout] (http-localhost-127.0.0.1-8080-1) D:\Dev\servers\jboss-eap-6.0-ER3\standalone\deployments\jesuisoula.war\WEB-INF\classes\org\jboss\tools\gwt\kitchensink\client\shared\Member.class: warning: Cannot find annotation method 'integer()' in type 'javax.validation.constraints.Digits'
> 23:24:42,124 INFO [stdout] (http-localhost-127.0.0.1-8080-1) D:\Dev\servers\jboss-eap-6.0-ER3\standalone\deployments\jesuisoula.war\WEB-INF\classes\org\jboss\tools\gwt\kitchensink\client\shared\Member.class: warning: Cannot find annotation method 'name()' in type 'javax.persistence.Column': class file for javax.persistence.Column not found
> 23:24:42,128 INFO [stdout] (http-localhost-127.0.0.1-8080-1) error: Bad service configuration file, or exception thrown while constructing Processor object: javax.annotation.processing.Processor: Provider org.jboss.errai.common.rebind.ModuleAnnotationProcessor not found
> 23:24:42,129 ERROR [ErraiMarshalling] (http-localhost-127.0.0.1-8080-1) failed to load static marshallers: java.lang.NullPointerException
> at org.jboss.errai.marshalling.server.MappingContextSingleton.loadPrecompiledMarshallers(MappingContextSingleton.java:98) [errai-marshalling-2.0-SNAPSHOT.jar:2.0-SNAPSHOT]
> at org.jboss.errai.marshalling.server.MappingContextSingleton.<clinit>(MappingContextSingleton.java:78) [errai-marshalling-2.0-SNAPSHOT.jar:2.0-SNAPSHOT]
> at org.jboss.errai.bus.server.io.MessageFactory.getParts(MessageFactory.java:109) [errai-bus-2.0-SNAPSHOT.jar:2.0-SNAPSHOT]
> at org.jboss.errai.bus.server.io.MessageFactory.createCommandMessage(MessageFactory.java:93) [errai-bus-2.0-SNAPSHOT.jar:2.0-SNAPSHOT]
> at org.jboss.errai.bus.server.servlet.DefaultBlockingServlet.doPost(DefaultBlockingServlet.java:117) [errai-bus-2.0-SNAPSHOT.jar:2.0-SNAPSHOT]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:754) [jboss-servlet-api_3.0_spec-1.0.0.Final-redhat-1.jar:1.0.0.Final-redhat-1]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.0.Final-redhat-1.jar:1.0.0.Final-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.10.Final-redhat-1.jar:]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.10.Final-redhat-1.jar:]
> at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62) [weld-core-1.1.5.AS71.Final-redhat-1.jar:2012-02-22 16:46]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.10.Final-redhat-1.jar:]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.10.Final-redhat-1.jar:]
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.10.Final-redhat-1.jar:]
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.10.Final-redhat-1.jar:]
> at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1]
> at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:154) [jboss-as-web-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.10.Final-redhat-1.jar:]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.10.Final-redhat-1.jar:]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.10.Final-redhat-1.jar:]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.10.Final-redhat-1.jar:]
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.10.Final-redhat-1.jar:]
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.10.Final-redhat-1.jar:]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.10.Final-redhat-1.jar:]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_31]
> 23:24:42,147 INFO [ErraiMarshalling] (http-localhost-127.0.0.1-8080-1) failing over to dynamic marshallers ... performance may be affected.
> {noformat}
> It turns out some files are missing from the deployment folder :
> * WEB-INF/classes/classlist.mf
> * WEB-INF/classes/org/jboss/errai/**
> These files should be created under the project /target/classes folder in the first place, during GWT Compile, as would mvn package do.
--
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, 9 months
[JBoss JIRA] (JBIDE-13209) Need to add ESB 4.12 option with constraints
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13209?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-13209:
----------------------------------
Fix Version/s: 4.0.2.Final
(was: 4.0.1.Final)
> Need to add ESB 4.12 option with constraints
> --------------------------------------------
>
> Key: JBIDE-13209
> URL: https://issues.jboss.org/browse/JBIDE-13209
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: esb
> Reporter: Tom Cunningham
> Assignee: Brian Fitzpatrick
> Fix For: 3.3.2.Final, 4.0.2.Final, 4.1.0.Alpha1
>
> Attachments: JBIDE-13209.patch
>
>
> SOA-P 5.3.1 is coming out soon and will require an ESB "4.12" option to be added to the ESB versions.
> Additionally, it may or may not have a new jUDDI version, which would require a different constraint to verify the AS has ESB 4.12 - or a removal of the constraints altogether.
--
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, 9 months
[JBoss JIRA] (JBIDE-12347) Unable to invoke SOAP web service when using Java 7
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12347?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-12347:
----------------------------------
Fix Version/s: 4.0.2.Final
(was: 4.0.1.Final)
> Unable to invoke SOAP web service when using Java 7
> ---------------------------------------------------
>
> Key: JBIDE-12347
> URL: https://issues.jboss.org/browse/JBIDE-12347
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Webservices
> Affects Versions: 3.3.1.Final
> Environment: Java 7
> Reporter: Jaroslav Jankovič
> Assignee: Brian Fitzpatrick
> Labels: upstream
> Fix For: 4.0.2.Final
>
>
> I am unable to invoke SOAP web service in WS Tester from http://www.webservicex.net/BibleWebservice.asmx?WSDL.
> In Response Body of WS Tester I got the message:
> {code}
> javax.xml.ws.soap.SOAPFaultException: System.Web.Services.Protocols.SoapException: Server did not recognize the value of HTTP Header SOAPAction: .
> at System.Web.Services.Protocols.Soap11ServerProtocolHelper.RouteRequest()
> at System.Web.Services.Protocols.SoapServerProtocol.RouteRequest(SoapServerMessage message)
> at System.Web.Services.Protocols.SoapServerProtocol.Initialize()
> at System.Web.Services.Protocols.ServerProtocolFactory.Create(Type type, HttpContext context, HttpRequest request, HttpResponse response, Boolean& abortProcessing)
> {code}
> In error log I got the error:
> {code}
> java.lang.Exception: javax.xml.ws.soap.SOAPFaultException: System.Web.Services.Protocols.SoapException: Server did not recognize the value of HTTP Header SOAPAction: .
> at System.Web.Services.Protocols.Soap11ServerProtocolHelper.RouteRequest()
> at System.Web.Services.Protocols.SoapServerProtocol.RouteRequest(SoapServerMessage message)
> at System.Web.Services.Protocols.SoapServerProtocol.Initialize()
> at System.Web.Services.Protocols.ServerProtocolFactory.Create(Type type, HttpContext context, HttpRequest request, HttpResponse response, Boolean& abortProcessing)
> at org.jboss.tools.ws.ui.utils.JAXWSTester2.doTest(JAXWSTester2.java:205)
> at org.jboss.tools.ws.ui.views.JAXRSWSTestView2.handleWSTest(JAXRSWSTestView2.java:1803)
> at org.jboss.tools.ws.ui.views.JAXRSWSTestView2.access$34(JAXRSWSTestView2.java:1789)
> at org.jboss.tools.ws.ui.views.JAXRSWSTestView2$21.run(JAXRSWSTestView2.java:1706)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> Caused by: javax.xml.ws.soap.SOAPFaultException: System.Web.Services.Protocols.SoapException: Server did not recognize the value of HTTP Header SOAPAction: .
> at System.Web.Services.Protocols.Soap11ServerProtocolHelper.RouteRequest()
> at System.Web.Services.Protocols.SoapServerProtocol.RouteRequest(SoapServerMessage message)
> at System.Web.Services.Protocols.SoapServerProtocol.Initialize()
> at System.Web.Services.Protocols.ServerProtocolFactory.Create(Type type, HttpContext context, HttpRequest request, HttpResponse response, Boolean& abortProcessing)
> at com.sun.xml.internal.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:178)
> at com.sun.xml.internal.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:111)
> at com.sun.xml.internal.ws.client.dispatch.DispatchImpl$DispatchAsyncInvoker$1.onCompletion(DispatchImpl.java:450)
> at com.sun.xml.internal.ws.client.Stub$1.onCompletion(Stub.java:381)
> at com.sun.xml.internal.ws.api.pipe.Fiber.completionCheck(Fiber.java:502)
> at com.sun.xml.internal.ws.api.pipe.Fiber.run(Fiber.java:420)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:722)
> {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, 9 months
[JBoss JIRA] (JBIDE-13209) Need to add ESB 4.12 option with constraints
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13209?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-13209:
----------------------------------
Fix Version/s: 4.0.1.Final
(was: 4.0.x)
> Need to add ESB 4.12 option with constraints
> --------------------------------------------
>
> Key: JBIDE-13209
> URL: https://issues.jboss.org/browse/JBIDE-13209
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: esb
> Reporter: Tom Cunningham
> Assignee: Brian Fitzpatrick
> Fix For: 3.3.2.Final, 4.0.1.Final, 4.1.0.Alpha1
>
> Attachments: JBIDE-13209.patch
>
>
> SOA-P 5.3.1 is coming out soon and will require an ESB "4.12" option to be added to the ESB versions.
> Additionally, it may or may not have a new jUDDI version, which would require a different constraint to verify the AS has ESB 4.12 - or a removal of the constraints altogether.
--
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, 9 months