Comparator not recognised on application level classpath

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 3.2.0
  • Fix Version/s: None
  • Component/s: Transport: File
  • Labels:
    None
  • Environment:

    JBoss Application server

  • User impact:
    High
  • Similar Issues:
    None

Description

Comparators packaged in a project jar and dropped in the application level classpath, are not recognised by the file inbound endpoint. Only when the comparator is packaged in it's own jar and dropped in the global classpath, is it recognised by Mule.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Ari Ruotsalainen added a comment -

We have the same problem. This gets the deployment kind of ugly. Is this going to be fixed sometimes?

Show
Ari Ruotsalainen added a comment - We have the same problem. This gets the deployment kind of ugly. Is this going to be fixed sometimes?
Hide
Permalink
Ari Ruotsalainen added a comment -

I guess the problem is in FileMessageReceiver.getComparator()-method





 Class<?> clazz = Class.forName(comparatorClassName.toString());

{code
 

    

    

        Show
        

            
    
    
    
                

    Ari Ruotsalainen
 added a comment  -                I guess the problem is in FileMessageReceiver.getComparator()-method






 Class<?> clazz = Class.forName(comparatorClassName.toString());
{code         

    



                     

    

        Hide
        

            Permalink
                                

        

    
    
    
                

    Ari Ruotsalainen
 added a comment  -   

        
Oh crap. Jira is bugging and there is not edit option to comment.



I guess the problem is in FileMessageReceiver.getComparator()-method



Class<?> clazz = Class.forName(comparatorClassName.toString());



This uses Mule classloader. I think this could be fixed something like:

Class<?> clazz = getConnector().getMuleContext().getClass().forName(comparatorClassName.toString());

the muleContext might have the correct application classloader
 

    

    

        Show
        

            
    
    
    
                

    Ari Ruotsalainen
 added a comment  -                Oh crap. Jira is bugging and there is not edit option to comment.

I guess the problem is in FileMessageReceiver.getComparator()-method

Class<?> clazz = Class.forName(comparatorClassName.toString());

This uses Mule classloader. I think this could be fixed something like:
Class<?> clazz = getConnector().getMuleContext().getClass().forName(comparatorClassName.toString());
the muleContext might have the correct application classloader         

    



                 



                                
                            

                            

                                
                                    
People
    
    
  • 
                
    
            
    Assignee:
    
            
    
                Unassigned
            
    
        
    
                        
    
            
    Reporter:
    
            
    
                        Jaco Koekemoer
            
    
        
    
                    
    • 




                Vote
    
                (5)
    



            Watch
    
        
            (2)
    


Dates
    
    
  • 
            
    
            
    Created:
    
            
    

                
                                            
                                         
            
        
    
            
    
            
    Updated:
    
            
    

                
                                            
                                         
            
        
    
        
    •