[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-8461) Editing AS Launch Configuration -Djava.library.path

[Rob Stryker (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-8461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12594092#comment-12594092 ] 

Rob Stryker commented on JBIDE-8461:
------------------------------------

It seems the code during POJP launches that adds the library path only applies when launching a "project".  Since a server is not a project in eclipse, this batch of code never gets executed. I basically have two options here:

1) I can fix the code that was broken before, so that modifying the parameter actually works properly
2) I could try to execute the same code (adding to library param) based on the classpath entries of projects already deployed on the server.

Item 1 obviously is the easiest fix. But if item 2 has some awesome benefits, it would be worth it entirely. Unfortunately, item 2 has severe drawbacks. Imagine a workspace with 3 web projects. Each web project demands native code from a different folder. Depending on which are deployed to the server at the time the server starts up would change the flag. The good side here is that the values the user hard-sets in the launch config himself would override this logic. But it also has bad sides, specifically, that if you start the server with zero modules deployed onto it, none of those native folders make it on during the server launch. 

I think this would confuse a lot of users, how depending on what module is already deployed could change the behaviour so greatly. Users often remove and re-add modules all the time, and they also often restart servers. A user would now need to pay careful attention to which modules are published before startup.  Also, this would make the usecase of a clean startup (0 deployed modules) and then publishing afterwards impossible, since the server would have already started with none of the 3 apps' native code on the library path. 

I will make a patch that moves the behaviour here more in line with that of generic POJP launches, but I cannot move it entirely. Patch will be ready in a short while. 

> Editing AS Launch Configuration -Djava.library.path
> ---------------------------------------------------
>
>                 Key: JBIDE-8461
>                 URL: https://issues.jboss.org/browse/JBIDE-8461
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS
>    Affects Versions: 3.2.0.CR1
>         Environment: Win7 64-bit, 32-bit 1.6 JVM
>            Reporter: Burr Sutter
>            Assignee: Rob Stryker
>              Labels: as_backwards
>             Fix For: 3.2.1, 3.3.0.M1
>
>         Attachments: native_lib_editing1.png, native_lib_editing2.png
>
>
> It seems that you can not make changes to -Djava.library.path on the Launch configuration properties.  In addition, dropping your native libs into this directory are not recognized when the server is launched - I am trying to add the JBoss Native tc-native1.dll to my AS6
> The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: D:\servers\jboss-6.0.0.Final\bin\native;

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira