从Android应用程序调试SQLite数据库(Debugging SQLite Database from Android App)

 你的例子有点简单。 你的实际问题可能是很多问题，但我会对最有可能发生的事情进行抨击。 
 
 如果目标是修改div的内容，那么答案就是根本不使用道具。 这正是你的国家所针对的！ 
 
var Banner = React.createClass({
    render: function() {
        return <div>this.state.word</div>
    },
    getInitialState: function(){
        return {word: this.props.word};
    }

    changeWord: function(word){
        this.setState({word: word});
    }
});
 
 编辑： 
 
 如果您尝试从嵌入页面中其他位置的vanilla js修改组件： 
 
 我认为在这种情况下你最好的选择是利用一些（如果不是全部）Flux设计模式： https ： //facebook.github.io/flux/docs/overview.html#content 
 
 如果不是整个Flux范例，你至少可以利用Flux处理'Stores'的方式，它实际上只是Node.js EventEmmiters： https ：//nodejs.org/api/events.html 
 
var BannerStore = new EventEmmitter();

var Banner = React.createClass({
    render: function() {
        return <div>this.state.word</div>
    },
    getInitialState: function(){
        return {word: this.props.word};
    },
    changeWord: function(){
        this.setState({word: BannerStore.word});
    },

    componentDidMount: function(){
        BannerStore.on('banner_change', this.changeWord);
    },

    componentWillUnmount: function(){
        BannerStore.removeListener('banner_change', this.changeWord);
    }
});

function changeText(component, text){
    if(component === 'banner'){
        BannerStore.word = text;
        BannerStore.emit('banner_change');
    }
}
changeText(banner, 'Goodbye') 
 
 从长远来看，使用全通量范式将更加清洁，但是可以合理地输入SO。 

Your example is a bit to simplistic. Your actual problem could be a number of things, but I'll take a stab at what seems most likely.
 
If the goal is to have the content of your div be modified, then the answer is not to use props at all. That's exactly what your state is for!
 
var Banner = React.createClass({
    render: function() {
        return <div>this.state.word</div>
    },
    getInitialState: function(){
        return {word: this.props.word};
    }

    changeWord: function(word){
        this.setState({word: word});
    }
});
 
EDIT:
 
If you're trying to modify the component from vanilla js embedded elsewhere in the page:
 
I think your best bet in this case would be to leverage some (if not all) of the Flux design pattern: https://facebook.github.io/flux/docs/overview.html#content
 
If not the entire Flux paradigm, you could at the very least make use of the way Flux handles 'Stores', which are essentially just Node.js EventEmmiters: https://nodejs.org/api/events.html
 
var BannerStore = new EventEmmitter();

var Banner = React.createClass({
    render: function() {
        return <div>this.state.word</div>
    },
    getInitialState: function(){
        return {word: this.props.word};
    },
    changeWord: function(){
        this.setState({word: BannerStore.word});
    },

    componentDidMount: function(){
        BannerStore.on('banner_change', this.changeWord);
    },

    componentWillUnmount: function(){
        BannerStore.removeListener('banner_change', this.changeWord);
    }
});

function changeText(component, text){
    if(component === 'banner'){
        BannerStore.word = text;
        BannerStore.emit('banner_change');
    }
}
changeText(banner, 'Goodbye') 
 
Using full flux paradigm will be cleaner in the long run, but is more than can be reasonably typed into SO.