[JBoss JIRA] Created: (JBIDE-3975) Make the selector path separator configurable
by Maurice Zeijen (JIRA)
Make the selector path separator configurable
---------------------------------------------
Key: JBIDE-3975
URL: https://jira.jboss.org/jira/browse/JBIDE-3975
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: smooks
Affects Versions: 3.0.0.CR2
Reporter: Maurice Zeijen
In Smooks it is possible to use a white space or a slash as selector path separator. Since Smooks 1.1 the slash is preferred by the Smooks developer team because it is more concise to Xpath . But it is off course up to the user to decide which separator they want to use.
Maybe a configuration option could be created to be able to set the selector path separator. This options should be set globally but should be override able per project.
In my opinion (as Smooks development team member ;) ), the slash should be the preferred separator.
--
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
17 years, 1 month
[JBoss JIRA] Created: (JBIDE-4469) Warning message or other - On MS Windows Systems, Periods in Seam Project Names Cause Deploy Errors
by Jeff Wexler (JIRA)
Warning message or other - On MS Windows Systems, Periods in Seam Project Names Cause Deploy Errors
---------------------------------------------------------------------------------------------------
Key: JBIDE-4469
URL: https://jira.jboss.org/jira/browse/JBIDE-4469
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JBossAS, Seam
Affects Versions: 3.0.1.GA
Environment: Seam 2.1.2.GA. JBoss AS 5.1.0.GA. Eclipse 3.4.2 Build Id: M20090211-1700. JBoss Tools 3.0.1.GA. Windows 2003 Server native Japanese version. Postgresql 8.3.7
Reporter: Jeff Wexler
Priority: Minor
On Windows Server 2003, using a project name with a period often causes issues.
For example, to easily illustrate:
Jboss AS stopped.
ant explode booking example (using ds configured to Postgresql in my case).
Rename ear to com.mysite.ear
Rename jar to com.mysite.jar
Rename war to com.mysite.war
Update application.xml with the changes.
Change com.mysite.war\WEB-INF\components.xml such that jndi-pattern changed to "com.mysite/#{ejbName}/local"
Change com.mysite.jar\META-INF\persistence.xml such that jta-data-source changed to java:/com.mysiteDatasource
Rename jboss-seam-booking-ds.xml to com.mysite-ds.xml
Change com.mysite-ds.xml such that jndi-name changed to com.mysiteDatasource
Then start Jboss default server, get deploy errors.
Stop JBoss AS.
Then make all the above changes but without the period in the file names and values such that commysite is used instead.
Then start JBoss AS, it works.
If stop JBoss AS, and change them all back to with the period again such that com.mysite again. Then will not work.
If change back to commysite again without the period works again.
I've verified this several times in somewhat amazement.
I say somewhat because period in folder names within c:\Inetpub\wwwroot also causes issues with IIS and thus is clearly a Microsoft problem.
If initially create a seam web project using JBoss tools with a period, it WILL work. However, after starting to use the project and make changes (i.e., simple stuff which should not cause issues), re-build, etc. eventually, get the strange errors as in the case above.
I recomend some kind of warning or other message or means to warn users using Windows to avoid including periods in the project names. It would save some people a lot of wasted time. I would also suggest adding a comment in an appropriate location in the related reference documents (Seam Tools and perhaps Seam Reference doc).
--
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
17 years, 1 month
[JBoss JIRA] Created: (JBDS-742) "Initializing Java Tooling" java.lang.NullPointerException when opening a 3.0.0.GA-R200903141626-H5 project with JDBS 2.0.0.GA
by Marc Tille (JIRA)
"Initializing Java Tooling" java.lang.NullPointerException when opening a 3.0.0.GA-R200903141626-H5 project with JDBS 2.0.0.GA
------------------------------------------------------------------------------------------------------------------------------
Key: JBDS-742
URL: https://jira.jboss.org/jira/browse/JBDS-742
Project: Developer Studio
Issue Type: Bug
Affects Versions: 2.0.0.GA
Environment: Mac OS X 10.5.7 MacBook Alu
Reporter: Marc Tille
Priority: Minor
As requested by Max Andersen
The problem was an "Initializing Java Tooling" java.lang.NullPointerException error after starting JDBS 2.0.0.GA (see JBoss Forum link for details if needed) when opening a project created with
Version: 3.4.2
Build id: M20090211-1700
3.0.0.GA-R200903141626-H5
on JBoss Developer Studio
Version: 2.0.0.GA
Build id: R200903141247-H4
Here is the full .log stacktrace :
!SESSION 2009-05-29 14:17:24.930 -----------------------------------------------
eclipse.buildId=M20090211-1700
java.version=1.5.0_16
java.vendor=Apple Inc.
BootLoader constants: OS=macosx, ARCH=x86, WS=carbon, NL=en_US
Framework arguments: -keyring /Users/zzkj/.eclipse_keyring -showlocation
Command-line arguments: -os macosx -ws carbon -arch x86 -keyring /Users/zzkj/.eclipse_keyring -consoleLog -showlocation
!ENTRY org.eclipse.core.jobs 4 2 2009-05-29 14:17:44.812
!MESSAGE An internal error occurred during: "Initializing Java Tooling".
!STACK 0
java.lang.NullPointerException
at org.drools.eclipse.util.DroolsRuntimeManager.getDroolsRuntimeJars(DroolsRuntimeManager.java:187)
at org.drools.eclipse.util.DroolsClasspathContainer.getJarNames(DroolsClasspathContainer.java:71)
at org.drools.eclipse.util.DroolsClasspathContainer.createDroolsLibraryEntries(DroolsClasspathContainer.java:52)
at org.drools.eclipse.util.DroolsClasspathContainer.getClasspathEntries(DroolsClasspathContainer.java:32)
at org.eclipse.jdt.internal.core.JavaModelManager.containerPutIfInitializingWithSameEntries(JavaModelManager.java:564)
at org.eclipse.jdt.internal.core.SetContainerOperation.executeOperation(SetContainerOperation.java:49)
at org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:716)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800)
at org.eclipse.jdt.internal.core.JavaModelOperation.runOperation(JavaModelOperation.java:782)
at org.eclipse.jdt.core.JavaCore.setClasspathContainer(JavaCore.java:4616)
at org.drools.eclipse.util.DroolsClasspathContainerInitializer.initialize(DroolsClasspathContainerInitializer.java:15)
at org.eclipse.jdt.internal.core.JavaModelManager.initializeContainer(JavaModelManager.java:2483)
at org.eclipse.jdt.internal.core.JavaModelManager$13.run(JavaModelManager.java:2413)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800)
at org.eclipse.jdt.internal.core.JavaModelManager.initializeAllContainers(JavaModelManager.java:2429)
at org.eclipse.jdt.internal.core.JavaModelManager.getClasspathContainer(JavaModelManager.java:1697)
at org.eclipse.jdt.core.JavaCore.initializeAfterLoad(JavaCore.java:3311)
at org.eclipse.jdt.internal.ui.InitializeAfterLoadJob$RealJob.run(InitializeAfterLoadJob.java:35)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
--
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
17 years, 1 month