Announcement Announcement Module
Collapse
No announcement yet.
Reference Manual feedback please! Page Title Module
Move Remove Collapse
This is a sticky topic.
X
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • Mark Fisher
    started a topic Reference Manual feedback please!

    Reference Manual feedback please!

    Spring Integration Community,

    We have an open issue for Reference Manual typos to be fixed in 1.0.3:
    http://jira.springsource.org/browse/INT-676

    Please feel free to add to that!... not only typos but also suggestions for any material that is unclear or lacking sufficient detail. The 1.0.3 release is planned for the end of next week, and we also have plenty of other issues, but we will try to address as much as possible based on comments added to that issue.

    I will soon be posting another thread for 2.0 roadmap suggestions - as soon as JIRA is reorganized a bit to reflect our current plan.

    Regards,
    Mark

  • kxen
    replied
    I have a gripe about SpEL documentation that isn't limited to the integration project. Since this is the only forum that I know has a 'Reference Manual feedback' thread I will subject this forum to my quibble.

    There isn't a document or page that covers all of what's available in SpEL.

    I have to go to each project to see what that object adds to SpEL. I pocked around on StackOverflow and found examples for #root, #this.getObject(), and #{byId()}; and I have know idea where to find that in the documentation. I've read the core reference manual and could only figure out how to do very basic things such a getting static fields, getting values out of maps or lists, and calling a bean property (only if that bean doesn't have a '.' in the name.).

    Google isn't a lot of help because it thinks I'm looking for twitter hash tags when I google #root.

    I the SpEL warrants it's own dedicated forum.

    Leave a comment:


  • Gary Russell
    replied
    Thanks for the feedback.

    FYI, there are a couple of samples that explore various testing techniques...

    https://github.com/SpringSource/spri...sting-examples

    https://github.com/SpringSource/spri...sting-examples


    If you still feel there is a need for further documentation, please feel free to open a JIRA issue against the 'Documentation' component.

    Thanks.

    Leave a comment:


  • splazit
    replied
    Thanks for the document, as usual, it's very helpful.

    Is it possible if you guys can include how to write unit tests for the flows? I saw there's a library but not sure how to use it yet.

    Leave a comment:


  • Gary Russell
    replied
    Thanks for pointing this out; I opened a JIRA issue - https://jira.springsource.org/browse/INT-2901

    Leave a comment:


  • mgirard
    replied
    In the spring integration reference document it shows the sprint-int mail outbound channel adapter as:
    Code:
    <int-mail:header-enricher subject="Example Mail"
                         to="[email protected]"
                         cc="[email protected]"
                         bcc="[email protected]"
                         from="[email protected]"
                         reply-to="[email protected]"
                         overwrite="false"/>
    In the current version, they are sub-nodes, rather than attributes:

    Code:
    <int-mail:header-enricher>
          <int-mail:to value="[email protected]" />
          <int-mail:from value="[email protected]" />
          <int-mail:subject value="TEST Mail Message/>
        </int-mail:header-enricher>

    Leave a comment:


  • kxen
    replied
    Please add definitions and diagrams for the terms upstream and downstream. I'm not confident that I understand what you mean when those terms appear in the reference manual.

    Leave a comment:


  • jav01_2000
    replied
    In B.3: Configuring the Task Scheduler
    (http://static.springsource.org/sprin...-taskscheduler), it would be nice to provide some of the reasons for providing our own "taskScheduler".

    Pleaser refer to http://forum.springsource.org/showth...nnel-adapte-gt for the problem I was facing in the past few days.

    Leave a comment:


  • oleg.zhurakousky
    replied
    Can you explain what you are trying to do?

    We are planning to work on exposing API more formally (e.g., with samples etc.), however it would be nice to hear your use case as we often found in these situations users who wanted to code with SI API didn't really have to do it in the first place.

    Leave a comment:


  • aappddeevv
    replied
    I found it hard to understand the message endpoint parts of the manual especially when trying to write at the API level. There are message sources and message handlers and in some cases you have to match them correctly based on the channel type. I'm not sure I got that on the first pass. It took me awhile to see that the inbound-channel-adapter and the output-channel-adapter mapped into MessageSource or MessageHandler.

    I do think the manual is very good though. The subject material is a harder than most.

    One suggestion is to have the namespace XML and then right below it have the nearly equivalent API code.

    Leave a comment:


  • jbbarquero
    replied
    Thank you very much for the response to both of you.

    Have you considered my request regarding the namespace apendix?

    Originally posted by jbbarquero View Post
    I miss an apendix regarding the namespace, as it appears in the Spring Security Reference Documentation: The Security Namespace

    Leave a comment:


  • oleg.zhurakousky
    replied
    Yeah, http://www.eaipatterns.com/ and the book is over 10 years long so it can hardly be called 'new', however I do agree that the programming model is not as widely adapted as the others and because of that in the very near future we'll begin releasing a series of sreencasts guiding you through this process. We'll post a separate announcement for that.
    Last edited by oleg.zhurakousky; Mar 18th, 2012, 09:20 AM.

    Leave a comment:


  • aheusingfeld
    replied
    Hi,

    Originally posted by jbbarquero View Post
    I'd like to have a chapter regarding "how to begin"

    I mean, EAI is some kind of new programming model, channels and messages, it's well explained int the chapter 2, but you're used to programming main applications, web applications and even enterprise applications.

    The "Hello World" sample shows a delay demo with an inbound channel, a file outbound channel and a task executor, but it wouldn't my approach in first application (due to my lack of experience with this new paradigm)
    In case you're completely new to enterprise application integration you should really give http://www.eaipatterns.com/ a read prior to starting with Spring Integration. The framework is mainly based on the patterns explained in the book of the same title by Gregor Hohpe and Bobby Wolf. With this knowledge at hand the reference manual is quite good.
    Unfortunately there are too many use cases to provide a "hello world"-example for each one, I'd say.

    Regards
    Alex

    Leave a comment:


  • jbbarquero
    replied
    I'd like to have a chapter regarding "how to begin"

    I mean, EAI is some kind of new programming model, channels and messages, it's well explained int the chapter 2, but you're used to programming main applications, web applications and even enterprise applications.

    I miss a lot an explanation of how to call the "message flow" for the very first time.

    It's not until the chapter 7 that you can read how to interact with Spring Integration from your application's business logic: with a Gateway (the good news are that you do it so completely unaware of the Spring Integration API)

    Please, take into account that if I create a first SI application, my mind is not ready to think in terms of channels and messages, but in terms of main classes, test classes or init servlets.

    The "Hello World" sample shows a delay demo with an inbound channel, a file outbound channel and a task executor, but it wouldn't my approach in first application (due to my lack of experience with this new paradigm)

    Leave a comment:


  • jbbarquero
    replied
    I miss an apendix regarding the namespace, as it appears in the Spring Security Reference Documentation: The Security Namespace

    I'd rather use the namespace, but you have a better understanding if you know the beans that are actually used. Furthermore, you can provide better values to the attributes if you can see what are they for.

    Leave a comment:

Working...
X