Cargo

When building the JBoss configuration, all files should be copied locally rather than being linked to

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Critical Critical
  • Resolution: Won't Fix
  • Affects Version/s: 0.8
  • Fix Version/s: None
  • Component/s: JBoss
  • Labels:
    None
  • Number of attachments :
    0

Description

When building the JBoss configuration, files are being linked to from different places, here are some examples:

  • container home for the base configuration and container files: libs, etc ...
  • configuration home for overriden descriptors
  • deployable locations

This is efficient when it comes to performance, but it is not appropriate when it comes to actually build a zip of the configuration. What's more, it is the only container that behaves like that.

All files should be copied localy in a single place.

Thanx

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
I Nyoman Winardi added a comment -

I'm not sure we really need to copy all the resources.
It will take a significant amount of space if we copy all of it.
What do you think?
Should we go for this?

Show
I Nyoman Winardi added a comment - I'm not sure we really need to copy all the resources. It will take a significant amount of space if we copy all of it. What do you think? Should we go for this?
Hide
Permalink
Cédric Vidal added a comment -

Hi,

Well I think that the files should be copied, first of all for the sake of consistency with the other containers, and secondly because as it is right now, it is absolutly impossible to use Cargo to build a JBoss configuration, which is precisely what I need Cargo to do

Anyway, to make everybody happy, one could add a configuration parameter which would enable to tell whether one wants to have all the files copied or linked. But even in that scenario, the default behavior should be to copy all the files for the sake of consistency.

Cheers,

Cédric

Show
Cédric Vidal added a comment - Hi, Well I think that the files should be copied, first of all for the sake of consistency with the other containers, and secondly because as it is right now, it is absolutly impossible to use Cargo to build a JBoss configuration, which is precisely what I need Cargo to do Anyway, to make everybody happy, one could add a configuration parameter which would enable to tell whether one wants to have all the files copied or linked. But even in that scenario, the default behavior should be to copy all the files for the sake of consistency. Cheers, Cédric
Hide
Permalink
Pedro Assuncao added a comment -

I can think of another reason why you would want to copy everything. Say you use an external native lib and you want to pick it up from your configuration (instead of having to get it from the jboss home folder), you would need to have it copied automatically by cargo to the target folder.

Also, this is not the best place for the question, but is there a particular reason why there is no configuration type "existing" for jboss 4.2.x?

Cheers,
Pedro

Show
Pedro Assuncao added a comment - I can think of another reason why you would want to copy everything. Say you use an external native lib and you want to pick it up from your configuration (instead of having to get it from the jboss home folder), you would need to have it copied automatically by cargo to the target folder. Also, this is not the best place for the question, but is there a particular reason why there is no configuration type "existing" for jboss 4.2.x? Cheers, Pedro
Hide
Permalink
Matt Wringe added a comment -

Pedro wrote:
"Also, this is not the best place for the question, but is there a particular reason why there is no configuration type "existing" for jboss 4.2.x?"

I don't believe there is a reason, could you please open another bug about it and assign it to me?

Thanks,

Matt Wringe

Show
Matt Wringe added a comment - Pedro wrote: "Also, this is not the best place for the question, but is there a particular reason why there is no configuration type "existing" for jboss 4.2.x?" I don't believe there is a reason, could you please open another bug about it and assign it to me? Thanks, Matt Wringe
Hide
Permalink
Savas Ali Tokmen added a comment -

Since JBoss container has support for existing local configurations, closing this issue.

Show
Savas Ali Tokmen added a comment - Since JBoss container has support for existing local configurations, closing this issue.

People

  • Assignee:
    Unassigned
    Reporter:
    Cédric Vidal
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: