December 2013 - jbdevstudio-users

Bug found - choosing configuration in JBoss runtime configuration window

by jbdevstudio-users＠lists.jboss.org

Hello, I've been trying to change configuration from default to all in my runtime, but each time I select "all" from the list and click "OK", I go back to this window and still see that "default" is choosen. Misleading fact is, that configuration was indeed changed - when I check launch configuration (server overwiew) I see that the parameters used to start Jboss has changed - now I have my "--configuration=all". But still, to check which configuration is used in which runtime, I need to have at least one server with given runtime, and then check these launch parameters, because indicator in runtime configuration is lying. I wanted to register a new bug, but I'm a newbie here, and I have no idea how to do it {emoticon:class=jive_macro jive_emote|src=https://community.jboss.org/6.0.3.60ddddd/images/emoticons... So in some way, this post may be read as - can anyone tell me, how to register a new bug? Posted by forums Original post: https://community.jboss.org/message/850301#850301

11 years

1
1
0 / 0

Enterprise Java Newscast - Episode 17 - November 2013

by jbdevstudio-users＠lists.jboss.org

Hello, I am pleased to announce a new episode of the Enterprise Java Newscast on JSFCentral.com. The Enterprise Java Newscast, hosted by Kito D. Mann, Ian Hlavats, and Daniel Hinojosa, is a monthly podcast that covers the latest headlines in the world of Enterprise Java development. In this episode, Kito, Ian, and Daniel cover new releases from Spring, PrimeFaces ICEsoft, JBoss, IBM, Oracle, Apache, and TypeSafe. They also discuss Oracle's decision to drop support for GlassFish, and RebelLabs' Decision Maker's Guide to Java Web Frameworks. Read the newscast here: http://blogs.jsfcentral.com/JSFNewscast/entry/enterprise_java_newscast_ep... --- Kito D. Mann | @kito99 | Author, JSF in Action Virtua, Inc. | http://www.virtua.com | JSF/Java EE training and consulting http://www.JSFCentral.com – JavaServer Faces FAQ, news, and info | @jsfcentral - Listen to the latest headlines in the JSF and Java EE newscast:http://blogs.jsfcentral.com/JSFNewscast/ - Sign up for the JSFCentral Newsletter: http://oi.vresp.com/?fid=ac048d0e17 Posted by forums Original post: https://community.jboss.org/message/849153#849153

11 years

1
0
0 / 0

jboss-javaee6-webapp unresolved dependencies

by jbdevstudio-users＠lists.jboss.org

I just dowloaded JBoss Developer Studio 7 and created a jboss-javaee6-webapp maven project. But I am not able to build: SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. [INFO] Scanning for projects... Downloading: http://repo.maven.apache.org/maven2/org/jboss/bom/eap/jboss-javaee-6.0-wi... Downloading: http://repo.maven.apache.org/maven2/org/jboss/bom/eap/jboss-javaee-6.0-wi... [ERROR] The build could not read 1 project -> [Help 1] [ERROR] [ERROR] The project org.jboss.tools.examples:jboss-javaee6-webapp:0.0.1-SNAPSHOT (C:\Users\s.martinelli\workspace\jboss-javaee6-webapp\pom.xml) has 15 errors [ERROR] Non-resolvable import POM: Could not find artifact org.jboss.bom.eap:jboss-javaee-6.0-with-tools:pom:6.2.0-build-5 in central (http://repo.maven.apache.org/maven2) @ line 71, column 25 -> [Help 2] [ERROR] Non-resolvable import POM: Could not find artifact org.jboss.bom.eap:jboss-javaee-6.0-with-hibernate:pom:6.2.0-build-5 in central (http://repo.maven.apache.org/maven2) @ line 78, column 25 -> [Help 2] [ERROR] 'dependencies.dependency.version' for javax.enterprise:cdi-api:jar is missing. @ line 95, column 21 [ERROR] 'dependencies.dependency.version' for org.jboss.spec.javax.annotation:jboss-annotations-api_1.1_spec:jar is missing. @ line 103, column 21 [ERROR] 'dependencies.dependency.version' for org.jboss.spec.javax.ws.rs:jboss-jaxrs-api_1.1_spec:jar is missing. @ line 111, column 21 [ERROR] 'dependencies.dependency.version' for org.hibernate.javax.persistence:hibernate-jpa-2.0-api:jar is missing. @ line 119, column 21 [ERROR] 'dependencies.dependency.version' for org.jboss.spec.javax.ejb:jboss-ejb-api_3.1_spec:jar is missing. @ line 127, column 21 [ERROR] 'dependencies.dependency.version' for org.hibernate:hibernate-validator:jar is missing. @ line 136, column 21 [ERROR] 'dependencies.dependency.version' for org.jboss.spec.javax.faces:jboss-jsf-api_2.1_spec:jar is missing. @ line 150, column 21 [ERROR] 'dependencies.dependency.version' for org.hibernate:hibernate-jpamodelgen:jar is missing. @ line 160, column 21 [ERROR] 'dependencies.dependency.version' for org.hibernate:hibernate-validator-annotation-processor:jar is missing. @ line 168, column 21 [ERROR] 'dependencies.dependency.version' for junit:junit:jar is missing. @ line 175, column 21 [ERROR] 'dependencies.dependency.version' for org.jboss.arquillian.junit:arquillian-junit-container:jar is missing. @ line 184, column 21 [ERROR] 'dependencies.dependency.version' for org.jboss.arquillian.protocol:arquillian-protocol-servlet:jar is missing. @ line 190, column 21 [ERROR] 'dependencies.dependency.version' for org.jboss.as:jboss-as-arquillian-container-remote:jar is missing. @ line 266, column 29 [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException [ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException Posted by forums Original post: https://community.jboss.org/message/848378#848378

11 years

1
1
0 / 0

Toolwiz cleaner vs Clean Master, which one do you prefer?

by jbdevstudio-users＠lists.jboss.org

Undoubtedly, nowadays, these two apps are the most eyes-catching android cleaner apps. Their simplicity and multi-language are the crux to capture people’s heart. After trying both, I finally choose Toolwiz Cleaner. If you tell me why, I’d tell you that its smaller memory, cute widget and heartbeat test win my heart. If you are more fond of Clean Master, what allures you to choose it? Posted by forums Original post: https://community.jboss.org/message/848347#848347

11 years

1
0
0 / 0

JBoss Knowledge Base Builder - NullPointerException (VirtualResource.getProjectRelativePaths(...))

by jbdevstudio-users＠lists.jboss.org

I am unable to get any content assistance in my xhtml pages, and I believe it is related to the error I get when building the project: Platform: Eclipse Java EE Version: Kepler Service Release 1 Build id: 20130919-8019 JBoss Tools: I am not sure which plugin versions are useful but here are some important looking ones: JBoss AS Core Plug-in - 2.4.100.Final-v20130717-0846-B106 JBoss Tools Common - 3.5.1.Final-v20130717-0450-B102 Application Server Interface Core Plug-in - 2.4.100.Final-v20130717-0846-B106 Context and Dependency Injection Core - 1.5.0.Final-v20130717-0417-B93 El Plug-in - 3.5.1.Final-v20130717-0450-B102 A popup appears that says: ---------------------------------------------------------------------------------------------------------------- Problem Occured 'Building workspace' has encountered a problem. Errors occured during the build. Details: Errors occurred during the build. Errors running builder 'JBoss Knowledge Base Builder' on project 'Web-2.23'. java.lang.NullPointerException ---------------------------------------------------------------------------------------------------------------- Stacktrace: !ENTRY org.eclipse.core.resources 4 75 2013-12-03 15:24:15.443 !MESSAGE Errors occurred during the build. !SUBENTRY 1 org.jboss.tools.jst.web.kb 4 75 2013-12-03 15:24:15.443 !MESSAGE Errors running builder 'JBoss Knowledge Base Builder' on project 'Web-2.23'. !STACK 0 java.lang.NullPointerException at org.eclipse.wst.common.componentcore.internal.resources.VirtualResource.getProjectRelativePaths(VirtualResource.java:119) at org.eclipse.wst.common.componentcore.internal.resources.VirtualResource.getProjectRelativePath(VirtualResource.java:154) at org.eclipse.wst.common.componentcore.internal.resources.VirtualResource.getWorkspaceRelativePath(VirtualResource.java:109) at org.jboss.tools.jst.web.model.helpers.InnerModelHelper.getWebInfPath(InnerModelHelper.java:91) at org.jboss.tools.jst.web.model.helpers.InnerModelHelper.createXModel(InnerModelHelper.java:46) at org.jboss.tools.jst.web.kb.internal.scanner.ClassPathMonitor.init(ClassPathMonitor.java:60) at org.jboss.tools.jst.web.kb.internal.KbProject.setProject(KbProject.java:202) at org.eclipse.core.internal.resources.NatureManager.createNature(NatureManager.java:233) at org.eclipse.core.internal.resources.Project.getNature(Project.java:448) at org.jboss.tools.jst.web.kb.KbProjectFactory.getKbProject(KbProjectFactory.java:67) at org.jboss.tools.jst.web.kb.KbProjectFactory.getKbProject(KbProjectFactory.java:34) at org.jboss.tools.jst.web.kb.internal.scanner.ClassPathMonitor.getKbProjects(ClassPathMonitor.java:201) at org.jboss.tools.jst.web.kb.internal.scanner.ClassPathMonitor.hasToUpdateProjectDependencies(ClassPathMonitor.java:166) at org.jboss.tools.jst.web.kb.internal.scanner.ClassPathMonitor.build(ClassPathMonitor.java:214) at org.jboss.tools.jst.web.kb.internal.KbBuilder.build(KbBuilder.java:102) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:733) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246) at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:299) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:302) at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:358) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:381) at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) Posted by forums Original post: https://community.jboss.org/message/848128#848128

11 years

1
1
0 / 0

VM arguments getting replaced

by jbdevstudio-users＠lists.jboss.org

Hi, I have install Jboss Developer Studio plugin in my eclipse Kepler. After installation, I removed all the VM arguments except -server paramter. my final VM arguments from server configuration looks as follows -server -Xms128m -Xmx2G -XX:MaxPermSize=512m Image:Modified.png But once I save the configuration and close the window, The VM arguments are getting replaced to default except -server parameter as below -server -Xms128m -Xmx2G -XX:MaxPermSize=512m -Djboss.home.dir=D:/jboss-standalone-config -Dorg.jboss.boot.log.file=D:/jboss-standalone-config/standalone/log/boot.log -Dlogging.configuration=file:/D:/jboss-standalone-config/standalone/configuration/logging.properties Image:Modified1.png Is there an existing bug with Jboss Developer studio server configuration? Thanks, Surendran Posted by forums Original post: https://community.jboss.org/message/847875#847875

11 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

jbdevstudio-users December 2013