email - Embeddable messaging component for Java web application -


To meet the customer's requirements, we need users to exchange information between each other. > Messaging system does not require state-of-the-art back-end and can be easily implemented with some tables to store messages and message types. The problem is that I believe the requirements of front-end are very high and disposable is very important. Apart from this, I hope part of this communication will become an important part of the system for a long time.

Is there anything that can be directly integrated into the Java web application and can be optimized for the design of the application?

  • <
  • Information on new messages in user inbox (if possible: on the current page)
  • Interface for existing user management
  • preferably, component first

    • Message Management (Select, Delete, Answer, Delete / Restore, ...)
    • Folder: Inbox, Sent, Trash
    • Tagging: Message categories
    • A panel Show the last x message in the / div
    • Style to look like an app

    If something is reasonably stable, then in this way Before using an application I like to use a component. The application runs on the wicket, but we are not connected to this framework for the component of the message.

    Thanks, Currenam


    In the portal server, I have the flexibility to add portlets which I can see anything that is similar to the component; Such as offers and portlets. As akf in a comment,

    provides a solid foundation for sending messages. We are looking for something that can be integrated into a web application. If we have to build many UI around the jabber, then we can not really consider it a good fit for our needs.

    itemprop = "text">

    Okay, this may be a little surprising but what about trying? If I review your criteria:

    Is there anything that can be directly integrated into the Java web application and may be adaptable to the application's design [...]

    It may be that you will search on this mini-tutorial: (How is it not interesting?)

    From the service level:

    < Ul>
  • Users (Topics, Topics)
  • Answer a message
  • User Guides on New Message in Inbox (If possible: on current page)
  • Interface management to existing user
  • Everything but final point is represented by Google Wave example The final point can be a little harder to solve because you will need all your users to have a Googlewave account. Managing those accounts, but ATMs are not possible. If this is absolutely mandatory then you can plan your own example because it is one but your goal has already been done for you, is not it?

    Preferably, ending with the following functionality:

    • Message Management (Select, Remove, Answer, Delete / Restore, ...)
    • Folder: Inbox, Sent, Trash
    • Tagging: Message categories
    • Show the last X messages in the panel / div
    • Like the app Style to see

    Great, it's all right with the wave.

    If there is any reasonable stability, then I like to use one component before applying an application like this. The application runs on the wicket, but we are not connected to this framework for the component of the message.

    Well the wicket is so fashionable, you should love this solution :-) I accept that it is a bit "I have not done anything like this myself, but thought That it can broaden your vision in relation to your problem ...


    Comments

    Popular posts from this blog

    c++ - Linux and clipboard -

    What is expire header and how to achive them in ASP.NET and PHP? -

    sql server - How can I determine which of my SQL 2005 statistics are unused? -