Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Couple of unrelated, but hopefully useful commits... #25

Closed
wants to merge 2 commits into from

Conversation

mathomas
Copy link

  • Allow extra libraries to cause a GF restart after installation. This is specifically useful when setting up a custom realm. The restart can be requested for specific libraries by specifying "requires_restart" in the library configuration hash (defaults to false, so can be omitted):
'extra_libraries' => {
    realm' => {
    'type' => 'common', 
    'url' => 'https://s3.amazonaws.com/my_bucket/myrealm.jar',
    'requires_restart' => true
}, . . .
  • Comment-out what appears to be some sort of prior fix in domain.rb, but that actually borks deployment under Glassfish 4. This is mainly to start a conversation (and because I had pushed two commits and GitHub apparently doesn't let you cherry pick commits for pull requests ;-)).

Mike Thomas added 2 commits February 11, 2014 15:13
… false), and carry out the restart if so specified.
…tampered with' error under GF4. Not sure what the removal will break, but not being able to deploy is possibly worse(?).
@@ -279,19 +279,19 @@ def replace_in_domain_file(key, value)

# There is a bug in the Glassfish 4 domain creation that puts the master-password in the wrong spot. This copies it back.
#file "#{domain_dir_path}/master-password" do
ruby_block "copy master-password" do
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This block of code seems to be what perturbs GF at deployment time. At this point I don't know why it causes a deployment problem, but for me, if it's commented out I can deploy.

I also don't understand what the side-effect of NOT having this code is. So please treat this commit as a "conversation starter".

@realityforge
Copy link
Owner

I have manually merged in the changes to the LWRP. Thanks!

The other outstanding changes that I have yet to get to that you have submitted include the branches

I will try to get to them soon but it needs a bunch of testing across our own infrastructure to see the impact.

Thanks again!

@mathomas
Copy link
Author

No problem. Happy to contribute. The restart flag has been working well for me thus far. When I first added it I thought it would only be useful for custom realm libraries, but today I needed it when I added the mysql JAR file to a different GF project. It was the only extra JAR that I needed to include, and didn't think I needed the flag. Well, the deployment didn't work. I went and added the restart flag to that lib, and everything started fine.

Thanks for creating this thing. I'm happy to contribute in whatever small way I can.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants